If you have sat through three vendor demos and come away with three different definitions of "route management software", you are not being slow. The category genuinely has no agreed boundary. One vendor means a map with pins on it. Another means a full distribution back office with invoicing and van inventory. A third means a driver app bolted onto a tracking device.
This article draws the map. It is written for someone who has to buy, not someone writing a market report.
The one-sentence definition
Route management software plans who visits which customers, in what order, on which vehicle, at what time — then tracks whether that plan survived contact with the day, and records what happened at each stop.
Everything else vendors sell around that is an extension. Useful extensions, often necessary ones, but extensions.
If your day is defined by what is delivered, look at route management. If it is defined by what is fixed, look at field service.
The six modules you will actually be choosing between
Almost every product in this space is assembled from the same six building blocks. Vendors differ in which ones they built well, which they bought, and which they are still pretending to have.
| Module | What it does | Who cares most |
|---|---|---|
| Planning and optimisation | Turns a list of stops and constraints into vehicle routes | Planners, transport managers |
| Dispatch and execution | Publishes routes, handles the day's changes, monitors progress | Dispatchers, supervisors |
| Driver mobile app | Manifest, navigation, proof of delivery, exceptions | Drivers, customer service |
| Customer communication | ETAs, tracking links, delivery notifications | Customer service, sales |
| Reporting and analytics | Plan versus actual, cost per stop, service performance | Operations, finance |
| Integrations | Order source, ERP, telematics, finance | IT, everyone downstream |
A product that is genuinely strong in all six is rare and expensive. Most buyers are better served by being honest about which two matter most in their operation and treating the rest as "must be adequate".
Where the category stops
Three neighbouring categories overlap enough to cause confusion in procurement.
Fleet management software is about the vehicles and drivers as assets: maintenance schedules, fuel, compliance documents, cost per mile, driver behaviour. It answers "is this van roadworthy, legal and economic?" not "where should it go today?". Many suites sell both, but the modules are usually distinct products under one login. Our complete guide to fleet management software covers that side.
Transport management systems (TMS) manage freight movement between locations: loads, carriers, rates, tendering, freight settlement. A TMS thinks in shipments and lanes. Route management thinks in stops and days. If you tender loads to third-party carriers, you want a TMS. If you own the vans and the drivers wear your logo, you want route management.
Field service management covers the same shape of problem — technicians visiting sites — but adds skills matching, parts on the van, job estimates, warranties and follow-up visits. If a stop lasts 90 minutes and the outcome is a repair rather than a drop, you are in field service, not delivery routing.
What "optimisation" means in practice
The optimisation engine is the part buyers over-weight in evaluation and under-test in the demo.
A real engine takes a set of stops with locations, demands and time windows, plus vehicles with capacities, shift rules, start and end depots, and cost characteristics, then searches for the assignment and sequence that minimises a cost function you define. That cost function is where the disagreements live: minimising distance, time, overtime, vehicle count or "cost" produces four different plans from identical inputs.
What separates serious products from map-drawing tools:
- Constraint depth. Can it handle a customer who accepts deliveries only Tuesday and Thursday, 07:00–11:00, requires a tail-lift vehicle, and must be visited before their neighbour on the same street?
- Service time modelling. Does it use a real per-customer service time, or a single global average? See service time estimation for why this matters more than the routing maths.
- Realistic travel times. Historical, time-of-day-dependent road speeds beat straight-line distance by a wide margin, and beat a single average speed by more than most buyers expect.
- Explainability. When the plan does something odd, can it tell you which constraint forced it? Without this, planners quietly stop trusting the system and go back to their spreadsheet.
The daily rhythm the software has to support
Products that demo well often fail here, because the demo shows planning and skips the twelve hours after it.
- Order intake — orders arrive from an ERP, e-commerce, EDI or phone, with varying quality.
- Cut-off and planning — planner runs the optimisation, reviews exceptions, adjusts manually, commits.
- Load sequencing — the warehouse loads in reverse stop order; a plan that ignores loading reality creates chaos at the dock.
- Dispatch — routes reach driver devices, ideally before the shift, with a downloadable offline copy.
- Execution — drivers complete stops, capture proof, report exceptions; dispatch handles failures and add-ons.
- Customer communication — ETAs go out and update as reality changes.
- Debrief and reconciliation — actuals return to the office: times, mileage, failed deliveries, returns.
- Reporting — the loop closes with plan-versus-actual analysis that feeds tomorrow's assumptions.
When you evaluate, walk a vendor through your version of these eight steps. It is a far more revealing exercise than any feature list. Our demo script for fleet vendors formalises the approach.
Who benefits most
Route management software pays back fastest where three conditions coincide: many stops per vehicle per day, variable demand, and manual planning today. A courier with 90 drops a day per van and a planner working in a spreadsheet is the archetype.
The payback is weakest where routes are genuinely fixed, dense and long-established — some municipal collection rounds, some fixed vending circuits — because a good manual route built over twenty years is often within a few percent of optimal. In those operations the value comes from execution, evidence and customer communication, not from the optimiser. That is a perfectly good reason to buy, but it changes which product wins.
What it costs, roughly
Pricing usually lands in one of six models, covered in detail in our pricing models guide. For orientation: per-vehicle-per-month subscriptions for delivery routing commonly sit in the $30–$120 range in the small and mid-market, with optimisation-heavy or route-accounting products running considerably higher, and implementation charged separately at anything from a few thousand dollars to six figures for a complex ERP-integrated rollout.
Frequently asked questions
Is route management software worth it for a fleet of five vehicles?
Often yes, but not for the optimisation. At five vehicles the savings from better sequencing are small in absolute terms; the value is in proof of delivery, customer ETAs, removing the planner's evening spreadsheet session and having evidence when a customer disputes a drop. Judge it on those benefits, not on a percentage-of-mileage claim.
How much distance does route optimisation really save?
On genuinely unstructured manual planning, 5–15% of distance is a realistic first-year range, occasionally more where territories have never been redesigned. Where planning is already disciplined and routes are dense, expect low single digits — and look for the payback in service consistency and planner hours instead.
Can I just use a consumer navigation app with multiple stops?
For up to roughly a dozen stops a day, per driver, with no capacity or time-window constraints, yes. What you lose is multi-vehicle assignment, proof of delivery, exception handling, integration with your order source and any record of what happened. Most operations outgrow the workaround at somewhere between 15 and 25 stops.
Does it work without reliable mobile coverage?
Only if the driver app is genuinely offline-first — full manifest cached, proof of delivery stored locally, automatic sync when signal returns. Ask vendors to demonstrate this in aeroplane mode rather than describing it. Rural delivery operations should treat it as a hard requirement.
What is the difference between route management and route accounting software?
Route accounting adds the commercial layer: mobile invoicing, pricing and promotions, van inventory, cash collection and driver settlement. Distribution businesses that sell from the truck need it; a parcel operation delivering pre-paid orders usually does not. See our route accounting guide.
