Solutions
Work
Blogs
About
Start a project →
← Back to blog
Ecommerce12 October 2026 · 5 min read

Delivery zones and minimum orders: the four decisions

A cobbled street between Victorian mill buildings and modern towers in central Manchester at dusk

Delivery areas are usually drawn once, in a hurry, as a circle on a map, and then never touched again. That circle is quietly deciding which orders you lose money on, and nobody ever goes back and checks.

There are only four decisions in it, and they are worth making deliberately.

Circle, postcodes or road distance

  • A circle is simple and wrong at the edges, because it measures as the crow flies. A river, a motorway or a one-way system can make a mile on the map twenty minutes in a car.
  • Postcode zones match how drivers actually think and let you price by area, but they need setting up properly and a postcode that straddles two zones has to be decided one way.
  • Road distance is the most accurate and the most work: real driving distance from your door, priced in bands. Worth it when your area has awkward geography, and overkill when it does not.

The minimum order is where the money is

A minimum order set by area, rather than one number for everywhere, is the single change most takeaways should make. The order that loses money is not the small one nearby, it is the small one at the far edge. Raising the minimum for the furthest zone costs you almost nothing you wanted and removes the drop that ties up a driver for half an hour.

Free delivery over a threshold

Free delivery is a discount, so it should buy you something. Set over a sensible threshold it reliably lifts the basket; set at zero it just reduces every order by the cost of a driver. If you offer it, put the threshold slightly above your current average order, not below it, or you are paying for behaviour you already had.

What happens when you are slammed

Every area should be pausable on its own. The furthest zone is the first thing to switch off when the kitchen is forty minutes behind, because those are the orders that generate the complaints. Quoting an honest longer wait is better than taking the order and hoping.

Check it once a quarter

Pull the last three months of delivered orders, look at the furthest ten per cent, and work out what each actually cost in driver time. Most places find a handful of streets they would rather not serve, or would serve at a higher minimum. That is a ten minute job that pays for itself.

All of this is ordinary configuration in a system you own, and awkward or impossible in one you rent. It is part of how we build your own ordering platform, and if you want the comparison against what the apps charge for the same delivery, the commission calculator does it in your own numbers.

Questions

Before you ask.

Should delivery areas be a radius or postcodes?

A radius measures as the crow flies, so it is wrong wherever a river, motorway or one-way system gets in the way. Postcode zones match how drivers think and let you price by area; road-distance bands are the most accurate and the most work to set up.

Should the minimum order be the same everywhere?

No, and changing that is the single most useful adjustment most takeaways can make. The order that loses money is the small one at the far edge, not the small one round the corner.

Is free delivery worth offering?

Only above a threshold, and the threshold should sit slightly above your current average order. Below that you are paying a driver to deliver behaviour you already had.

What should happen when the kitchen is slammed?

Each area should be pausable on its own, with an honest longer wait quoted. The furthest zone is the first to switch off, because those orders generate the complaints.

How often should delivery zones be reviewed?

Once a quarter. Pull the last three months of orders, look at the furthest ten per cent and work out what each cost in driver time. It is a ten minute job that usually pays for itself.
Related reading
Web Design
Why your website is slow, and what it costs you
Technology
When two of your systems should be talking to each other
Security
What a software support contract should actually cover