Why your delivery zone should follow roads, not a circle on a map

If you run delivery for your own restaurant, you've probably drawn your delivery zone the same way most people do: pick a number — three miles, five miles — and picture a circle around your kitchen. Anyone inside the circle gets delivery. Anyone outside doesn't.

The problem is that a circle doesn't know your town. It doesn't know that the "three miles" on one side of your restaurant is a straight shot down a main road, and the "three miles" on the other side is across a river with the nearest bridge two miles out of the way. It doesn't know about the highway that cuts your neighbourhood in half, or the one-way streets that make a short trip home take twice as long as it should.

A circle measures distance as the crow flies. Your driver doesn't fly. Your driver drives. And drive time — not straight-line distance — is what actually determines whether an order arrives hot, on time, and worth the trip.

What a bad delivery zone actually costs you

This isn't just a theoretical annoyance. A delivery zone based on a plain radius costs real money in a few specific ways.

You say yes to orders you shouldn't. A customer three miles away as the crow flies might be a 22-minute drive once you account for the one bridge, the school-zone crawl, and the two sets of lights. By the time the order arrives, the fries are soggy, the customer is annoyed, and you've tied up a driver for half an hour on a $14 order.

You say no to orders you should take. Meanwhile, a customer just outside your circle — but on a fast, direct road — could be a 9-minute drive. You're turning away an easy, profitable order because it happens to sit slightly past an arbitrary line on a map.

Your drivers waste time on edge cases. When the boundary doesn't match reality, your staff end up making judgment calls order by order — "is this one worth it?" — which slows down the phone, slows down online orders, and creates inconsistency. One shift accepts an address, the next shift declines the same one.

Refunds and complaints pile up. Late deliveries because of poor routing are one of the most common sources of refund requests and bad reviews for delivery-driven restaurants. Every one of those costs you the order, the goodwill, and often a discount code to smooth things over.

None of this is a staffing problem or a driver problem. It's a mapping problem. And it's fixable without hiring anyone or buying routing software built for national chains.

The fix: measure drive time, not crow-flies distance

The better approach is to build your delivery zone around actual driving distance and driving time from your restaurant — factoring in the real road network, not a compass and a piece of string. Once you know the real drive time to every address in your area, you can draw a boundary that matches how your neighbourhood actually works: tight where roads are slow or indirect, generous where roads are fast and direct.

The good news is that you don't need to be a mapping expert or hire anyone to do this. You need two things: a list of addresses (or even just streets and zip codes across your delivery area) and a way to turn that list into real map coordinates and distances you can work with. That second part is what CSV2GEO does — you upload a spreadsheet, and you get back a finished spreadsheet with the location and distance information added. Nothing more complicated than that.

How it works

Step 1: Pull together your address list

Start with a list of addresses you want to test — this could be past delivery addresses pulled from your point-of-sale system or online ordering platform, or it could just be a grid of streets and cross-streets across your town if you're planning a zone from scratch. Either works. Put them in a simple spreadsheet, one address per row.

Step 2: Upload the file

Log in, upload your spreadsheet, and choose the option for driving distance and drive time from your restaurant's address. You don't need to format anything specially or write any formulas — the file goes in as-is.

Step 3: Let it process

The system reads through every address, works out its exact location, and calculates the real driving distance and estimated drive time from your kitchen. For a typical restaurant's delivery list — a few hundred to a few thousand addresses — this takes minutes, not hours.

Step 4: Download your results

You get back the same spreadsheet, now with extra columns showing distance and drive time for every address. No new software, no dashboard to learn — it opens in whatever you already use to open a spreadsheet.

Step 5: Draw your real boundary

Sort the results by drive time instead of straight-line distance. Now you can see, address by address, where your true 15-minute zone ends and where it doesn't. You'll likely find your zone isn't round at all — it's a lopsided shape that follows your fastest roads and pulls back around slow crossings, one-way clusters, and anything that splits your town in two.

Step 6: Update your ordering system and repeat monthly

Once you've drawn the new boundary, update it in your online ordering platform and delivery apps. Then, because roads change, new addresses come online, and your own order volume shifts over time, run the same check again next month or next quarter to keep the zone accurate rather than letting it quietly drift out of date.

What this actually costs

This is where a lot of restaurant owners expect a big number, because most tools built for "route optimisation" are priced for national chains. This isn't that.

The Lite plan is $19 a month and covers 21,000 US addresses. A single restaurant checking its delivery zone — even a busy one running a few thousand orders a month, plus a batch of test addresses to redraw the boundary — will use a small fraction of that allowance. There's no setup fee, no contract, and no minimum term. You can cancel any month you don't need it.

Compare that to the cost of one badly routed delivery: a refunded order, a driver's wasted half hour, a one-star review that costs you future orders. The subscription pays for itself the first month it saves you from accepting even a handful of orders you shouldn't have taken — or from finally saying yes to nearby customers you'd been turning away for no good reason.

Objections, answered

"I already have a delivery radius set in my ordering app." Most ordering platforms only let you set a radius or a rough polygon you draw by eye. Neither of those uses real drive time. This process gives you the data to draw a smarter polygon inside that same app — you're not replacing your ordering system, you're improving the boundary you feed into it.

"This sounds like something for big chains, not a single restaurant." It's actually the opposite. Big chains build custom routing systems because they have the budget and the engineering staff. A single restaurant needs something simple and cheap that does one job well — this is built for exactly that gap.

"I don't have a clean spreadsheet of my delivery area." You don't need a perfect one. A rough grid of streets and zip codes across your town works fine for the first pass. Past delivery addresses from your ordering history work even better once you have them.

Frequently asked questions

Is this hard to set up if I'm not techy at all? No. If you can attach a file to an email, you can use this. You upload a spreadsheet and download a finished one — there's no software to install and no account settings to configure beyond logging in.

What happens if an address is messy or incomplete? Most real-world addresses — missing zip codes, odd abbreviations, apartment numbers written differently — are still handled correctly. For the small number that can't be matched confidently, they're flagged in the results so you can check them by hand rather than being silently dropped or guessed at.

Do I need special hardware or a routing device? No. This isn't a device or an app for drivers — it's a one-time (or monthly) data process that tells you the drive time and distance for a list of addresses, which you then use to draw or update your delivery boundary.

Can I cancel if a slow month means I don't need it? Yes. It's billed monthly with no contract. If you skip a month, you just resubscribe when you're ready to re-check your zone.

Will this replace my delivery driver app or routing software? No, and it's not meant to. This handles the mapping and distance calculation that feeds into your delivery zone decisions. Your ordering platform and driver app still handle turn-by-turn navigation and dispatch.

Is my customer address data kept private? Yes. Your uploaded spreadsheet is used only to process the addresses you send and is not shared, sold, or used for anything beyond returning your results.

How often should I actually re-check my delivery zone? Most restaurants find a quarterly check is enough, with a re-check any time there's a major road change nearby — a new bridge, a closed street, a new development — or when order volume shifts meaningfully in one part of town.

Related Articles

• Quoting jobs by real driving distance, not guesswork
• Mapping a service radius that keeps crews on schedule
• Territory mapping for a mobile service business
• Geocoding without engineers: an ops guide
• The real cost of running your own geocoder

---

*I.A. / CSV2GEO Creator*