Choose a delivery area by working backward from the experience you can reliably provide. Estimate the full time from order acceptance to arrival, calculate what each zone costs to serve, and set the boundary where both the customer promise and the order economics still work.
A circle on a map is a useful starting point, not the final answer. A neighborhood three miles away across a busy bridge may be harder to serve than one four miles away along a clear route. Start with a smaller area you can manage during a busy shift, then expand only when the evidence supports it.
Map travel times instead of drawing one circle
Divide the surrounding area into a few practical zones. Use streets, rivers, bridges and neighborhood edges that staff can recognize. For each zone, identify several representative addresses, including one near the outer edge. A single address beside the restaurant will not tell you much about a whole neighborhood.
Estimate travel time for the hours when delivery orders actually arrive. Check the lunch period, the dinner rush and any late-night window you plan to serve. Note routes that depend on a bridge, a railroad crossing, a difficult parking situation or a building where drivers regularly need extra time to reach the door.
Use a range rather than treating a map estimate as a promise. A zone that usually takes 10 to 15 minutes in light traffic may take considerably longer on a rainy Friday. Also consider the return trip: the customer sees the outbound journey, but the restaurant or delivery partner must have enough driver capacity for the next order.
Think about food quality as well as speed. A long trip may be acceptable for some packaged dishes but leave fried items limp or cold items warm. Review packaging and menu suitability before accepting orders at the edge. If the route is unpredictable, a narrower boundary or different service hours may be more useful than a generous radius.
Compare zone costs and customer promises
The following worksheet is a hypothetical planning example, not a vendor quote. The zones use estimated peak outbound travel times. The promise is the total time shown to a guest, not just the drive. Delivery fees are hypothetical charges paid by the guest; they do not include the price of food.
| Zone | Peak outbound travel | Guest delivery fee | Provisional arrival promise |
|---|---|---|---|
| Near: local streets | 8–12 minutes | $3 | 35–45 minutes |
| Middle: across town | 13–18 minutes | $4 | 45–55 minutes |
| Outer: beyond the bridge | 20–30 minutes | $5 | 60–75 minutes |
The table makes the tradeoff visible: the outer zone brings a higher guest fee and a longer promise, while its travel range is also wider. Those figures are starting estimates. Check whether your ordering setup can apply different fees and promises by zone, and whether it can restrict particular areas or hours.
Next, calculate the restaurant's expected contribution per order in each zone. Use your own menu mix and written delivery quotes. In this separate hypothetical cost comparison, assume an average $30 food order, $11 in food and packaging cost, and $2 in payment and other variable order costs. A quoted delivery charge to the restaurant is $7 in the near zone and $10 in the outer zone. Guests pay the fees shown above.
- Near zone: $30 food sale + $3 guest delivery fee − $11 food and packaging − $2 other variable costs − $7 delivery = $13 contribution per order.
- Outer zone: $30 food sale + $5 guest delivery fee − $11 food and packaging − $2 other variable costs − $10 delivery = $12 contribution per order.
These contributions include the stated variable costs and delivery charges. They exclude fixed costs such as rent and software subscriptions, as well as exception costs such as refunds, remakes and failed deliveries. They are not profit. The guest fee offsets part of the delivery expense, but it remains a cost to the customer and may affect whether the customer orders.
Under these assumptions, the outer zone contributes $1 less per order before fixed and exception costs and needs a longer arrival promise. That does not automatically rule it out. It does mean the operator should check demand, likely exceptions and the capacity needed to serve it before expanding. Estimate monthly order volume by zone, then multiply expected contribution by that volume; do not assume a large area will produce enough orders to cover its added burden.
Ask each delivery provider for a written quote that explains distance-based charges, peak surcharges, waiting time, cancellation charges and who handles a failed delivery. Compare those amounts with any guest fees you plan to charge. A quoted processing fee alone is not the all-in cost of operating the service. For a broader comparison of order economics, see the guide to comparing direct and marketplace orders.
Build the promise around kitchen and driver capacity
Travel is only one part of delivery time. The clock starts when the guest places the order and includes acceptance, preparation, packing, waiting for pickup, the journey and any delay at the destination. A short drive cannot make up for a kitchen that is already behind.
For each busy service window, estimate how many delivery orders the kitchen can prepare without disrupting dine-in and pickup. Count the shared bottlenecks: grill space, fryer baskets, packing staff and the counter area where bags wait. Then check how many drivers or delivery pickups are realistically available. The usable order capacity is limited by whichever part of that chain fills up first.
Set the guest promise using the slower periods you intend to serve, not a quiet afternoon. For example, a zone with a 15-minute drive might also need 20 minutes for preparation and packing and 10 minutes for pickup wait. That is already 45 minutes before allowing for normal variation at the destination. A 30-minute promise would not fit those assumptions.
Decide what staff should do when capacity tightens. Can they extend the displayed estimate, pause delivery, restrict an outer zone or stop accepting orders temporarily? Ask the ordering provider which controls are available and who can change them during service. A clear pause is better than continuing to accept orders with a promise the team cannot meet.
Also agree on responsibility at handoff. Staff need to know when an order is considered ready, where a driver collects it and whom to contact if pickup is late. If a third party handles delivery, ask how its pickup estimates and status updates reach the restaurant and the guest.
Check the boundary before a live pilot
Before opening a new zone, walk through the ordering and dispatch process with staff. Use a sandbox, demo or other clearly simulated setup to check representative addresses just inside and outside each boundary. Confirm the fee, available hours and displayed promise. Include an address near a bridge or boundary road and one in a building with a difficult entrance.
A practice scenario should not create a real card payment, send a guest message or dispatch a courier. Ask the provider how to simulate these steps safely. If a complete simulation is unavailable, review the remaining steps with the provider before taking live orders.
Then run a limited live service pilot with real orders only when the team is ready. Start with the nearer zones or a short set of hours, and add the outer edge in a controlled window. Brief staff on the boundary, the promise and when to pause orders. Make sure guests see the actual fee and estimate before placing an order.
Record more than the average drive. For each zone, track accepted orders, refused or unavailable orders, promised arrival windows, actual arrival times when available, late arrivals and the reason for delays. Note remakes, refunds and delivery exceptions separately. A zone with few orders can look good or bad by chance, so review individual incidents as well as totals.
At the end of the pilot, compare results against your own limits. Can the kitchen keep up during the busiest intended shift? Do arrivals usually fit the displayed window? Does the contribution still make sense after delivery exceptions? If not, shorten the boundary, change the hours, adjust the fee or promise, or improve the handoff before trying again. Avoid expanding simply because the map has empty space.
Choose software that supports the operating plan
Bring your zone worksheet to provider conversations. Ask how addresses are checked, how boundaries are entered, whether fees and estimates can vary by area, and how staff pause or adjust delivery during service. Ask what happens when an address sits on a boundary and how changes appear on your restaurant website.
Also separate ordering software from delivery fulfillment. Fleksa provides direct ordering software; it is not a courier fleet. Its Fix plan is listed at $199 per month per location with 0% Fleksa commission on direct online orders. Payment processing, delivery or dispatch, hardware and add-ons, and applicable sales tax are extra. See the Fleksa plans for pricing checked in November 2026, and confirm the current quote and setup for your location.
Once you have marked three candidate zones and estimated their busy-period costs, review Fleksa's restaurant online ordering and ask for a demonstration of how your proposed boundaries, fees and service pauses would be configured.
Frequently asked questions
What is a good delivery radius for a restaurant?
There is no single distance that fits every restaurant. Choose the boundary using peak travel time, food quality, delivery costs and the kitchen and driver capacity available during the hours you plan to serve.
Should every delivery zone have the same fee?
Not necessarily. A farther zone may cost more to serve, but a higher fee is also a customer cost. Compare written delivery quotes and expected order contribution, then check whether your ordering setup supports the fee structure you want.
When should a restaurant expand its delivery area?
Consider expansion after a limited live pilot shows that the current area can be served within its stated promises and at an acceptable contribution. Review late arrivals, refused orders and exceptions before adding another zone.
