Third-party delivery networks

No driver fleet — or not enough of one? Connect a third-party delivery network and SupaOrder hands deliveries to their couriers while orders stay in your branded apps and the customer relationship stays yours. Four providers are supported: DoorDash Drive, Uber Direct, Shipday, and Nash.

How it works

A delivery order is ready to go out.
Instead of one of your own drivers, the order is handed to a connected network. The provider quotes the delivery and dispatches one of its couriers.
The provider’s delivery fee flows into the order, and delivery progress flows back so your staff and the customer can follow it.
The courier picks up from your outlet and delivers — your packaging, your brand, their wheels.

Your menu, checkout, and customer accounts are untouched; only the last mile changes hands.

Connecting a provider

Open Dashboard → Settings → Integration → Plugin List (/configuration/integrations/integration/plugin-list) and add the provider you’ve signed up with.
Supply the provider credentials from your account with them — API keys or an account connection, depending on the provider. These are issued by the provider when you register (for example a DoorDash Drive developer account or an Uber Direct account).
Save, and the network becomes available for deliveries.

You’ll need a commercial account with the provider itself — SupaOrder connects to it, it doesn’t create it.

Using more than one network

You can connect several providers at once and set a priority order between them. When a delivery needs a courier, quotes are tried in your priority order — so you can prefer your cheapest or most reliable provider and fall back to the next when it can’t serve a given address or time.

This also pairs well with your own fleet: many restaurants run their own drivers for the core area and hours, and lean on a network for overflow, late nights, or far-out addresses. See Drivers & assignment for the own-fleet side.

Customer-facing delivery quotes

Networks can also power the delivery price your customer sees: at checkout, a live quote from your connected providers can be used for the delivery fee, so what the customer pays tracks what the delivery actually costs. Whether you pass the quote through, subsidize it, or stick with your own zone-based fees is a pricing decision — both models are supported.

Tracking and costs

Progress — network deliveries show up alongside your own on the order, with the courier’s progress updating as the provider reports it.
Fees — the provider’s delivery fee is recorded on each order, so reporting reflects what each delivery actually cost you.
Summary report — see Dashboard → Reports (/reports/delivery-network-summary) for network usage and costs over time.

Choosing a provider

Coverage and pricing vary by city, so the right answer is local:

DoorDash Drive and Uber Direct — the white-label arms of the big marketplaces; strong courier density where those apps are popular.
Shipday — delivery management with its own driver options; popular with smaller operations.
Nash — a delivery orchestration layer that itself spans multiple fleets.

If more than one covers your area, connect both and let priority ordering and the summary report tell you which earns the top slot.

Network vs your own fleet

	Your own drivers	Third-party network
Cost shape	Wages/contracts — fixed-ish, cheap at volume	Per-delivery fee — zero when quiet, pricier per drop
Control	Full: who delivers, in what uniform, how trained	The provider’s courier, the provider’s standards
Coverage	Only where your drivers are	The provider’s whole courier map
Setup effort	Recruit, approve, train, manage	Sign up with the provider, connect, test

The common path: start on a network to launch delivery with zero fleet overhead, then bring core hours in-house once volume justifies it — keeping the network connected for overflow.

Troubleshooting

Symptom	Try this
Provider never returns a quote	Confirm the credentials saved in Plugin Config are correct and your outlet address sits inside the provider’s coverage area
Quotes work but deliveries fail for some addresses	Coverage gap or address-format quirk on the provider’s side — test that exact address in the provider’s own tools, and rely on priority fallback to another provider
Delivery fee on the order looks wrong	Check which provider won the quote — a fallback provider may have priced the job; review your priority order
Courier progress not updating	Provider-side reporting delay is common; if it persists across orders, re-check the connection in Plugin Config and contact the provider