At a glance
Absolute count of Evri parcels that missed their service-aim delivery date in the rolling 7-day window. Evri sells day-aim services (Standard 3-5 day, Next Day, ParcelShop), so “late” is judged against the aim-by date for that service, not a time-of-day cutoff. Each parcel that overruns its aim scores 1.
Calculation
Calculated automatically from your Evri (formerly Hermes UK) 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 pet-supplies brand running Evri Standard for everyday parcels (food, toys, accessories), around 3,400 parcels per week. £30 average order value, 70 percent residential delivery. Reading taken at 09:00 BST on 12 Mar 26 for the trailing 7 days (06 Mar 26 to 12 Mar 26).
The card reads 225 as the headline; the alert at
>5% of total is tripped at 6.6 percent. Five things to notice:
- The 178 Standard late parcels are the bulk of the issue. At 6.3 percent late rate the merchant is feeling the trade-off cost. Compare to a 4 percent baseline in earlier months, the additional 60 to 70 late parcels per week is the action signal.
- Next Day at 9.3 percent is structural for Evri, not a one-off failure. Evri’s Next Day product over-promises on the same self-employed-courier network. If the brand’s customer promise on Next Day is firm, the right action is to switch Next Day volume to Royal Mail Tracked 24 (which delivers ~95 percent on next day at higher cost). Keep Evri Standard for everyday.
- The 225 late parcels translate to roughly 60 to 80 customer-service tickets in the next 3 to 5 days. WISMO conversion for Evri tends to be higher than for Royal Mail because customers’ baseline expectation is “Royal Mail-tier reliability”; when Evri misses, the complaint rate is disproportionate. Pair with the merchant’s CS ticket volume metric.
- Geographical concentration matters. Spot-check the 178 Standard late parcels by postcode: if 60 to 80 are concentrated in two postcodes, that is a courier event in a specific round. Pair with OTD by Route. If uniform across postcodes, the issue is network-wide (weather, depot capacity).
- Compare against the same week last year. A 6.6 percent late rate is bad if last year’s same week was 3.5 percent (real degradation), but normal if last year’s was 6 percent. Steady-state for Evri Standard is 4 to 7 percent; treat 6.6 percent as the higher end of normal, not an emergency.
Sibling cards merchants should reference together
Late count is a workload metric. Pair it with these:Reconciling against the vendor’s own dashboard
Where to look in Evri’s own portal: Evri Business Portal → Reports → Service Performance → Late Deliveries. Filter Date Range = Last 7 Days. The aggregate late-count at the top of the filtered view should reconcile with this card. Why our number may legitimately differ from Evri’s portal:
Internal identity (within Evri):
her_late_shipments_count = her_shipments_total - (her_shipments_total × her_otd_rate), ignoring rounding.
Cross-connector reconciliation:
Documentation cross-reference (UK carrier peers).