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

DoorDash treats delivery distance as a rule you write rather than a shape you draw, and restaurant operators who expect a polygon are surprised twice. Its merchant help states that “Delivery distance rules assign orders to Dashers when customers fall within a specified straight-line radius from your store”, that “Rules must be set as a distance range in whole miles (for example, 5–10 miles)”, and that distance “is measured ‘as the crow flies,’ not by driving route”. Straight lines and whole miles are a coarse instrument in a city built around a river or a motorway.

The article that says all this is titled “What is the Delivery Distance for Flexible Fulfillment (Self-Delivery)?”, and the title is the first thing to notice. These rules exist for merchants who deliver their own orders and want DoorDash to take some of them. If DoorDash is delivering everything for you, this is not the screen your coverage question lives on, and mistaking one for the other sends operators down the wrong path for weeks.

What does a DoorDash delivery distance rule actually do?

It hands an order over. The rule does not decide whether a customer can order from you, it decides who carries the food once they have. DoorDash’s own phrasing is that the rules “assign orders to Dashers when customers fall within a specified straight-line radius from your store”, and its stated purpose is written from the merchant’s side: to “Reach customers farther from your store without sending your own drivers long distances”, to “Expand delivery coverage while keeping existing self-delivery operations unchanged”, and to “Increase order volume without increasing driver travel time”.

That framing is the key to reading the whole feature. Flexible Fulfillment is a way of buying reach from DoorDash’s fleet at the edge of your own. A merchant that sets a 5 to 10 mile rule is saying that inside five miles its own drivers cope, and between five and ten miles it would rather pay for a Dasher than send a driver across town. Coverage therefore has two layers on this platform, and a district can go quiet because either layer changed.

Why does DoorDash measure distance “as the crow flies”?

Because a straight line ignores everything that makes a city slow. DoorDash says so itself, in a warning printed directly under the rule: “Straight-line distance may differ significantly from road distance due to geography”. Two addresses exactly six miles from your store in a straight line can be a twelve minute drive and a forty minute drive, depending on whether there is a bridge, a rail line, a river or a one way system between you.

The failure this produces is not a missing store, it is a badly chosen one. A rule tuned to the easy side of your map will be far too generous on the hard side, and the orders it lets through from the hard side are the ones that arrive late and collect the bad reviews. Because the rule is expressed in whole miles, you cannot tune it finely either. You get five or six, not five and a half, so the granularity of the instrument is coarser than the geography it is trying to describe.

Can DoorDash delivery distance rules be combined with custom zones?

No, and DoorDash states the conflict plainly. Under Limitations it says “Delivery distance rules can’t be used with custom delivery zones” and then repeats the reason: “Flexible Fulfillment requires a straight-line delivery radius in whole miles and isn’t compatible with custom zones”. It adds one more constraint without giving a figure, saying that “Rules must stay within platform distance limits”.

That is a genuine trade off and it is worth deciding deliberately rather than discovering. Custom zones let you describe your city honestly, following the roads and skipping the districts your drivers hate. Distance rules let you hand the far edge to DoorDash. You cannot have both on the same store. Any chain running a mixed estate should expect its stores to fall into two groups that behave differently, and should stop trying to explain that difference as a bug.

What does DoorDash do about peak hours?

It gives you a schedule rather than a shrinking map, which is unusual in this list. Alongside distance rules sit Time of Day rules, and DoorDash describes them as follows: “Time of day rules assign all orders to Dashers during specific times on specific days.” The stated reasons are operational and blunt, to “Manage delivery volume during peak periods” and to “Reduce staffing strain during high demand or avoid paying for drivers during low-volume hours”.

When both rule types are live, DoorDash publishes the combined logic: “During the specified time windows, all orders are fulfilled by DoorDash and assigned to Dashers. Outside of those time windows, orders that fall within the designated delivery distance radius are also fulfilled by DoorDash.” So your Friday evening is not the same product as your Tuesday afternoon, by design and by your own configuration. One more limit catches people: “Rules must fall within your store’s operating hours on DoorDash”, so a rule cannot extend trading beyond the hours already set in the Merchant Portal.

Why can a customer inside your DoorDash radius still not see the store?

Because a delivery distance rule is a fulfilment rule, not a visibility rule, and nothing in DoorDash’s help article claims otherwise. Whether your store appears for a given address depends on DoorDash’s own marketplace behaviour, which that article does not describe, and we are not going to describe machinery we have not seen documented. What is documented is that the rules you control operate on assignment, not on display.

The practical result is a gap between what you configured and what a customer at a specific address is offered, and it is a gap no merchant screen closes. Your Merchant Portal shows the rule you wrote. It does not show what a person standing in that postcode was shown at eight on Friday. Those are two different facts, and only one of them is the one that generates revenue.

How should a DoorDash operator verify coverage?

Sample addresses at the hard edges of the map rather than in the easy directions, because the straight-line rule is by definition most wrong where geography is most awkward. Take the far side of the river, the wrong side of the interchange, and the neighbourhood your drivers already complain about, and read what a customer there is actually offered, including the quoted wait. Do it inside your Time of Day windows and outside them, since DoorDash has told you those two states differ.

Repeating that reading at fixed addresses is what turns a suspicion into a record, and keeping the per zone history so that a bad Friday and a lost district look different is what Kitchain (kitchain.co) does with Coverage. Our wider profile of this platform, including the markets it runs in, is at https://kitchain.co/aggregators/doordash/.

One last thing to write down before you change anything. Record the rules currently in force on each store, both the distance range and any Time of Day windows, with the date you read them. DoorDash’s Merchant Portal shows the present state and not the history, so a chain that adjusts rules across dozens of stores has no way afterwards to correlate a change in orders with the change that caused it. A dated snapshot of the configuration alongside a dated record of what customers were offered is what makes the next argument short.