At a glance
Share of Net Dispatch-routed parcels that received a UK carrier exception scan in transit. Net Dispatch normalises Royal Mail, DPD, Evri, Yodel exception event codes into a unified taxonomy. Leading indicator for late deliveries.
Calculation
Calculated automatically from your NetDispatch data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A UK DTC fashion merchant via Net Dispatch. Reading taken at 09:00 GMT on 12 Mar 26 for the trailing 30 days vs the prior 30 days.
The card reads 5.8% with sentiment red (above warn=3); alert tripped. Five things to notice:
- Address-issue rate climbing 0.5 ppt is the headline. Investigation: the merchant launched a new mobile-checkout flow in late February that doesn’t validate UK postcodes against Royal Mail’s PAF (Postcode Address File). Fix: integrate Loqate or AddressFinder for UK address validation at checkout. Expected drop: 0.4 to 0.7 ppt within 2 weeks.
- Recipient-absent at 2.5% is normal for UK urban DTC. UK households (especially flats) are typically empty during business hours; “delivery attempted” is irreducible to ~2% for non-safe-place merchants. Mitigation: enable safe-place options at checkout (porch, neighbour, parcel locker) which Net Dispatch can pass through to most carriers.
- Held at depot at 1.0% is part of the UK pattern. “Held at depot for collection” is common when delivery attempt fails and recipient hasn’t arranged redelivery. The recipient must collect within 7-18 days (carrier-dependent) or the parcel returns to sender.
- Failed collection at 0.2% indicates merchant-side issue. 28 shipments where Evri/Yodel drivers failed to pick up from the merchant’s warehouse on schedule. Investigate with Net Dispatch CSM; usually traces to specific driver routes or unreliable pickup windows.
- The 952 exceptions in 30 days will produce roughly 480-670 late deliveries downstream. This card is the early-warning signal for the on-time number.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Net Dispatch’s own dashboard: Net Dispatch Dashboard → Tracking → Filter by status: Exception. Lists shipments with active or recent exception events, per type. The card aggregates; the dashboard supports row-level triage. Why our number may legitimately differ from Net Dispatch’s portal:
Cross-connector reconciliation: