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

Deliveroo publicly documents the mechanism, which makes it the easiest platform in this list for restaurant operators to reason about. Its help centre states that “Restaurants/stores will only appear on the Deliveroo if they are within the delivery radius of the post / area code the customer has entered”, and, more importantly, that “Sometimes the delivery radius of a restaurant/store will be reduced when there is a shorter supply of riders”. The radius belongs to Deliveroo, it contracts with rider supply, and it contracts without notifying the site.

A radius reduction is invisible to every availability measure, including ours. A site whose radius has quietly halved contributes nothing to our own downtime figure for Deliveroo in the UAE (2.28 percent of stated trading hours unavailable, July 2026), because the listing is open the whole time. It is open to fewer people. Coverage therefore has to be measured as its own quantity, from addresses rather than from the listing, and a chain that watches only uptime will never see this happen.

What does Deliveroo say its delivery radius is for?

Deliveroo gives a reason rather than a number, and it gives the same reason to customers and to merchants. Its “Deliveroo 101” article says “We’re all about quality so we have a set delivery radius that makes sure your food or products are never in transit for longer than they need to be.” Its merchant FAQ, including the United Arab Emirates edition, answers the question “How far do you deliver?” with a near identical sentence and one extra clause: “Customers located in your delivery radius will be able to place an order from your business.”

The word to notice is “set”. Deliveroo describes the radius as something it has, not as something a site chooses, and the merchant version makes the consequence explicit by defining who can order from you in terms of that radius. Everything else on this page follows from that framing. A site that believes it owns its delivery area will read a district going quiet as a bug in its own setup and will spend weeks looking for a control that, in most markets, it does not have.

Why does Deliveroo shrink the delivery radius when riders are short?

Deliveroo states this outright in the article it wrote for partners whose stores are not appearing: “Sometimes the delivery radius of a restaurant/store will be reduced when there is a shorter supply of riders, to make sure that your food/product arrives on time and in good condition.” Read that as a design decision rather than an outage. Deliveroo would rather serve a smaller area properly than a larger area badly, so when the rider pool thins, the map contracts from the outside in.

The same mechanism surfaces in Deliveroo’s developer documentation, which is useful because it shows how the platform models the state internally. A site carries a visible flag, and the documentation says “If the value of the visible flag is set to false, Deliveroo cannot currently deliver from this site”, noting that this may occur when there are no available riders. Alongside it sits distance, defined as “The straightline distance to the Restaurant in meters”. So rider supply, visibility and distance are all first class concepts on Deliveroo’s side, and none of them is a setting on yours.

Can a Deliveroo site set its own delivery radius?

Only if it is delivering the orders itself. Deliveroo’s merchant FAQ states the exception plainly: “Marketplace+ Partners that are delivering orders through their own riders will be able to set their own delivery radius.” That is the dividing line. On Deliveroo’s own logistics the radius is Deliveroo’s. On your logistics it is yours, because you are the one who has to reach the customer.

Where that control appears as an actual tool, it is narrower still. The “Delivery settings” feature lives in the Hub for partners with their own riders in “the United Kingdom, Ireland, France, Italy and Belgium”, where it lets you “Increase your site’s delivery radius” and “Select delivery distance by moving the slider”, with up to five delivery areas in some of those markets and postcode level selection for UK partners outside Northern Ireland. It also carries a warning that catches people out: “once you select your preferences on delivery settings, you will have a circular delivery area and cannot revert back to your previous delivery area”. A bespoke shape traded for a circle does not come back.

How does Deliveroo calculate the delivery time a customer sees?

Deliveroo publishes the arithmetic, which almost no platform does. Deliveroo defines prep time as “how long it takes restaurants to get an order ready for pickup by a rider”, and then gives the formula for what the customer is shown: “EOD = time to prep food + time to load vehicle with food + time to travel to customer”, with a worked example, “EOD 25 mins = 15 mins prep time + 3 mins loading + 7 mins travel”. EOD stands for estimated order duration.

The consequence for coverage is in the next sentence Deliveroo writes: “Restaurants with a shorter EOD will appear higher in the restaurant list.” Travel time is a term in that sum, and travel time grows with distance, so a customer at the edge of your radius does not merely wait longer, they see you ranked lower than the same food from a nearer kitchen. There is a ring of the city where you are inside the radius and losing anyway, and no availability check will ever flag it, because on that check you are present.

Does Deliveroo tell you when your radius has been reduced?

We found no Deliveroo page that promises a notification, an alert, a log or a history of radius changes to the partner. The help centre explains that reductions happen and why they happen. It does not say the partner will be told, and we are not going to invent a mechanism Deliveroo has not published. Treat the absence as the working assumption: if the radius moves, you learn it from customers or you learn it from measurement.

That is the whole reason this failure survives so long. A customer outside the live radius is not shown an apology or an error. Your restaurant is simply not in their list, so they order something else, no complaint is filed, and no row is written anywhere in your systems. The revenue does not fall off a cliff, it leaks district by district, and by the time it is large enough to notice it looks like a marketing problem rather than a geography problem.

How should a Deliveroo operator check coverage rather than guess?

Check from the customer side, at addresses you care about, at the hours that carry your revenue. Because Deliveroo has told you the trigger is rider supply, the readings that matter are the ones taken when riders are scarce, which means Friday and Saturday evenings and any night the weather is bad. A single reading tells you the current shape. Repeated readings at the same addresses are what separate a district that is genuinely gone from one that only drops at peak, and only the second of those is a supply conversation.

Record the quoted time next to the availability result, because Deliveroo’s own formula makes that number the second half of the story. Reading both at booked hours, and keeping the per zone history that turns one bad evening into a pattern, is what Kitchain (kitchain.co) does with Coverage. Our fuller profile of the platform, its markets and what we watch on it lives at https://kitchain.co/aggregators/deliveroo/.