Local demonstration — payments, orders, calls, messages and delivery records are disabled.

YardFlow · solid-fuel delivery platform

A delivery business, set up for the fuel trade.

Each supplier starts with its own local workspace: a branded ordering site, product and area controls, office operations, and a driver handoff. This demonstration does not create accounts or connect live systems.

1 supplier workspace3 sample delivery areas0 connected payments

01 · supplier profile

Start a local workspace

No account created

Capture the fields a solid-fuel supplier needs before a branded site and operations views can be prepared.

Values stay in the current browser session only.

Supplier path

One workspace per seller

  1. 1
    Supplier profileLocal setup only
  2. 2
    Catalogue and areasSet products, prices and capacity
  3. 3
    Storefront reviewCheck the customer journey
  4. 4
    Operations handoffGive office and drivers clear work
  5. 5
    Payment activationOnly after supplier and provider checks

02 · catalogue

Set the local price book

Sample euro pricing
Cost, margin and stock are fixture values for this supplier workspace. They are not accounting, stock-control or settlement records.

03 · delivery coverage

Define service areas

Capacity is local sample data
T12T23P17
Available capacity36 unitsSample allocation across 3 areas
Delivery slot capacity

04 · branded storefront

A site for Cairn Solid Fuel

Preview ready
CCairn Solid Fuelsolid fuel

Order fuel for delivery

Coal · wood · briquettes3 local delivery areas configured
Preview only. It is not a published supplier website.

05 · Stripe Connect readiness

Keep merchant money controls separate

Not connected

Each supplier is the seller of record. YardFlow can prepare a supplier-scoped application-fee model, but it does not create a Stripe account, connected account, charge, refund, webhook or settlement in this demonstration.

  • Supplier identity, seller terms and roles
  • Connected-account onboarding and payout eligibility
  • Supplier-scoped payment, fee and refund ledger
  • Verified webhooks, idempotency and recovery procedures

Regional rollout

Reuse the product carefully

The same workflow can support more suppliers and countries, but each legal seller, currency, tax setting, delivery rule and payment eligibility must be configured separately.

Ireland · local sampleOther markets · not configured