Operations guide

How to reduce failed deliveries in multi-drop European operations

A failed delivery is not one cost, it is five: the wasted drop, the return leg, the re-plan, the customer contact and the delayed invoice. This is the operational playbook we see work across European multi-drop fleets.

All guides

8 min read · Last reviewed 20 August 2026

Key takeaways

  • Most failures are information failures, not driving failures.
  • ETA accuracy matters more than ETA speed — a reliable two-hour window beats an optimistic thirty-minute one.
  • Access notes belong on the stop record, not in a dispatcher's memory.
  • Every failed stop needs a structured reason code, or you cannot fix the cause.
  • Measure first-time delivery rate per customer and per lane, not as a single fleet average.

Where failures actually come from

CauseTypical shareFix
Recipient absentHighPre-arrival notification with a realistic window
Wrong or incomplete addressMediumValidate and geocode at intake, not at the kerb
No access: gate code, dock slot, lift, permitMediumPersistent access notes on the stop record
Vehicle arrives outside the site's receiving hoursMediumTime windows enforced in the planner
Goods refused or damagedLowPhoto condition check at load, not at delivery

Note what is missing from this list: driver performance. Fleets that respond to failed deliveries with driver pressure tend to see the number stay flat and turnover rise. The leverage is upstream, in the data attached to the stop.

Make the ETA something the customer can trust

An ETA is a promise. It becomes reliable when the planning engine models service time per stop type, mandatory breaks, and traffic patterns for the actual time of day — and when it is recalculated as the route runs, not fixed at 06:00.

  • Use measured service times per stop type instead of one flat average.
  • Push a narrowing window: a morning window at plan time, a tighter window once the previous stop is completed.
  • Send the notification in the recipient's language, with a link that shows live progress.
  • Let the recipient reply — a two-tap 'not home, deliver to neighbour' saves an entire return leg.

Handle exceptions as a workflow, not a phone call

When something goes wrong, the driver's options should be visible in the app: report a delay, report a failed attempt with a reason code and photo, or request a re-plan. Each action should reach the dispatcher as a structured item in an exception inbox with an SLA clock, not as a message in a group chat.

The four numbers to track weekly

  • First-time delivery rate, broken down per customer, per lane and per stop type.
  • ETA accuracy: the share of stops served inside the promised window.
  • Exception resolution time, from the driver's report to a dispatcher decision.
  • Proof-of-delivery completeness: the share of stops with photo, signature and timestamp captured.

Track these for four weeks before changing anything. Most operations discover the problem is concentrated in a handful of customers and one part of the day, which makes the fix far cheaper than a fleet-wide programme.

Fix the causes, not the symptoms

Depot2Door combines constraint-aware planning, stop-level access data, structured exception handling and photo proof of delivery in one system your drivers actually use.

Explore the TMS

Frequently asked questions

What is a good first-time delivery rate for multi-drop B2B work?

It depends heavily on stop type. Scheduled B2B dock deliveries should be well above 95%, while unattended residential deliveries of bulky goods run considerably lower. Compare yourself against your own trend per stop type rather than an industry headline number.

Does route optimisation on its own reduce failed deliveries?

Only partly. Optimisation reduces distance and improves punctuality, but it does not know that the gate code changed. Failure rates drop when planning, stop-level data and driver feedback share one record.

How much does a failed delivery cost?

Add the vehicle and driver time for the wasted drop, the re-delivery, the administrative handling and the delayed invoice. Most European operators who measure it land on a figure well above the profit margin of the original delivery, which is why prevention pays quickly.

Should drivers be allowed to leave goods with a neighbour?

Only against an explicit, recorded instruction from the recipient, captured in the app with proof of delivery. Verbal permission without a record shifts liability onto the carrier.