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.
| What it counts | COUNT(parcels WHERE actual_delivery_date > aim_delivery_date AND status = 'DELIVERED') over the rolling 7-day window. In-transit parcels are not counted yet; they flip into the count once a delivery scan lands. |
| API endpoint | Evri’s tracking API surface; reads tracking_number, service_code, aim_delivery_date, actual_delivery_date, latest_event_status. |
| Service level scope | All Evri outbound services pooled (Standard, Next Day, ParcelShop, Light & Large). International Tracked is excluded (different aim definition). |
| Returns / RTO | Outbound only. Failed-and-redelivered parcels score against the first successful delivery date, so a re-attempted parcel delivered late still counts late. |
| Self-employed-courier failure attribution | Evri’s couriers are paid per parcel and rotate through rounds; courier-induced lateness (sick day, no-show, holiday) and weather / network events all sit in the same count. The card does not split cause-attribution. |
| Time zone | UK local. |
| Time window | 7D (rolling 7 days, period-over-period). Tighter than the 30D OTD card on purpose, late spikes need to surface before they bleed into refunds and WISMO ticket volume. |
| Alert trigger | >5% of total. The 7-day late count tripping above 5 percent of total 7-day volume flips amber. For Evri, with structurally lower OTD than Royal Mail, a 5 percent late rate is the threshold of “trade-off no longer worth it”; below 5 percent the cost saving offsets the reliability gap. |
| Currency | n/a directly. |
| Roles | owner, operations |
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).| Service | Parcels (7D) | Late (missed aim) | Late % | Notes |
|---|---|---|---|---|
| Evri Standard (3-5 day) | 2,820 | 178 | 6.3% | Above alert |
| Evri Next Day | 410 | 38 | 9.3% | Above alert (typical for Next Day) |
| Evri ParcelShop drop-off | 170 | 9 | 5.3% | Just above alert |
| Total (this card) | 3,400 | 225 | 6.6% | Alert tripped |
>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:| Card | Why pair it | What the combination tells you |
|---|---|---|
| On-Time Delivery Rate | The percent companion. | Late count rising while OTD% holds means volume rose. Both moving means real degradation. |
| ParcelShop Drop-off Failure Rate | Specific Evri failure mode. | If late count is rising and ParcelShop failure rate is climbing, the route into the network is the cause. |
| Redelivery Attempts > 3 | Late parcels often cycle into multi-attempt scenarios. | Each row past 3 attempts is on its way to RTS or loss. |
| Lost-Parcel Rate | Some late parcels never arrive at all. | A persistent rise in both is the trigger to switch carrier. |
| OTD by Route | Postcode-level breakdown. | Identifies courier-event concentrations. |
| Failed Deliveries | Sister metric. | Late minus failed roughly equals “would-be-on-time-with-faster-redelivery” parcels. |
Cross-connector: royal_mail.roy_late_shipments_count | Carrier peer comparison. | Same merchant, same week, two different carriers. |
| Cross-connector: customer-service ticket volume (Zendesk, Gorgias) | Downstream effect. | Late count predicts WISMO spike at 24-72 hours lag, with Evri converting at higher rates than other carriers. |
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:| Reason | Direction | Why |
|---|---|---|
| Aim-date strictness | Ours stricter | Evri’s portal may treat day-after-aim as “marginal”; this card scores it late. |
| Failure-cause exclusions | Evri lower | Evri’s portal sometimes excludes “customer fault” failures (recipient absent, refused) from headline late count for performance-review purposes; this card pools all overruns. |
| Scan timing in low-signal areas | Ours stale | Evri couriers scan via mobile app; in poor signal areas the scan can lag 30 to 90 minutes. |
| In-transit treatment | Ours lower for “today” | Vortex IQ excludes still-in-transit parcels; Evri’s portal sometimes pre-categorises late-ETA parcels. |
| Time zone | Boundary days off | UK local on both. |
her_late_shipments_count = her_shipments_total - (her_shipments_total × her_otd_rate), ignoring rounding.
Cross-connector reconciliation:
| Card | Expected relationship | Causes of legitimate divergence |
|---|---|---|
royal_mail.roy_late_shipments_count | Carrier peer for the same merchant. | Different parcel populations and service-level mixes. |
| Customer-service ticket volume | Strong lagged correlation, ~24 to 72 hours. | Other ticket drivers (product issues, payment failures). |
Documentation cross-reference (UK carrier peers).