A delivery minimum should change by zone when the cost of serving that zone changes enough to make the current minimum uneconomical. Start with the contribution from a basket at the minimum, subtract the delivery cost the restaurant actually bears, and compare the result across zones. Then check whether a higher minimum would stop too many customers from ordering.
Distance is a useful starting point, not the whole answer. A short trip across a congested area can cost more than a longer trip on an easy route. A single restaurant-wide minimum may be simple to explain, but it can also leave expensive orders underpriced or make nearby customers buy more than they need.
Estimate the cost of serving each zone
Draw your current delivery areas on a map and name them in a way your staff can recognize. If your ordering system uses distance bands, note the distance and how it is measured. If it uses custom boundaries, check the actual streets or addresses at each edge. Do not assume a radius on a map matches the driver's route.
For each zone, collect the inputs that change with an order:
- Delivery expense: Ask your delivery provider for its charge by area, time and order type. If you use your own drivers, estimate the labor and vehicle costs attributable to each delivery, including waiting and return time where relevant.
- Food and packaging: Use your own recipe and packaging costs to estimate how much of a typical basket remains after those expenses. Include items that tend to be ordered for delivery, not just your best-margin dishes.
- Payment processing: Ask your processor how the fee is calculated and what it applies to. A quoted processing rate is one expense, not the all-in cost of taking and delivering an order.
- Guest delivery charge: Record what the customer pays separately from what the courier costs you. A $3 charge can offset $3 of expense, but the guest still sees it as part of the price.
- Exceptions: Look for peak-period surcharges, failed deliveries, refunds and other recurring costs. Use an average allowance when you have enough history, and keep unusual events visible rather than hiding them in the average.
Pull order values and delivery charges from your ordering records, and compare them with delivery invoices or driver records for the same period. If costs vary by lunch, dinner or weekend, separate those periods before setting a threshold. A zone average can conceal a costly Friday rush.
For a wider view of direct-order expenses, use the guide to comparing orders on contribution. The zone decision is narrower: it asks whether a particular delivery basket covers the costs associated with serving that area.
Compare contribution at candidate minimums
Use the minimum as the basket value in your first calculation. That tests the order most likely to be marginal. Contribution here means the money left after the listed per-order costs; it is not net profit and does not cover every cost of running the restaurant.
Hypothetical example: A restaurant is considering three zones and a $3 guest delivery charge in each. Food and packaging cost 40% of the basket, processing costs an assumed 3% of the basket, and delivery costs the restaurant $8, $11 or $14 per order by zone. Assume the restaurant receives the full $3 guest charge and that processing is calculated only on the basket. These are decision assumptions, not vendor quotes.
The table subtracts those variable costs and adds the guest charge. Fixed costs and exception costs are excluded. For example, at a $20 basket in the middle zone, the calculation is $20 minus $8 for food and packaging, minus $0.60 processing, plus $3 from the guest, minus $11 for delivery: $3.40 remains.
| Zone | $15 minimum | $20 minimum | $25 minimum |
|---|---|---|---|
| Near: $8 delivery | $3.55 | $6.40 | $9.25 |
| Middle: $11 delivery | $0.55 | $3.40 | $6.25 |
| Far: $14 delivery | −$2.45 | $0.40 | $3.25 |
Each cell is the estimated contribution from an order exactly at that column's minimum. A negative number means the listed variable costs exceed the basket contribution and guest charge. A positive number still has to contribute toward fixed costs and any exceptions.
Suppose this restaurant wants at least $3 per minimum-sized order toward those excluded costs. Under these assumptions, $15 meets that target in the near zone, $20 meets it in the middle zone, and $25 meets it in the far zone. Those are starting thresholds, not proof that customers will accept them. If far-zone demand falls sharply at $25, the owner should revisit the delivery charge, delivery arrangement or zone rather than assume the table settles the decision.
Actual orders can exceed the minimum, and their item mix may differ from the 40% assumption. Recalculate with your own numbers and test a less favorable mix. Also check whether processing applies to delivery charges, tips or other amounts; if it does, include those fees in your calculation.
Fixed software costs belong in the broader operating picture, even though they do not change with each extra order in this table. As of November 2026, Fleksa's plans list Fix at $199 per location per month, with 0% Fleksa commission on direct online orders. Processing, delivery or dispatch, hardware or add-ons, and applicable sales tax are extra. Confirm the current quote and who pays each delivery charge before comparing totals.
Check friction at zone boundaries
A minimum that works on paper can feel arbitrary at checkout. Imagine two addresses on opposite sides of a zone boundary. One sees a $15 minimum and the other sees $20, even though their trips may be similar. The difference may be justified by the delivery arrangement, but the customer needs to see the requirement before spending time building a basket.
Walk through your ordering flow from the guest's point of view. Enter representative addresses near both sides of each boundary and check the zone, minimum and delivery charge shown. Try a basket below the minimum, exactly at it and above it. The customer should be able to understand how much more is needed and whether adding an item will satisfy the requirement.
Run these checks in a simulation or other non-live setup that cannot take a real payment, send a guest message or dispatch a courier. If your system has no safe practice mode, ask the provider how to verify the flow without triggering those actions. A simulation can reveal a confusing message or boundary assignment; it cannot show how real customers will respond.
For a live service pilot, agree on the zones, dates and staff responsibilities first. Watch real orders and abandoned checkouts only through the normal live ordering process. Compare results with a similar prior period where possible, while noting changes in hours, promotions and demand. A small sample can suggest a problem, but it cannot isolate the effect of the minimum on its own.
Ask your ordering provider whether it can set different minimums and charges by zone, show the requirement early, and report abandoned baskets by area. Also ask how it handles overlapping boundaries and addresses it cannot place. Do not design a policy around a setting until you have seen how it works in your setup. Your restaurant website should also give customers a clear path to check their address and ordering terms.
Review thresholds on a schedule
Set a review date when you make the change. Check weekly during an initial pilot, then monthly once the policy has settled. Review sooner if a courier changes its charges, your delivery area changes, or an unusually busy period makes the current estimate unreliable.
For each zone, track order count, basket value, guest delivery charges, delivery expense and contribution after the variable costs you can measure. Add refunds and failed-delivery costs when they occur. Compare orders at or near the minimum with larger baskets; an attractive average can hide losses on the smallest deliveries.
Keep a simple decision record:
- Write down the current minimum, guest charge, delivery cost and contribution assumption for each zone.
- Recalculate the sensitivity table when a meaningful input changes. Include a reasonable allowance for exceptions if you have usable history.
- Review customer friction alongside the math. Look for drop-offs at the address or minimum message and ask staff what questions customers raise.
- Change one part of the policy at a time where practical, record the date and review the result against your target.
A higher minimum is not the only response to an expensive zone. You can assess a different guest delivery charge, a smaller service area, limited delivery hours or another delivery arrangement. Each option changes the customer's offer or your costs, so calculate it separately and confirm the settings your provider supports. For contract or tax treatment, consult a qualified adviser.
Next step: Use the zone checklist above with one month of your own records, then ask Fleksa about restaurant online ordering, zone settings and verified US availability for your location. Bring your boundary examples and ask to see how the guest-facing minimum would appear.
Frequently asked questions
Should every delivery zone have a different minimum?
No. If the cost of serving two zones is similar and one minimum meets your contribution target in both, keeping the same threshold may be easier for customers and staff. Review it when costs or ordering patterns change.
Does a delivery fee replace a minimum order?
Not necessarily. A guest delivery charge offsets some expense, while a minimum sets the smallest permitted basket. Compare both together, including the total price the customer sees and any processing fees that apply.
What if a far-zone minimum causes customers to leave?
Check the size of the drop-off and whether other changes could explain it. Then recalculate alternatives, such as a different delivery charge or service area, rather than lowering the minimum without checking the cost of those orders.
