Guides

Preventing meal delivery address errors

Address problems look like small individual incidents and are actually one of the largest recurring costs in a delivery operation, because each one consumes two people at once.

Why written addresses fail in the Gulf

In much of the region a written address does not resolve to a door. Communities are large, towers share names, and building numbering is inconsistent. Dubai Municipality issues Makani numbers precisely because postal-style addressing does not work reliably here.

The consequence is that a delivery round planned on text addresses generates phone calls, and every call stops a driver and interrupts someone in the kitchen simultaneously.

Fixing it at the source

  1. Capture a pin at signup

    Ask for a shared map location or a Makani number when the customer joins, while they are motivated and paying attention.

  2. Store access notes as a field

    Gate codes, reception instructions, which tower, where to leave the bag. In a structured field, not in a chat thread.

  3. Let the customer correct it

    A self-service address update takes effect on future manifests immediately. An address only the office can edit goes stale.

  4. Generate manifests live

    A list exported at 6am stops being true the moment anything changes. The driver should read the current record.

  5. Record failures honestly

    A stop marked failed with a note is a data point. A stop quietly left open is an argument next week.

The measurement that justifies the work

Count the calls. Most operators are surprised by how many stops per week involve a driver phoning for directions, because each one feels minor in isolation.

At twenty-odd stops a round, a handful of ambiguous addresses is a meaningful share of the driving day — and unlike food cost, it is a cost with no revenue attached to it at all.

Common questions

Is a Makani number better than a typed address?
For finding a door in Dubai, yes. It resolves to a specific entrance, which is precisely what a written community-and-tower address often does not. A shared map pin works equally well.
Should drivers be able to correct addresses?
They should be able to flag a problem; corrections are better made by the customer or the office so the change is deliberate and attributed. A driver editing under time pressure invites new errors.
Why do exported manifests cause address problems?
Because an exported list is a copy, and it stops being true the moment anything changes after printing. An address corrected at ten o’clock never reaches a sheet printed at six.

See how this works in practice

The home page walks through the same mechanics against a real admin loaded with a demonstration kitchen: production, packing, routes and the customer side.