an area we have not drawn is not an area we refuse

Delivery priced by area is easy to describe and awkward to implement honestly, because three different situations look identical from inside a lookup that misses: the point is inside an area the business serves, the point is outside every area it serves, and the business has not drawn any areas at all.

A single not-found answer collapses all three, and the collapse lands on the newest business on the platform. Draw nothing yet, and every delivery order carrying a location is refused — the product looks broken on the day it is switched on, for a reason the operator cannot see in the interface.

The change separated them. Inside an area, the quote carries that area's price adjustments, timing and minimums. Outside every active area, the answer is an explicit refusal about coverage, which the surface renders plainly: we do not deliver here. With no areas configured, the quote falls back to the flat economics the business configured.

Then the same guard went into the path that prices an order when payment starts. Without it the two paths disagreed: the quote priced while the order hard-blocked, or the reverse. A quote and a committed price are the same claim made twice.

Cost: an unfinished configuration now yields a less precise answer than a drawn map would, and the surface must keep "we do not serve there" visibly distinct from "we have not said where we serve".

What it proves: the team treats a missing configuration as a stated default with an owner, not as an outage for the customer to discover.