Delivery scheduling and route planning for distribution businesses
Delivery scheduling is rarely a mapping problem. It is a constraint problem: vehicle capacity that changes through the day, customer opening hours, service intervals, driver hours and a road network that does not behave the way last week's plan assumed. This guide covers how those constraints interact, using the model behind ProWat.
Plan around constraints, not distance
The shortest route is often not the deliverable one. A realistic plan accounts for vehicle dimensions and access restrictions, load weight that falls as the round progresses, delivery and collection on the same visit, customer time windows, and the service or sanitisation work due at each stop.
Treating service visits and deliveries as separate rounds is one of the most common sources of wasted mileage. When both are scheduled against the same asset and the same customer, one visit frequently covers both.
Recurring orders and demand patterns
Most distribution demand is predictable. Customers on recurring patterns generate forecastable volume, which lets you plan rounds ahead, buy stock against real demand and spot accounts whose consumption has drifted away from their agreed schedule.
Exceptions matter more than averages: a stop that is consistently short-delivered or repeatedly rescheduled is usually a pricing or service problem showing up in the logistics data.
Re-optimise more often than you think
A plan built on Friday is stale by Monday. Cancellations, urgent additions, vehicle availability and road conditions all change the optimal sequence. Operations that re-optimise daily — and allow controlled in-day changes pushed to the driver's device — consistently run fewer miles per drop than those working from a fixed weekly round.
Close the loop in the field
The plan is only worth as much as the data coming back from it. An offline-capable driver app that captures proof of delivery, signatures, photographs, quantities delivered and collected, failed-delivery reasons and asset movements turns the round into an auditable record — and feeds invoicing without re-keying.
- Proof of delivery with signature and photo capture
- Asset installs, exchanges and collections recorded against the customer
- Failed-delivery reasons that drive the next scheduling decision
- Offline operation with sync on reconnection
Frequently asked questions
- How is this different from a satnav or mapping tool?
- Mapping tools sequence stops. Scheduling systems decide which stops exist in the first place, based on recurring orders, service intervals, asset requirements, capacity and time windows — then sequence them.
- Does route optimisation account for load weight?
- It should. Weight changes through the round and affects both vehicle legality and access, so a plan built only on distance can produce rounds that cannot legally be run.
- Can drivers work without a signal?
- The ProWat driver app is built for offline use, holding the day's work locally and synchronising proof of delivery and asset changes when connectivity returns.
Want to take this further?
Explore ProWatRelated guides
What is the Clarion programming language?
A practical introduction to Clarion: what it is, what it is used for, why business applications built with it are still running after 30 years, and where it fits today.
Clarion ABC vs Legacy: which template chain should you use?
The difference between the ABC and Legacy (Clarion) template chains, what each means for maintenance and third-party add-ons, and how to decide when converting is worth it.
Upgrading Clarion: moving an application from Clarion 6 to Clarion 12
A staged approach to upgrading older Clarion applications — what actually breaks, how to sequence the work, and how to keep shipping while you do it.