Routes build themselves. Drivers just drive.

There is a specific moment every growing tiffin kitchen hits: a driver quits, a new one starts, and the owner discovers that the route only ever existed in their own head. The next two hours are spent reading addresses down a phone while food goes cold.

Everything here is designed so that a driver who started this morning can complete tonight's run without you.

Zones first, routes second

Delivery areas are defined by postal-code prefix — the front half of a Canadian postal code, which maps neatly onto the neighbourhoods people actually live in. Customers sort themselves into the right zone from their address as they sign up.

There is a map view with real boundaries, so an area is something you can look at rather than a list of codes you are trusting.

Zones are the unit that makes the economics legible. The zones and areas report shows customers, deliveries, success rate and revenue by area — which is how you discover that one zone is quietly unprofitable, too few customers spread too far apart.

One run per area

Each area's deliveries for the day become a single run, assigned to one driver. That mapping — area to run to driver — is what keeps a driver from crossing the city twice, and what makes performance comparable between drivers.

Runs cannot be dispatched before the day is packed. Packing comes first by design; a route that starts before the food is boxed just moves the waiting from the driver's car to your kitchen.

The stop order is not yours to worry about

When a driver starts their route, the stops sort into the shortest driving order from where they are. Fewer kilometres, less fuel, less time — and no judgement calls from someone who does not know the neighbourhood yet.

They follow the list top to bottom. That is the entire instruction.

The driver app

Built for one hand, in a car, in winter:

• The day's stops, in order. No planning, no map-reading, no decisions.
• One tap for delivered. One tap for failed, with a reason attached.
• A photo at every door — proof of delivery, which ends the "I never got it" conversation permanently.
• Delivery notes — the buzzer that never works, the gate code, leave it with the neighbour, do not ring after 8.
• Cash collected, recorded per run so it reconciles instead of living in a jacket pocket.

You watch from the kitchen

The route fills in live as stops complete. No "where are you?" calls, and when a customer rings to ask, you can answer without ringing the driver first.

And afterwards, the numbers

Four reports come out of this. Delivery history for any past day, every stop with its proof photo, searchable and exportable. Delivery performance — success rate, trend, by area, with distance and fuel. Failed deliveries, recorded with the reason, because failures cluster around one bad address or one buzzer rather than spreading evenly. And a driver leaderboard with pay reconciliation, checking delivered stops against what is actually booked.

A failed delivery is a meal you cooked, packed, drove and cannot charge for. Anything under about 97% success is costing real money, and the only way to fix it is to know which addresses are doing it.

Open the live demo to walk the routes and the driver view with sample data — no signup needed.