Skip to main content
Nerve Centre KPIs · Audit Profile · Sentiment Settings Evri (rebranded from Hermes UK in 2022) is a UK B2C courier with a distinctive multi-attempt + ParcelShop drop-off model. CloudHub probe shows 2 active merchants on the legacy HermesAccount table (2021-11 refresh) plus 2 fresh ones on the new EvrisAccounts table (2026-03). Findings either lose a customer (failed ParcelShop drop-off, 3+ delivery attempts) or burn cash (lost-parcel claims - Evri historically higher loss rate than peers).

What this audit checks

Authentication & access

  • ClientID + ClientSecret still issue valid tokens (no 401)
  • Legacy username/password fallback still works for older integrations
  • Per-merchant base URL reachable
  • Hermes / Evri URL ID maps to a valid account

On-time delivery & courier-window promise

  • Carrier OTD < 95% rolling 30D
  • Courier-window adherence (estimated arrival window) < 90%
  • First-attempt delivery rate < 80% (Evri lower bar than peers due to multi-attempt model)
  • Median transit time > 4 days for non-Highlands UK postcodes

ParcelShop drop-off integrity (Evri-specific)

  • ParcelShop drop-off failure rate > 3% (courier never picks up)
  • Specific ParcelShops with failure rate > 10% (rogue-shop watchlist)
  • Drop-off-to-pickup lag > 24h (warehouse cutoff missed signal)

Multi-attempt delivery cap

  • Any tracking_number with attempt_number > 3 (return-to-sender risk)
  • Redelivery rate > 15% rolling 30D (address-quality / availability signal)
  • Returned-to-sender rate > 1.5% (Evri-specific - the multi-attempt + RTS path)

Exceptions, claims & lost-parcel rate

  • Exception rate > 3% rolling 30D
  • Open claims unresolved > 14 days
  • Lost-parcel claim rate > 1.5% rolling 90D (Evri historical baseline)
  • Damaged-parcel claim rate > 1%

Cross-channel: revenue at risk (the kill-shot area)

  • Cross-channel: late shipments joined to commerce_sibling orders -> revenue at risk per channel
  • Cross-channel: open claims with no Jira tracker_item -> CS coverage gap
  • Cross-channel: lost-parcel claims correlated with high-value orders -> finance focus
  • Cross-channel: 3+ attempt parcels heading to RTS -> proactive customer-service intervention candidates

Severity thresholds

SignalWarnCritical
on_time_delivery_rate9590
first_attempt_delivery8580
parcel_shop_failure_pct23
redelivery_rate_pct1215
attempt_count_max34
exception_rate23
open_claims_age_days714
lost_parcel_claim_pct11.5
damaged_parcel_claim_pct0.71
rts_rate_pct11.5
shipping_cost_per_order_change_pct510
claim_value_pct_of_revenue12
auth_token_failures_24h15

Data sources

  • GET TBD - pending CloudHub C# backend URL extraction - Auth probe + token issuance
  • GET TBD - pending CloudHub C# backend URL extraction - Shipment list + status
  • GET TBD - pending CloudHub C# backend URL extraction - Tracking events with attempt_number
  • GET TBD - pending CloudHub C# backend URL extraction - Claims