Delivery used to be an impossible choice
For years, many restaurant groups felt stuck between two expensive models: pay marketplace commission that can reach 30% plus, or build and manage an in-house delivery fleet that creates heavy operational overhead.
A third model has been hiding in plain sight
White-label delivery networks such as Uber Direct, Stuart, and Gophr allow restaurants to use courier infrastructure without handing over the full guest journey to an aggregator app. You keep your own ordering surface, your own data, and your own brand experience.
What is Uber Direct?
Uber Direct is a logistics API that connects Uber's courier network to your own ordering channels. A guest orders through your website or app, a courier is dispatched for fulfilment, and the customer experience stays on your brand.
Same driver network, different commercial model
The courier network may be similar to what powers marketplace fulfilment, but the economics are not. In a white-label model, delivery behaves like a utility cost, closer to parcel logistics in e-commerce.
Marketplace tax vs utility model
| Model | Commercial structure | Typical outcome |
|---|---|---|
| Marketplace apps | 25% to 35% commission on total order value | Cost scales with basket size and volume |
| White-label delivery | Flat courier fee per drop (distance/vehicle based) | Predictable logistics cost, no basket commission |
| Customer ownership | Marketplace retains most customer relationship | Direct channel keeps customer data and lifecycle control |
Marketplace model usually means
- Commission paid on every order value, not a flat admin fee.
- Limited customer ownership and weaker re-engagement options.
- Guest experience controlled by third-party product surfaces.
- Higher basket values becoming more expensive to process.
White-label model usually means
- A flat fulfilment fee based on distance and vehicle type.
- Direct customer data capture through your own channel.
- Brand-controlled menu, checkout, and post-order communications.
- Economics that stay clearer as basket value increases.
A simple delivery economics example
Worked example
Inputs
- £35 average delivery order value
- 30% marketplace commission
- £4.80 white-label delivery fee
Steps
- Marketplace commission per order is £10.50.
- White-label fulfilment cost per order is £4.80 before payment processing.
- Difference is about £5.70 per order before any fee subsidy adjustments.
At 100 delivery orders per week, that gap can represent substantial annual savings per site.
How white-label delivery works in practice
The workflow is straightforward: the guest orders on your own channel, your platform confirms and routes the order to kitchen operations, a courier is dispatched via API, and fulfilment is billed at a delivery fee level rather than a basket commission.
Typical workflow
- Guest places a delivery order on your website or app.
- Your checkout applies your delivery fee and payment rules.
- Order flows into your operational stack.
- Courier dispatch is triggered through Uber Direct or another network.
- You pay courier fulfilment cost; guest pays your configured delivery fee.
- Any subsidy is the gap between your guest fee and courier fee.
Distance and vehicle pricing still matters
White-label delivery fees are typically shaped by distance, vehicle type, and local demand conditions. Most groups design delivery-fee strategy around expected zone economics and acceptable subsidy levels.
Typical UK ranges (early 2026 guidance)
- 0 to 2km (bike): roughly £3.20 to £4.50
- 2 to 5km (bike or car): roughly £4.50 to £6.20
- 5 to 8km (car): roughly £6.20 to £8.50
Why this is strategic for multi-site operators
For groups operating multiple locations, this is not only a margin discussion. It is also an ownership and control discussion: who owns guest identity, who owns retention, and who can optimise the full lifecycle from first order to repeat frequency.
What ownership unlocks
- Direct CRM and lifecycle automation.
- Full visibility of repeat behaviour and LTV.
- Better control of promotion logic and fee strategy.
- Cleaner experimentation on AOV, delivery thresholds, and conversion.
The integration layer matters
Courier APIs handle logistics, but your ordering and guest-experience platform should orchestrate dispatch rules, delivery comms, and reporting. The strongest setups treat white-label fulfilment as infrastructure inside a direct-channel strategy.
What a strong stack should handle
- Dispatch timing aligned to prep time and distance.
- Live delivery tracking in your brand experience.
- Unified reporting across dine-in, collection, and delivery.
- Single guest identity across channels.
When white-label delivery fits best
White-label delivery is typically strongest for operators already running or building owned ordering channels and wanting to reduce marketplace reliance while keeping delivery convenience.
Best-fit conditions
- You already have meaningful direct-channel demand.
- You are focused on retention and customer ownership.
- You operate in urban or suburban areas with reliable courier coverage.
- You want controllable delivery-fee policy and margin modelling.
Less suitable conditions
- Very low delivery volume where setup effort cannot be justified.
- Rural service areas with inconsistent courier availability.
- Short-term campaigns without long-term channel strategy.
FAQ: Is Uber Direct cheaper than marketplaces?
In many scenarios, yes. Marketplaces usually apply percentage commission on order value, while white-label delivery is fee-per-drop. On higher basket values, the gap can widen quickly.
FAQ: Do I need my own ordering platform?
Yes. Uber Direct is a logistics API, not a consumer ordering app. You need your own ordering layer to capture demand, route operations, and trigger courier dispatch.
FAQ: Can I run multiple courier networks?
Yes. Many operators connect more than one network and route dispatch by coverage, speed, or cost to reduce fulfilment risk and improve service consistency.
The bottom line
Delivery does not have to be a margin leak. White-label delivery lets you keep the guest relationship, keep the data, and pay logistics as a fulfilment utility rather than a basket tax.