Software for Logistics and Delivery
Last updated:
The 5% that costs the money
Deliveries that go to plan cost what they were priced at. The money leaks on the exceptions: nobody home, access blocked, wrong address, refused, damaged, redelivery.
Off-the-shelf systems handle the happy path well and exceptions generically. That is where a custom layer earns its cost, because your exception rules are specific to your customers and your promises.
Buy the routing
Vehicle routing is a genuinely hard optimisation problem with mature commercial solutions. Building your own is a research project with an uncertain outcome.
Buy it, and spend the budget on feeding it properly — accurate service times, real vehicle constraints, driver skills, time windows. Routing quality is dominated by input quality, not by the algorithm.
Build the exception layer
- A defined outcome for every failure type, agreed in advance
- Driver capture of the reason with a photograph, on the device
- Automatic customer communication with a rebooking option
- A cost attributed to each exception, so the pattern is visible
- Weekly reporting by cause, which is what actually reduces them
Every logistics client we have worked with was surprised by the exception report. Not the total — the distribution. One cause is usually a third of the cost and nobody had counted.
Proof of delivery that holds up
- Photograph, timestamp and GPS position, captured together
- Signature where it is genuinely required, not by default
- Recipient name recorded
- Available to the customer within minutes
- Stored long enough to answer a dispute months later
Tracking that reduces phone calls
“Where is my delivery?” is the highest-volume support contact in the sector, and it is almost entirely preventable with proactive updates.
- Confirmation with a window when the route is planned
- A narrowing window as the day progresses
- A notification when the vehicle is a defined number of stops away
- Immediate confirmation on completion, with the photograph
- Proactive notification of a failure, before the customer notices
That last one matters most. A customer told about a problem is annoyed; a customer who discovers it is angry and calls.
What it costs
| Component | Cost | Duration |
|---|---|---|
| Driver app with offline POD | £25k–£60k | 12–20 weeks |
| Exception workflow | £12k–£30k | 6–12 weeks |
| Customer tracking and notifications | £10k–£25k | 6–10 weeks |
| Routing integration | £8k–£20k | 4–8 weeks |
Frequently asked questions
Do we need our own driver app?
Can you integrate with courier networks?
How accurate can delivery windows be?
What about electric vehicle range?
Want software that fits how your sector actually works?
Tell us about your operation. We will tell you what to buy, what to build and what to leave exactly as it is.
Related services
What we build for problems like this one