Why Uber Eats says your restaurant does not deliver to an address you cover

Uber Eats is unusually direct about this, and restaurant operators should read its sentence twice. Its merchant help article “How do delivery zones work?” states that “Delivery zones are dynamic and determined by an algorithm that evaluates many factors that include cuisine type, location, distance, and expected total delivery times”. Dynamic means the zone is recalculated rather than drawn once. Cuisine type means two restaurants at the same address can be offered to different customers. Neither of those is something a merchant on Uber’s own delivery network can change.

The exception is stated in the same article. Restaurants that use their own delivery staff “set their delivery zones directly within their Uber Eats Manager accounts”, and they “set the delivery area that they feel comfortable fulfilling orders within”. So on Uber Eats there are two entirely different answers to the same question, and which one applies to you depends on who carries the food.

What does Uber Eats mean by a dynamic delivery zone?

It means the boundary is an output, not a setting. Uber’s stated purpose for zones is that they “ensure that customers enjoy high food quality with reliable service and speedy delivery”, and the four inputs it names are cuisine type, location, distance and expected total delivery times. Three of those four are things about you and your city. The fourth, expected total delivery time, moves with traffic and with courier supply, which is what makes the output move.

The cuisine input is the part worth dwelling on, because it has no analogue on any other platform in this set. If cuisine type is a factor, then the zone is not purely a logistics calculation about how far food can travel, it is partly a judgement about how far this kind of food should travel. Ice cream, sushi and pizza do not survive the same journey, and a platform optimising for food quality will not give them the same reach. A brand comparing its map with a neighbour’s and finding them different is not necessarily looking at a fault.

Can you set your own Uber Eats delivery area?

If you deliver your own orders, yes, and with more precision than most platforms allow. Uber’s help article says “Uber Eats now offers merchants with their own delivery staff the ability to customize the delivery area by radius, custom shape and postal codes”, and it walks through all three. Each of them lives in the same place: log into Uber Eats Manager, go to “Settings”, then “Delivery”, where you see the “current delivery area, associated delivery fee, and fulfillment time”.

The three area types work differently. “By radius” means picking the area type “Radius” from a dropdown and adjusting the distance. “By custom shape” gives you something rarer, an editable polygon: Uber tells you that “You will see a square shape centered around your restaurant”, and that you then drag the corners, or a point between them, to change the shape of the delivery zone. “By postal codes” uses the “Create Area” option with the area type “Postcode” and a multi select field. Each area carries its own delivery fee, its own minimum order value and its own fulfillment time, so a far district can be priced and timed differently from a near one.

Why do the three Uber Eats area types not behave the same way?

Because each of them describes a different thing about your city, and only one of them describes roads. A radius describes an ambition, a distance you are willing to travel in any direction, and it will always be simultaneously too generous in the hard directions and too mean in the easy ones. Postcodes describe administrative boundaries, which are stable and easy to reason about with your team but were drawn for the post office rather than for a rider on a scooter. A custom shape is the only one of the three that can follow a river, skip an industrial estate or stop at a motorway.

That is why the shape option is worth the twenty minutes it takes. Most operators pick radius because it is one number and it is done, then spend a year absorbing late deliveries from the one direction where their radius crosses something slow. If you are going to use radius, at least set it by the worst direction rather than the average one, and use per area fees and fulfillment times to make the far ring honest about what it costs and how long it takes.

Why does an Uber Eats customer at a covered address still not see you?

Because the zone was recalculated, and nothing told you. On Uber’s own delivery network the zone is described as dynamic, which is Uber’s way of saying it is not stable between one evening and the next. There is no radius you set that could have been wrong, and there is no configuration to audit. Your listing did not go offline, your hours are correct, and a customer three streets closer is being offered you normally.

That is why this failure is nearly invisible from inside the business. The customer outside the current zone sees no message about your restaurant, because your restaurant is simply not in the list they were shown. They order from someone else. Nothing reaches your tablet, your POS or your Uber Eats Manager, and the only trace is a slow decline in orders from one part of the map, which reads like weak demand rather than like a boundary that moved.

Does Uber Eats tell you when your zone changes?

We found no Uber page promising a notification, a change history or an alert to merchants when a dynamic zone is recalculated. The article explains that zones are dynamic and lists the factors. It does not say the merchant is informed, and we are not going to invent a mechanism Uber has not published. If you are on Uber’s delivery network, treat the zone as unobservable from inside and observable only from a customer address.

For self delivery merchants the situation reverses. Your area is exactly what you last saved in Uber Eats Manager, so the useful check is whether the saved area still matches the area your drivers can actually serve at the hours you are busiest. An area that was reasonable when you drew it and unreasonable now produces late orders and poor ratings rather than invisibility, which is a different symptom with the same root.

What should you check first if a district went quiet on Uber Eats?

Establish which of the two systems you are in, because everything else follows from it. If Uber Eats Manager has a Settings then Delivery screen showing a current delivery area with a fee and a fulfillment time, you are a self delivery merchant and the area is yours. If it does not, the zone is Uber’s and dynamic, and the question is not what you set but what customers are being offered.

Then read the map from the outside. Pick real addresses in the districts that matter, at the hours they order, and record whether your restaurant appeared and what wait it was quoted with. Because Uber names expected total delivery time as one of the zone inputs, the quoted wait and the availability result are two halves of the same measurement and belong in the same record, which is how Kitchain (kitchain.co) Coverage captures them at kitchain.co.

One last thing worth doing while you are in there. Uber’s custom shape editor starts you with a square centred on the restaurant, and a surprising number of merchants save that square without dragging its corners. A square is a worse description of a real delivery area than almost any shape you could draw yourself, and it costs money in exactly the corners nobody looks at. What we watch on this platform more broadly is set out at https://kitchain.co/aggregators/uber-eats/.