Delivery Routes Optimization Simulator

Optimize last-mile ops: cost per delivery, breakeven density, fleet utilization and routing scenarios. Daganzo model, AI, 3 scenarios. Free.

Advanced simulator

Which zone is losing money today, and what do I change first?

Spot which route or fleet costs more than it earns, and which density or vehicle change turns the operation profitable.

Fleet and drivers

Vehicles, shift hours and direct daily operating costs.

Zone and timing

Delivery-zone geography and operational timing.

Daganzo constant (k)

Geometric shape of the routing area. 0.55 clustered zones (LatAm urban neighborhoods), 0.70 random tour (Daganzo 1984), 0.85+ sparse rural. Scales the mean inter-stop distance linearly.

k = 0.62

Revenue and fuel

Revenue per delivery, fuel variable costs and operating month.

Saved configurations

Fill in your data to see the report

This simulator only generates a diagnosis, charts and recommendations when it has your real business values. Fill the editor above and the report will appear automatically.

  • Available vehicles
  • Vehicle cost per day
  • Driver cost per hour
  • Fuel price
  • Revenue per delivery
  • Deliveries per day

Load a realistic case to see how the report looks. You can edit any field afterwards.

Connect with other simulators

Methodology and assumptions

How results are calculated, what we assume when modeling, and where the method loses precision.

Formula

Total cost = Σ Distance × Cost/km + Time × Cost/h + SLA penalty · Cost per delivery = Total cost ÷ Deliveries

Assumptions

  • Average speed constant per zone (urban / suburban).
  • Per-stop service time (drop time) stable.
  • Per-vehicle capacity respected as a hard constraint.

Applicability limits

  • Heuristic optimization — does not guarantee the global optimum of the Vehicle Routing Problem.
  • Strict time windows and multi-depot are not modeled.
  • Traffic treated as a seasonal factor, not real-time.

Sources

  • Dantzig & Ramser (1959) — The Truck Dispatching Problem (Vehicle Routing).
  • Internal editorial estimate based on industry best practices.

How it works

1. Define your fleet

Vehicles, cost per day, driver cost, shift hours and physical capacity per vehicle.

2. Characterize the zone

Density (stops/km²), service time, effective speed, success rate. Realistic values per urban zone type.

3. Compare scenarios

Base, tough-zone expansion (lower density) and optimized routing. Identify breakeven and profitable quadrants.

Frequently asked questions

1How do you calculate average distance between stops?
Uses the Daganzo approximation for quasi-random routing zones: avg_distance ≈ 0.7/√density. Standard logistics heuristic to estimate tours without solving full VRP. For zones with peculiar topology (islands, rivers, limited roads), actual distance may differ.
2What is breakeven density?
It is the stops-per-km² density at which margin per delivery reaches zero. Below that number, operating is a net loss. Computed via binary search while keeping other parameters constant. Useful for deciding geographic expansion.
3Does it consider waiting times or delivery windows?
Not directly. The model assumes continuous flow during the shift. If your operation has strict windows (e.g., 8-10am for a client), real utilization will be lower. Use it as an upper bound on capacity.
4Does it work for courier, food delivery and e-commerce equally?
Principles are the same but tune: service time (food delivery 2-3 min, B2B courier 8-12 min), success rate (food delivery 98%+, residential courier 80-90%), revenue per drop (food delivery USD 4-8, B2B courier USD 6-15). The model is flexible to these ranges.

Complete guide

Route optimization: TSP, VRP and why spreadsheets don't solve real delivery

Delivery route optimization is one of the classic operations research problems and remains the single highest operating leverage for any carrier moving more than 30 stops per vehicle per day. The mathematical foundation is the Traveling Salesman Problem (TSP) — finding the shortest sequence that visits every stop and returns to origin — extended to the Vehicle Routing Problem (VRP) once you add multiple vehicles, varied capacities, customer time windows, and operational constraints. Pure TSP on 30 nodes has 2.65 × 10^32 possible routes; exhaustive enumeration is impossible even on a modern cluster. That's why the industry relies on heuristics (Clarke-Wright savings, 2-opt, Lin-Kernighan) and solvers like Google's OR-Tools, which resolve real 200-500 stop instances in seconds with a 2-5% gap to theoretical optimum.

Formulas and operating KPIs

Cost per stop = (Fuel + Driver wages + Vehicle depreciation + Maintenance) ÷ Stops delivered

Route density = Stops per route ÷ Kilometers driven. The higher the density, the lower the marginal cost per delivery. UPS ORION route optimization in Manhattan averages 6-8 stops/km; UPS suburban runs 2-3 stops/km. FedEx Ground and Amazon Logistics sit in the same corridor.

Stops per hour (SPH) = Stops delivered ÷ Route hours. UPS ORION benchmark: 18-22 SPH dense urban, 12-16 suburban. Amazon Logistics reports 15-20 SPH on its Delivery Service Partners.

Backhaul optimization — filling the empty return leg of the vehicle with pickups or return cargo. A truck that runs empty 30% of the time has cost efficiency 40-60% worse than one with scheduled backhaul.

Worked example: US mid-market last-mile carrier

A carrier with 20 vans delivers 1,400 daily parcels across a Phoenix metro zone. With manual dispatcher planning they average 70 stops/vehicle, 138 km per route, 10.8-hour shifts — SPH of 6.5 and route density 0.51 stops/km. Cost per stop: USD 3.85.

With OR-Tools calibrated for time windows (B2B 9-1pm, B2C 10-8pm), 450-lb capacity, and 9-hour shift cap:

  • Stops per vehicle: 70 → 78 (+11%)
  • Kilometers per route: 138 → 104 (−25%)
  • SPH: 6.5 → 8.6 (+32%)
  • Route density: 0.51 → 0.75 stops/km
  • Cost per stop: USD 3.85 → USD 2.72 (−29%)

Monthly savings on 31,000 stops: USD 35,000. Payback on OR-Tools integration (open-source + 2 weeks of an engineer): recovered in month one.

Time windows: the constraint that breaks pure TSP

The customer's time window is the variable that separates academic VRP from real delivery. A B2B account that only receives from 9:00-11:00 turns its stop into a hard constraint — if you miss the window, you have a failed delivery and a reattempt (1.5-3x the original shipment cost). The solver weighs penalty for window violation against marginal detour cost. US retail windows typically front-load the morning (7-11am store opening) and commercial deliveries concentrate 9-13h, creating peaks that force more vehicles for the same stop volume.

Backhaul, milk runs and dense zones

The LatAm and US carriers with best cost per stop — UPS, FedEx, Amazon Logistics, OSM, Rappi, 99minutos — run three plays: (1) milk runs: pre-programmed routes with B2B pickup after B2C delivery, using the vehicle already in-zone; (2) zone density: assigning routes by fixed polygon lets the driver learn the zone — Amazon Logistics documents 8-12% SPH improvement after 90 days in the same zone; (3) B2B-B2C backhaul: leaving DC with B2C morning cargo and returning with B2B or return pickups in the afternoon, cutting idle time below 10% of shift.

Electric vehicle constraints: range planning and charging stops

The EV transition is already reshaping route design. An ICE van on a 280-km route is range-unlimited within a working day. A 100 kWh LFP urban delivery van (BYD T3, Rivian EDV, Mercedes eSprinter) carries 200-280 km usable range at 30-50% urban payload. Routes must now account for: (1) range buffer — no dispatch below 15-20% reserve given temperature degradation in winter; (2) charging stops — DC fast chargers (150+ kW) recharge 20-80% in 30-40 minutes, imposing a driver-rest equivalence that can fit within regulatory breaks; (3) depot charging capacity — a 40-van EV fleet needs 40 × 11 kW overnight chargers plus 2-4 DC fast chargers for partial topping, representing a one-time CAPEX of USD 180K-400K that the routing economics must absorb. The VRP solver handles EVs as vehicles with dynamic range state, charging nodes, and forced recharge time windows. This is more complex than adding a constraint to the classic VRP — it requires a variant called EVRPTW (Electric VRP with Time Windows) that solvers like OR-Tools and OptimoRoute now support natively.

Pharma rep and field-service routing: the B2B variant

Not all routing is parcel delivery. Pharmaceutical sales reps visiting 10-15 clinics, hospitals, or pharmacies per day face a VRP variant with: soft time windows (preferred appointment times), visit frequency requirements (some accounts need weekly coverage, others monthly), and territory equity constraints (sales manager wants similar coverage across reps). OptimoRoute and Salesforce Maps (formerly MapAnything) are the dominant platforms here. The simulator models territory design and call-frequency scenarios to quantify the cost of each additional rep hire against the coverage gap it fills — a decision that typically involves USD 80-120K in fully-loaded rep cost.

Sector benchmarks: US vs LatAm

US leading last-mile operators — UPS ORION, FedEx Ground, Amazon Logistics DSPs — run in the 15-22 SPH corridor with route density 2-5 stops/km in dense urban. LatAm leaders like Rappi Turbo, 99minutos and OSM Colombia sit at 6-9 SPH with 3-5 stops/km. The gap isn't from solver quality (both use modern VRP) but from urban traffic (2-3x worse in CDMX, São Paulo, Bogotá vs Nashville or Dallas), informal addressing density (missing visible numbers forces a customer call), and in-building delivery time (doorman, elevator, signature). Understanding the benchmark appropriate to your geography is step one before rolling out optimization — importing UPS SPH targets to a Bogotá operation sets up failure.

Common mistakes in route optimization projects

  • Running the solver on stale address data. A 5% geocoding error rate means 5% of stops are placed at the wrong coordinate — the solver optimizes a fiction. Geocode validation is the highest-impact pre-processing step.
  • Optimizing for distance without cost-weighting. Minimizing kilometers is not the same as minimizing cost — toll roads, fuel surcharges, and time-of-day traffic can make the shortest route the most expensive.
  • Ignoring driver behavior after deployment. A perfectly optimized route degrades quickly when drivers deviate. Without GPS trace comparison against the planned route, you have no feedback loop.

Differentiation vs Excel and Google Maps

Excel doesn't solve TSP or VRP — the Solver add-in hits its variable ceiling around 15 stops. Google Maps optimizes waypoint sequence but ignores time windows, vehicle capacity and multi-vehicle routing. OR-Tools, Onfleet, Routific and Circuit for Teams close that gap; the web simulator is the bridge for carriers still planning manually and needing to quantify the value before investing in a TMS (Transportation Management System).

Conclusion

For carriers, e-commerce, FMCG distributors, and last-mile operators, route optimization is the number-one operating lever: 15-30% reduction in transport cost with marginal investment. The simulator lets you run TSP/VRP on your actual stops, compare scenarios with different fleet configurations, windows, and density, and quantify the savings before committing capital to software or additional fleet.

Illustrative case

Composite case for instructional purposes: combines sector dynamics with realistic figures. Names are fictional and do not represent a specific company.

Case study: Regional US last-mile carrier, Austin metro

Sunline Delivery Group operates out of Austin with 42 vans delivering 2,800 daily B2B2C parcels for e-commerce and pharma. In February 2025 the VP of operations flagged that cost per stop had jumped from USD 3.40 to USD 4.90 over 14 months — fuel and wages explained half, but analysis showed the third variable was route inefficiency: kilometers per route up 17% while stops per vehicle fell 5%.

The team loaded 30 days of history (GPS traces, actual times, customer windows) into OR-Tools and compared three configurations: (A) status quo with manual dispatcher planning; (B) VRP solver with windows and capacity; (C) VRP solver + fixed driver zones + B2B-B2C milk runs. Simulation over the 30-day window: scenario B cut kilometers 21% and raised SPH from 6.3 to 8.1; scenario C reached 8.9 SPH and recovered 14% of idle time via pickup milk runs.

Sunline rolled out scenario C in phases: month 1 pilot with 7 vans, month 2 expansion to 22, month 3 full fleet. Six-month results: cost per stop USD 4.90 → USD 3.35 (−32%), SPH 6.3 → 8.8, failed deliveries 4.5% → 1.9% (less rework), customer NPS +13 points from windows actually being honored. Annualized savings USD 420,000 against an investment of USD 32,000 (OR-Tools integration, TMS API, dispatcher training). ROI 13x in year one. The VP replicated the exercise for the San Antonio operation — still in pilot but tracking to similar outcome.

From theory to calculation

When you need more than a quick calculation, our advanced simulators model full scenarios with your data.

See advanced simulators

Sector reference ranges

Indicative ranges based on public sector literature and operational observation. Your business may differ — use the numbers as a starting point, not as a target.

MetricValueSource
Typical transport cost reduction with VRP solver10-20%ARC Advisory Group, TMS Market Analysis 2024
Stops per hour benchmark — dense urban (UPS ORION)18-22 stops/hUPS Annual Report 2023 / MHI Annual Industry Report
Route density target — LatAm urban last mile15-20 stops/hDHL Supply Chain Benchmarks 2024
SPH improvement after 90 days on same zone (Amazon Logistics)10-25%Bureau of Transportation Statistics / Amazon Logistics disclosures
Incremental cost of a failed delivery (retry)1.5-3× coste originalCSCMP State of Logistics Report 2024

Frequently asked questions

1What is VRP (Vehicle Routing Problem)?
VRP is the extension of the Traveling Salesman Problem (TSP) when there are multiple vehicles, different capacities, customer time windows, and constraints like maximum stops or route time. It's NP-hard, so it's not solved by enumeration but by heuristics (Clarke-Wright savings, 2-opt) or specialized solvers like Google OR-Tools, Routific or Optibus, which reach solutions within 2-5% of the theoretical optimum in seconds for real 200-500 stop instances.
2How much can I save by optimizing routes?
The ARC Advisory Group and DHL Supply Chain benchmark is 15-30% reduction in transport cost when migrating from manual planning to a VRP solver. Range depends on starting inefficiency: operations already using fixed zones and milk runs gain 10-15%; those running dispatcher-driven manual planning frequently recover 25-30%. Software ROI (OR-Tools open-source + integration) typically pays back in 1-3 months.
3What is route density and why does it matter?
Route density = stops per route divided by kilometers driven. It's the central metric for marginal delivery cost: higher density, lower cost per stop. US last-mile urban benchmarks are 2-5 stops/km; UPS in Manhattan and dense LatAm zones exceed 6 stops/km. Improving route density 20-30% typically reduces cost per stop 15-25%.
4How do I handle customer time windows?
Time windows are hard VRP constraints. A B2B customer receiving only 9-11am turns its stop into a constraint: if you miss, failed delivery (1.5-3x original cost). The solver weighs window violation penalty against marginal detour cost. Operating discipline: tight windows during morning rush (store openings) justify more vehicles; wide windows let you consolidate into fewer routes.
5What is backhaul optimization?
Backhaul means using the empty return leg for return cargo or pickups. A truck that runs empty 30% of the time has cost efficiency 40-60% worse. Tactics: milk runs with B2B pickup after B2C delivery, scheduled returns on the way back to DC, consolidation with another operator at cross-dock. Impact on cost per kilometer can be 20-35% improvement.
6Is OR-Tools free?
Yes, Google OR-Tools is open-source (Apache 2.0) and includes solvers for CP-SAT, linear programming, routing (VRP/TSP) and assignment. Real cost isn't license but integration: an engineer with optimization experience gets a first version running in 2-4 weeks. Commercial alternatives with built-in UI: Routific (~USD 49/vehicle/month), Circuit for Teams (~USD 20/driver/month), Onfleet (starting USD 500/month).
7Does Google Maps work for route optimization?
Partially. Google Maps Directions API optimizes waypoint sequence (TSP up to 25 stops) but doesn't solve VRP — it ignores multiple vehicles, capacities, time windows and shift constraints. For delivery with more than 15 stops per vehicle or multiple vehicles, you need a real VRP solver (OR-Tools, Routific, Optibus).

Tools from the same topical cluster. Use them together to close the loop on your analysis.

Last updated: April 30, 2026 · Reviewed by the Simúlalo editorial team. Figures and benchmarks are indicative; verify with your own data before deciding.

View methodology

How this simulator was reviewed

What you'll see, what it prevents, and where you shouldn't trust it

Every simulator on Simúlalo ships with the same editorial structure: two hypothetical worked examples with numbers, the errors it helps you avoid, the model's declared limitations, and a visible financial disclaimer. The review is signed and dated.

Hypothetical caseCase A

An operation that finds out its minimum profitable density is 9 deliveries/hour, not 6

A food delivery company had 4 motorcycles at 6 deliveries/hour with a target unit cost of $32 MXN/delivery. The simulator, with rider fixed cost ($14,000/mo), fuel, and depreciation, computes a minimum profitable density of 9.2 deliveries/hour — not 6. At 6 deliveries/hour, the real cost per delivery is $54.80. The decision: cut fleet from 4 to 3 motorcycles in off-peak hours (density rises), outsource peak hours (high density absorbed by in-house fleet), and monitor conversion for 30 days.

Illustrative figures. Does not represent a real company or an investment recommendation.

Hypothetical caseCase B

A retailer that outsources peripheral zones where in-house costs 38% more

A retailer delivers in CDMX with an in-house fleet. The simulator breaks down cost by zone: central $24/delivery (density 12), peripheral $74/delivery (density 3.2). The 3PL offer is $58/delivery with the same SLA. The gap: $16/delivery × 1,200 deliveries/mo in periphery = $19,200/mo in savings. The decision: outsource periphery, keep the in-house fleet in central zones where density sustains the cost. Reassign two underused central routes to same-day deliveries.

Illustrative figures. Does not represent a real company or an investment recommendation.

Common mistakes it helps you avoid

Things a team or decision-maker might assume that this simulator forces you to verify before committing.

  • Calculating cost per delivery using fuel only: you need to add rider, depreciation, maintenance, vehicle financing cost, and accident rate.
  • Comparing 3PL versus in-house without an equivalent SLA: if the 3PL has 2x delivery time, conversion drops and the savings evaporate.
  • Assuming uniform density: density varies by hour, day of week, and zone — the simulator forces you to declare it per segment for accurate cost.
  • Ignoring return cost: low FTR (first-time-right) drives re-delivery and doubles cost in problem zones.

Model limitations

What the simulator does not do, and where you need a professional or a specialized tool.

  • Does not optimize routing in real time (does not replace Google OR-tools, OptimoRoute, or similar). It models cost from declared densities.
  • Assumes a standard shift and regular operating regime. For peak seasons (Hot Sale, Black Friday) you need to model separately.
  • Does not include externalities: extreme traffic, mass events, natural disasters. When they happen, real cost spikes and assumptions lose validity.
  • Density break-even assumes you can adjust fleet. If headcount is locked by contract, cost per delivery changes.

When NOT to use this simulator

If your business is high-cadence B2C last mile with a rider incentive structure (gig model), unit cost depends heavily on tip mechanics, sub-contracting, and per-kilometer commission — variables a deterministic simulator does not capture cleanly. In that case, model the fixed component of your headcount first and treat the variable as pass-through to the service price.

Financial notice

Results are illustrative estimates and do not constitute financial, tax, accounting, or legal advice. Use the results as a reference point and validate important decisions with a certified professional.

Editorial review

Reviewed by the Simúlalo editorial team

This simulator was reviewed by the people listed below before being published. The review covers the declared formula, the model's assumptions, the explicit limitations, and the absence of unsupported financial claims.

They are part of the Simúlalo editorial team, focused on building financial tools that are clear, educational, and easy to interpret.

Last updated: We update this page when the methodology, sources used, or simulator structure change.

This tool uses standard financial formulas and user-supplied data. To explain concepts like rates, credit, risk, or cash flow we consult public and official sources (Banxico, SAT, CONDUSEF, CNBV, Banco de España, IFRS, BIS, among others). Simúlalo is not affiliated with, sponsored by, or endorsed by these institutions.