Solutions
Capturing delivery locations that drivers can actually find
A typed address is a description of where someone lives. A coordinate is a place a driver can navigate to. In much of the Gulf those are very different things, and the gap between them is measured in driver hours.
Why typed addresses fail here specifically
Postal-style addressing assumes numbered streets and a delivery network built around them. Large parts of the Gulf are not organised that way: communities are large, towers share names, building numbers are inconsistent, and the useful unit is a pin rather than a line of text.
Dubai Municipality issues Makani numbers precisely because of this — a ten-digit code identifying a specific entrance. Their existence is the clearest evidence that written addressing alone does not resolve reliably here.
The operational consequence is that a round planned on text addresses generates phone calls, and each call stops a driver and interrupts someone in the kitchen at the same time.
Capturing it once, properly
Ask at signup, before payment
A customer mid-signup shares a pin without hesitation. The same request by message a week later competes with everything else in their inbox.
Offer search and pin together
Address search finds the area quickly; dragging the pin fixes the entrance. Neither alone is sufficient.
Capture access notes as a field
Gate code, tower, reception, where to leave the bag — structured rather than buried in a chat thread nobody can find at six in the morning.
Let the customer correct it
A self-service update that takes effect on future manifests immediately, because an address only the office can edit goes stale.
Carry it into every manifest
So the driver taps through to navigation rather than reading an address aloud down the phone.
What this uses, and what it costs you
Address search is powered by Google Maps and requires your own API key, which is a paid Google service billed to you rather than something we bundle. Without a key configured, typing an address, pasting a shared Maps link and the driver’s navigation links all still work — you simply lose the autocomplete.
A practical warning learned the hard way: restrict that key to the API you need and to your server, not by HTTP referrer. A referrer restriction blocks server-side calls, which is a confusing failure because it looks like a broken integration rather than a configuration choice.
Limits worth stating
This captures a location. It does not verify that anyone lives there, does not validate an address against a postal database, and does not detect that a customer has moved — that remains a human update.
It is also not geofencing. There is no automatic rejection of signups outside your service area, so deciding and enforcing your boundary stays a business process.
And precision at capture does not help if the manifest is exported. A pin recorded correctly in March is useless on a printed sheet from a round that was planned before the customer corrected it.
Common questions
- Do I need my own Google Maps API key?
- Yes, and it is billed to you by Google rather than bundled. Without one, typing an address, pasting a shared Maps link and the driver’s navigation links all still work — you lose autocomplete, not the capability.
- How should the API key be restricted?
- To the specific API and to your server’s IPs. An HTTP-referrer restriction blocks server-side calls, which presents as a broken integration rather than as a configuration mistake and wastes a lot of debugging time.
- Does this stop signups outside my delivery area?
- No. There is no geofencing or automatic rejection, so defining and enforcing your service boundary remains a business process rather than something the address capture handles.
- Is a Makani number better than a pin?
- They serve the same purpose — resolving to a specific entrance. Either works; what matters is capturing one of them at signup rather than relying on a written community-and-tower description.
See it running against a real kitchen
The product pages show the actual admin loaded with a demonstration kitchen — production, packing, routes and the dashboard, exactly as an operator sees them.
Related reading
- GuidesPreventing meal delivery address errorsAddress 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.
- SolutionsMeal delivery software for Dubai kitchensThe operational core of a meal-plan business is the same everywhere. Four things about running one in Dubai are not, and each of them is the kind of detail that generic software gets quietly wrong.
- GuidesDelivery manifests and the driver handoverThe handover from kitchen to road is where a well-run morning gets undone. Almost every failure at this boundary is an information failure rather than a driving one.
- GuidesWhat to collect when a meal plan customer signs upEvery field you skip at signup becomes either a chase later or a guess. Two of them, added late, mean re-contacting your entire customer base.