Delivery, dispatch and the driver app: what happens after the order is taken

Delivery looks like an extension of the restaurant. It is closer to a second business that happens to share a kitchen — different costs, different failure modes and, very often, a different margin.

Zones are a promise, not a map

A delivery zone is four decisions written down: a centre, a radius, a fee, and an expected time. Every one of them is a commitment you are making to a customer before they order.

The common mistake is a single radius around the branch with one fee. Distance is not the only cost — a zone with heavy traffic and no parking costs more per drop than one twice as far along a clear road. Two zones with different fees are more honest than one average that overcharges half your customers and loses money on the other half.

The six states of a delivery

Once a driver is involved, the order carries its own life:

Pending → Assigned → Picked up → In transit → Delivered, with Failed, Cancelled or Returned as the exits.

That may look like bureaucracy. It is the difference between a manager who knows where every order is and a manager who is calling three riders during a rush. It also gives you the two timestamps that matter: how long the food sat waiting for a driver, and how long the drive itself took. Those are separate problems with separate fixes, and a single “late” label hides both.

What the driver should see

The driver app should show the current job and the next one. Address, customer name, what to collect, what to charge if it is cash, and one button to move the state forward.

That is deliberately austere. A rider is on a bike, often in traffic, sometimes in the rain. Every extra choice on that screen is a decision made badly. GPS coordinates on the drop-off mean the address does not have to be re-read; the collected amount means the cash-up at the end of the shift is arithmetic instead of memory.

The number nobody calculates

Here is the calculation most restaurants skip. Take a delivery order and a dine-in order of the same value, and subtract what each actually costs:

• Dine-in: food cost, and a share of labour that you were paying anyway.
• Delivery: food cost, packaging, the delivery fee you did not charge, the rider’s time or the aggregator’s commission, and the refunds you issue when something arrives cold.

Very often delivery is a third of revenue and a tenth of profit. That is not an argument against delivery — the volume keeps the kitchen busy and the brand visible. It is an argument for knowing the number, because the decisions that follow are all different:

• If delivery margin is thin but positive, the fix is the fee or the zone, not the menu.
• If it is negative on one zone only, close that zone.
• If it is negative on aggregator orders and positive on your own channel, you have a marketing problem, not a delivery problem.

Practical rules

1. Price the fee against distance, not against embarrassment. A fee that covers the trip is normal everywhere.
2. Cap the promise. An estimate you miss twice teaches a customer not to trust the third one.
3. Separate “waiting for rider” from “on the road” in your review. They are different departments.
4. Track rating and feedback per delivery. A single rider or a single zone is usually behind a cluster of complaints.

Delivery run properly is a good business. Delivery run as an afterthought is a busy way to lose money with the kitchen at full volume.