★★★★★ 4.9 / 5 — 143 ratings

Revenue Per Mile: Delivery Profitability Analysis for Restaurants

Most restaurants measure delivery success by order count and total revenue. Both metrics can look healthy while the delivery operation quietly bleeds money. Revenue per mile shows you the truth.

Quick Answer: Revenue per mile is calculated as total delivery order revenue divided by total miles driven in delivery. A healthy restaurant delivery operation targets $8 to $14 per mile. Below $6 per mile, the operation is likely unprofitable after true costs. The metric enables data-driven decisions about delivery zones, minimum order values, batching strategy, and driver compensation. This analysis covers calculation, benchmarking, and the four levers that move the number most.
DL
David Laurent
Delivery Economics Specialist, KwickOS
Published May 27, 2026 · 15 min read

Here is a scenario that plays out in restaurant delivery operations more often than operators realize. A restaurant is doing 75 delivery orders per night with an average order value of $38. Gross delivery revenue is $2,850 per night. That looks like a successful delivery program. But when you map those 75 deliveries against the total miles driven to complete them, and divide revenue by miles, you may find your operation running at $5.80 per mile. At that revenue per mile, after accounting for driver compensation, fuel, vehicle wear, insurance, and software costs, you may be clearing less margin on delivery than you are on a dine-in table that turns twice.

Revenue per mile does not replace other delivery metrics. But it connects the physical reality of your delivery operation, the miles your drivers actually travel, to the revenue those miles generate. That connection reveals inefficiencies that no other single metric exposes.

The Formula: Building It From Scratch

Revenue Per Mile Calculation

Revenue Per Mile = Total Delivery Revenue / Total Miles Driven

Example:
75 orders x $38 avg = $2,850 revenue
Total miles driven = 312 miles (all drivers combined)
Revenue per mile = $2,850 / 312 = $9.13 per mile

The revenue figure should be the full order value, not just the delivery fee. You are assessing the economics of the entire delivery transaction, including the food margin that the delivery enabled. The cost structure analysis comes separately. Revenue per mile is a gross metric that you then compare against your cost per mile to determine net margin per mile.

Calculating Cost Per Mile

Cost Per Mile Calculation

Driver Compensation per Mile: Mileage rate or hourly rate / avg mph
Vehicle Cost per Mile: (Fuel + Maintenance) / total miles
Insurance per Mile: Annual premium / annual miles driven
Overhead per Mile: (Software + dispatcher time) / total miles

Example total cost per mile:
Driver: $0.38 | Vehicle: $0.22 | Insurance: $0.14 | Overhead: $0.09
Total cost per mile = $0.83

With revenue per mile of $9.13 and cost per mile of $0.83, your delivery operation generates $8.30 per mile before food cost. Multiply by food cost percentage (typically 28 to 34 percent of order value), subtract that from revenue per mile, and you have your delivery margin per mile. This number should be positive and healthy. If it is not, you have found the problem before it becomes a crisis.

Benchmarks: Where Do You Stand?

Revenue Per MileAssessmentTypical Cause
$12 - $18+ExcellentTight zone, high AOV, strong batching
$9 - $12HealthyWell-managed zone and batching
$6 - $9MarginalZone too wide or AOV too low
Under $6Loss-likelySignificant structural problem

The Four Levers

Lever 1: Delivery Zone Optimization

This is the most powerful lever and the one that operators are most reluctant to pull. Extending your delivery zone to capture more potential customers seems like a revenue strategy. In reality, every mile you add to your maximum delivery radius generates lower revenue per mile orders because those far-edge deliveries involve more driving for the same or similar order values.

Run a mile-band analysis: segment your deliveries by distance from the restaurant in one-mile bands and calculate average order value and total miles per delivery for each band. You will almost certainly find that deliveries in the 4 to 6 mile band have similar or lower average order values as 1 to 2 mile deliveries but dramatically higher miles driven. The revenue per mile for those outer-band deliveries may be half of what you earn on inner-zone orders.

This is the core insight behind delivery zone optimization. Cutting the outer mile or two of your delivery zone rarely reduces total order count by more than 8 to 12 percent while increasing revenue per mile by 25 to 40 percent. The math almost always favors a tighter zone.

Lever 2: Minimum Order Value

Low-ticket delivery orders are disproportionately damaging to revenue per mile. A $14 order delivered 2.5 miles generates $5.60 per mile. A $42 order delivered the same 2.5 miles generates $16.80 per mile. The miles driven are identical. The revenue difference is three times.

Setting a meaningful delivery minimum, typically $18 to $25 depending on your price point, eliminates the subset of orders that pull your revenue per mile average down significantly. The objection is that you will lose those orders. You will. But you will not lose much net margin from them because they were barely generating any to begin with. What you gain is a higher average revenue per mile on every remaining order, better driver utilization during peak hours, and shorter delivery times because drivers are completing higher-value runs instead of low-value ones.

Lever 3: Order Batching

Order batching is a revenue-per-mile multiplier. When a driver carries two orders in one run, the revenue per mile for that run is approximately 1.6 to 1.8 times higher than a single-order run to the same area. The math is simple: two $35 orders together generate $70 of revenue on a combined route that might cover 5.5 miles instead of two separate 3-mile routes totaling 6 miles. Revenue per mile jumps from $11.67 on two separate runs to $12.73 on a batched run.

The caveat is that bad batching destroys revenue per mile and customer satisfaction simultaneously. Sending a driver 4 miles north for the first delivery and then 4 miles south for the second is not batching. It is two separate deliveries on one run with a 4-mile detour in the middle. Good batching requires intelligent batching algorithms that cluster orders geographically and consider cook times so both orders are fresh when they reach their respective customers.

Lever 4: Average Order Value Growth

Increasing average order value without changing delivery zone or mileage is the cleanest improvement to revenue per mile. Every dollar added to average order value adds a dollar to the numerator of the revenue per mile calculation with no change to the denominator. Menu optimization for delivery, strategic upsell prompts in the ordering flow, and bundle offers designed for delivery all increase AOV without additional operational complexity.

An operation running 80 deliveries per night with a $36 average order value and a 280-mile daily total generates $10.29 per mile. If AOV increases to $42 through effective upsell design, revenue per mile jumps to $12.00, a 16.6 percent improvement on every operational metric that flows from revenue per mile, purely from menu and ordering flow optimization.

KwickSpot tracks total miles driven per driver, per shift, and per delivery zone. Calculate revenue per mile automatically from your KwickOS order data and GPS mileage logs. No spreadsheets required.

See KwickSpot delivery analytics →

Real Story: Frank Andersen, Minneapolis, MN

Frank runs a Scandinavian-inspired cafe in Minneapolis's Uptown neighborhood with a delivery operation he had been proud of: 85 to 90 orders per night, $3,200 per night in delivery revenue. By every measure he was tracking, the business was growing.

When Frank started tracking miles for the first time after implementing KwickSpot, the numbers surprised him. His three drivers were collectively covering 410 to 440 miles per night. Revenue per mile was $7.30 to $7.80. "I had no idea I was working that hard for those numbers," he says.

Frank pulled his zone data and found that 14 percent of his orders were coming from a cluster of apartments 5.5 to 6.5 miles away, a neighborhood his restaurant did not have any particular reason to serve over local competitors. Those outlier deliveries averaged 8.4 miles round trip per delivery and averaged order values of $31, producing revenue per mile of $3.69. "I was essentially delivering to that neighborhood at a loss," he says.

He trimmed his delivery zone to 4.5 miles and raised his minimum order to $22. He lost 11 orders per night, approximately 12 percent of volume. But total miles driven dropped from 430 to 308 per night. Revenue per mile improved from $7.55 to $10.12. Total miles-based costs fell by 28 percent. Net delivery margin improved by $340 per night despite $418 less in gross revenue. "I am making more money delivering less," Frank says. "That sentence still sounds wrong to me, but the numbers do not lie."

Tracking Revenue Per Mile: Making It Operational

Revenue per mile only generates value if you track it consistently and act on what it tells you. Here is a practical monitoring structure.

Daily Tracking

At the end of each service period, pull two numbers from your delivery management system: total delivery revenue and total miles driven. Calculate revenue per mile. Post it alongside your order count and average order value in your daily operations summary. Within two to three weeks of consistent tracking, you will have a meaningful baseline and will start seeing patterns that demand investigation.

Weekly Zone Analysis

Once per week, segment your revenue per mile by delivery zone band. Identify any bands where the metric falls below your target. Assess whether the underperformance is systemic, requiring a zone adjustment, or situational, attributable to an unusual week. Make zone decisions based on four-week trends, not single-week anomalies.

Driver-Level Revenue Per Mile

Individual driver revenue per mile reveals efficiency variations across your team that aggregate metrics mask. A driver consistently running below the team average revenue per mile is likely taking less efficient routes, declining batched orders, or working in a higher-mileage delivery pattern. GPS route history, combined with revenue per mile data, pinpoints the specific behavior driving the underperformance. This connects directly to your broader delivery metrics and KPI framework.

Revenue Per Mile as a Zone Pricing Tool

Some restaurants use revenue per mile analysis to implement distance-based delivery fee tiers rather than a flat delivery fee. The logic is straightforward: orders going 4 miles should pay a higher delivery fee than orders going 1 mile because they cost more to execute. A tiered fee structure keeps revenue per mile more consistent across zones while passing some of the cost variation to customers in the form of transparent, distance-proportional fees.

Customers generally accept distance-based delivery fees more readily than expected, particularly when they are implemented transparently with clear explanations at checkout. The alternative, subsidizing far-delivery customers through cross-subsidy from near-delivery customers, is less fair and harder to explain if customers ever ask why delivery costs the same for different distances.

Become a KwickOS Reseller

Help restaurants build delivery operations that are measurably profitable, not just busy. KwickOS resellers provide the analytics platform that turns delivery data into margin-improving decisions.

Learn About the Reseller Program

KwickOS Ecosystem

Kwick2Go KwickDesk KwickEPI KwickOS POS KwickPhoto KwickSpot KwickToGo KwickView RestaurantsPager RestaurantsPaging RestaurantsTables

© 2024-2026 KwickOS. All rights reserved.