The Week a Delivery Management System Stops Being Optional
Drafted with AI assistance, edited and fact-checked by Sean Flannery. See our editorial policy.
A delivery management system is software that runs deliveries end to end: importing orders, optimising routes, dispatching jobs to a driver app, tracking vehicles live, sending customers ETA updates, and capturing electronic proof of delivery. It replaces spreadsheets, phone dispatch and paper run sheets.
That definition is easy. Knowing when you actually need one is harder.
Most operators do not sit down and decide to buy logistics software. They hit a morning where the old routine stops holding, and the decision makes itself.
Three phone calls in one morning: how operators know the spreadsheet has failed
Picture a twelve vehicle operation on a normal Tuesday.
The first call comes at 11:20. A customer was promised a 9am to 11am window and nobody has arrived. The dispatcher does not know why, because the run sheet was printed at 6am and reality moved on around 7:30.
The second call is internal. Sales wants to know where a driver is so they can tell an account manager something useful. The only way to find out is to ring the driver, who is mid-drop and does not answer.
The third is a dispute. A customer says a pallet never turned up. The driver says it did. The evidence is a photo sitting in a phone camera roll, unsorted, no timestamp anyone trusts, and no way to attach it to the order.
None of those three problems is a people problem. They are all the same information problem wearing different clothes.
In my experience working with dispatch teams, this is the pattern that triggers the software conversation, not fleet size on its own. Two vans doing 60 booked time windows a day will hit it before eight vans doing loose all-day drops.
The question is never really "are we big enough". It is "can we still answer where, when and did it happen, without picking up the phone".
What is a delivery management system?
A delivery management system is the software layer that plans, executes and proves your own-fleet deliveries. It sits between your order source and your drivers.
It covers five stages: order intake (manual, CSV, e-commerce or API), route optimisation with time windows and vehicle constraints, dispatch to a driver mobile app, live vehicle tracking with customer ETA notifications, and electronic proof of delivery.
It is not a transport management system, which is built around procuring freight and rating third-party carriers. It is not a standalone route planner, which produces a stop sequence and stops there.
The distinguishing test is evidence. If the software cannot tell you who delivered what, where, at what time, and produce a photo or signature to back it up, it is not a delivery management system.
A delivery day, end to end: order intake to proof of delivery
Here is the same Tuesday, run on software instead.
Orders land overnight. Some come from a Shopify or WooCommerce store, some by API from an ERP, some as a CSV a customer emails at 4pm. They arrive with an address, a time window and a service duration.
At 5:30am the plan is built. The route optimisation engine sequences the stops against vehicle capacity, driver shift length, booked windows and traffic patterns, then splits the work across the vehicles that are actually available today.
Dispatch is one click. Each driver opens the driver app and sees their run in order, with navigation, customer notes and the goods on board.
At 7am the customer gets an SMS with a live tracking link and a narrowing ETA. That link is what stops the 11:20 phone call from ever being made.
Geofencing marks arrival and departure automatically, so service time is measured rather than guessed.
Then something goes wrong, because something always does. A site is locked, a customer is out, a pallet is refused.
The driver logs an exception with a reason code and a photo. Dispatch sees it in real time and either reattempts later in the run or rolls it into tomorrow's plan without anyone rekeying an address.
Every completed stop closes with electronic proof of delivery: timestamp, GPS coordinates, signature or photo, and a barcode scan where the goods are serialised.
By 4pm you have plan versus actual data. Which stops ran long. Which windows slipped. Which customer keeps adding 20 minutes to a route without paying for it.
Core features, and what each one actually replaces
Feature lists on vendor sites are useless because they never say what the feature displaces. This table does.
| Capability | What it replaces in a manual operation | Who feels it first |
|---|---|---|
| Order intake and integration | Rekeying orders from email, store admin and phone messages into a spreadsheet | Office admin |
| Route optimisation with time windows | The most experienced dispatcher's memory of the round, and the map on the wall | Dispatcher |
| Dispatch to driver app | Printed run sheets, WhatsApp groups, morning briefings in the yard | Driver |
| Live vehicle tracking | Ringing the driver to ask where they are | Dispatcher |
| Customer ETA notifications and tracking link | Inbound "where is my delivery" calls landing on whoever answers | Customer |
| Geofencing and service time capture | Guessing how long each site really takes when quoting the next job | Owner or ops lead |
| Exceptions and failed-delivery reattempts | A sticky note that says "redeliver Thursday" and sometimes gets actioned | Dispatcher and customer |
| Electronic proof of delivery | Photos in a camera roll, signed dockets in a glovebox, credit notes issued to end an argument | Finance and the customer |
Read the middle column again. Every row is a task somebody in your business is doing right now, by hand, at a cost you have never itemised.
Delivery management by business type
The category label matters less than the constraint you are actually solving for. Five common shapes, drawn from segments Locate2u works in:
Cold chain and temperature-sensitive food
The constraint is time, not distance. Product quality degrades on the road, so sequencing and service-time accuracy matter more than raw kilometres saved.
Premium seafood delivery is a good example of this shape of problem, and Madam Seafood's case study covers how that segment operates.
Subscription and direct-to-consumer
Volume is predictable, addresses are residential, and the customer expects retail-grade communication.
Meal kit and recurring box operations live or die on ETA notifications and first-attempt success. My Foodie Box sits in this segment.
B2B wholesale and retail replenishment
Fewer stops, bigger drops, receiving hours that are non-negotiable. Miss the dock window and the whole stop is wasted.
Early-morning bakery wholesale runs are the sharpest version of this, which is what makes Husk Bakery and distribution operations like GT Product Sales useful reference points.
Scheduled collections and pickups
Reverse logistics has the same machinery pointed the other way: recurring schedules, container or asset tracking, and proof that a collection happened.
Containers for Change operates in this collection-routing space.
Heavy goods to site
Construction and materials delivery adds access constraints, crane or forklift availability, and a site contact who may not be there.
Proof of delivery carries real commercial weight here, because a disputed drop on a build site becomes an invoice argument. Franz Building Supplies is in this segment, as is multi-drop refrigerated courier work of the kind Perth Couriers handles.
Eight things to check before you commit to a platform
Demos all look the same. These eight questions separate the platforms fast.
- Integrations. Does it connect natively to your order source? Locate2u covers Shopify, WooCommerce, ShipStation, Xero, ServiceM8 and Zapier natively, plus a public API for ERP and WMS work, which matters more than it sounds when your orders live in three places.
- Driver app usability on cheap hardware. Your drivers will not carry flagship phones. Test the app on the oldest Android handset in the business, in a low-signal area, wearing gloves.
- Proof of delivery depth. Signature, photo, barcode scan, notes, GPS and timestamp. Ask whether the record is exportable and attachable to an invoice, not just viewable in a dashboard.
- Exception and reattempt handling. What happens on a failed delivery? If the answer is "the driver rings dispatch", the platform has not solved the problem.
- Customer notification quality. Branded messages, narrowing ETAs, a tracking page that works on mobile. This is the part your customer judges you on.
- Onboarding and support. Who cleans your address data, who trains the drivers, and what time zone is support in when a route breaks at 5am.
- Scale without re-platforming. Locate2u runs micro-fleets of three drivers and enterprise operations planning for 1000-plus drivers on the same product, so growth does not force a migration.
- Pricing model. Per driver, per vehicle, per stop or tiered. Model it at double your current volume before you sign.
One more thing worth checking that rarely makes buyer checklists: whether the platform handles both parcel-style multi-drop work and heavier scheduled freight. Plenty of tools pick one. If your business mixes both, picking a specialist means running two systems.
What a delivery management system costs, and what moves the price
Pricing in this category is almost always subscription based, charged per driver, per vehicle or per stop.
Locate2u publishes its tiers openly, starting from US$25 per user per month, and the current pricing tiers are listed here. Quote-only pricing is common among enterprise-focused vendors, which makes budgeting harder for smaller operators.
Five things move the number.
Active driver or vehicle count is the base. Stop volume matters where pricing is consumption based.
Customer SMS and email notifications are sometimes metered separately, so check whether messaging is bundled.
Integration work is the variable most people underestimate. A Shopify connection is minutes; a custom ERP integration is a project.
Onboarding and support depth is the fifth. Self-serve setup costs nothing extra and takes longer; guided onboarding costs more and gets you live sooner.
The comparison that actually matters is not software cost against zero. It is software cost against the admin hours, failed deliveries and credit notes you are already absorbing. According to McKinsey's analysis of parcel economics, the last mile carries the largest single share of total delivery cost, which is why routing and dispatch decisions dominate delivery margin.
Delivery management system vs TMS vs standalone route planner
These three get used interchangeably in sales conversations. They are not the same tool.
| Dimension | Delivery management system | Transport management system (TMS) | Standalone route planner |
|---|---|---|---|
| Built around | Executing the final leg with your own fleet | Freight procurement, carrier rating, multi-leg planning | Producing a stop sequence |
| Primary user | Dispatcher, ops lead, drivers | Logistics or procurement team | Whoever plans the round |
| Customer communication | Built in: tracking links, ETA notifications | Usually carrier-dependent | Rarely included |
| Proof of delivery | First-class: photo, signature, GPS, scan | Depends on carrier feeds | Not covered |
| Good fit when | You control the vehicles and the promise | You buy freight across multiple carriers and modes | Planning is the only broken part |
Gartner treats last-mile delivery execution, driver enablement and customer communication as capability sets distinct from transportation management, and that split is reflected in its supply chain technology research. Larger operations often run both layers. Most fleets that control their own vehicles start with the delivery layer, because that is where the customer-facing failures happen.
Worth noting how the two dimensions a delivery management system directly improves show up at national level too: the World Bank's Logistics Performance Index scores countries on six dimensions, two of which are timeliness and tracking and tracing.
Implementation: what the first 30 days look like
A small fleet does not need a six-month rollout. It needs a sequence.
Two failure modes are worth naming.
The first is skipping address cleanup. Bad geocoding produces bad routes, drivers lose trust in the sequence, and the whole rollout stalls in week two.
The second is running the spreadsheet in parallel indefinitely. If dispatch keeps a shadow copy, nobody commits, and the data you need for the week four review never accumulates.
Frequently asked questions
What is the difference between a delivery management system and a TMS?
A TMS focuses on freight procurement, carrier selection, rating and multi-leg planning, usually across third-party carriers. A delivery management system focuses on executing the final leg with your own drivers: routing, dispatch, driver app, live tracking, notifications and proof of delivery.
Is a delivery management system the same as route optimisation software?
No, route optimisation is one component of it. A route planner produces the stop sequence, while a delivery management system also handles order intake, dispatch, live tracking, customer ETA links, exception handling and electronic proof of delivery.
How many vehicles do you need before it is worth it?
There is no universal threshold, and fleet size is a weaker signal than operating pattern. The usual triggers are booked time windows you keep missing, daily "where is my driver" calls, and delivery disputes you cannot settle from your own records.
What drives the cost of a delivery management system?
Pricing is normally charged per driver, per vehicle or per stop, with tiers by feature depth. The main cost drivers are active driver count, stop volume, whether customer SMS and email notifications are bundled, integration complexity, and the level of onboarding you need.
What features should a small fleet insist on?
Route optimisation with time windows, a driver app that runs well on low-cost Android handsets, electronic proof of delivery with photo and signature, live tracking links, automated ETA notifications, and exception handling for failed deliveries. An integration path to your order source is the seventh non-negotiable.
How long does implementation take?
A small fleet can typically be running live routes within the first week, with full rollout across drivers, notifications and integrations inside a month. Complex ERP integrations extend that timeline, so scope them separately from the core rollout.
Where to start
If you recognised the three phone calls, the decision has already been made for you. The only question left is which platform, and that comes down to the eight checks above rather than the demo you enjoy most.
Test the driver app on your worst phone. Ask what happens on a failed delivery. Model the pricing at double your current volume.
When you are ready to see how the pieces fit together, look at how Locate2u runs delivery operations end to end, from order intake through to signed and photographed proof of delivery.