Delivery Pricing Models

A delivery charge should be a deliberate part of the commercial model, not a copy of a competitor’s checkout. The right structure depends on zone cost, order contribution, driver model, customer expectations and peak capacity. A simple model that staff and customers understand is often better than a technically precise model that changes unpredictably.

Common pricing structures

Model	Useful when	Main risk
Flat fee	The service area is compact and journey costs are similar	Inner customers may subsidise expensive outer journeys
Zone-based fee	Journey time and cost vary materially by area	Boundary errors and complex maintenance
Distance-based fee	The platform calculates routes reliably	Customers may see inconsistent prices for nearby addresses
Free delivery threshold	Additional basket contribution genuinely funds the journey	Discounting delivery without enough incremental margin
Subscription or membership	Repeat demand is proven and terms are tightly controlled	Heavy users can create loss if usage assumptions are weak
Peak adjustment	Capacity and provider cost change sharply at defined times	Customer distrust if the rule is unexpected or opaque

Calculate the full cost first

Include driver paid time or provider charge, vehicle or mileage arrangements, employer costs where applicable, dispatch time, packaging, payment charges, failed-delivery allowance, redelivery, support and the return journey. Then compare that burden with basket contribution rather than sales value alone.

Keep price and availability separate

A higher fee cannot make an unsafe or impossible journey viable. When kitchen or driver capacity is exhausted, reduce availability, extend the promise or close the zone. Do not use surge pricing as a substitute for operational control.

Present the charge clearly

• Show the delivery fee before the final payment step.
• Explain the minimum order and threshold condition.
• Do not preselect optional extras.
• Show how promotions interact with delivery charges.
• Make location-specific changes visible before commitment.

Test customer and financial outcomes

Measure conversion, order contribution, basket mix, zone demand, complaints, abandoned checkouts and delivery reliability. Compare the effect over a representative period, including peaks. A lower fee may improve order volume but worsen kitchen overload; a higher fee may improve unit contribution while destroying dense routes.

Common mistakes

• calling delivery “free” while adding an unavoidable service fee later;
• using one fee across very different zones;
• funding delivery and a basket discount simultaneously without modelling the combined cost;
• ignoring the customer’s full payable price;
• changing fees without testing marketplace, website and saved-address behaviour;
• keeping an attractive price after the operation can no longer fulfil the promise.

Keep pricing consistent across systems

Document which platform owns the fee and how it reaches website, app, marketplace and staff-assisted orders. Test boundary addresses, promotions, saved baskets, refunds and pre-orders. A pricing model is not implemented until every active channel displays and records the same approved rule or an intentional, documented exception.

Use change governance

Record the reason, expected outcome, approval, start and review date for each change. Preserve the previous value for rollback. Staff should know whether a new price is permanent, promotional, zone-specific or limited to a service period.

Practical next step: compare three models — flat, zone-based and threshold — using actual completed-delivery cost and representative baskets rather than headline revenue.

Official UK price-transparency reference

• Competition and Markets Authority: Providing clear and accurate information about prices

Guidance checked: 24 July 2026. Mandatory delivery and service charges should be clear before the customer commits to the purchase.

Related guides

• Delivery Management — the main guide for the wider topic.
• Delivery Zones and Minimums — the broader guide that frames this implementation.
• How to Plan Delivery Minimums — a closely related operational control to review alongside this page.
• How to Manage Multiple Delivery Zones — a closely related operational control to review alongside this page.