Skip to main content
Metrics type: Cross-Platform MetricsCategory: Shipping & Courier
Evri-specific failure mode - the courier never picks up from the ParcelShop, leaving the parcel in limbo. Below 97% means specific shops need flagging.

At a glance

Share of Evri ParcelShop drop-off parcels where the Evri pickup courier did not collect from the ParcelShop on the daily collection sweep, leaving the parcel sitting at the convenience store waiting for the next day’s collection or longer. This is an Evri-specific failure mode unique to the ParcelShop drop-off model: parcels enter the network via merchant deposit at one of Evri’s 6,500+ ParcelShop partners (mostly small convenience stores), and the Evri courier collects from each ParcelShop typically once daily. When a courier no-shows or skips a ParcelShop, parcels there are stranded.

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 craft-supplies brand with an out-of-hours dispatch routine, around 950 ParcelShop drop-off parcels per month. Brand uses ParcelShop because the warehouse manager finishes packing at 18:30 (after Evri’s last courier collection) and drops parcels at the local Co-op (an Evri ParcelShop) on his way home. Reading taken at 09:00 BST on 12 Mar 26 for the trailing 30 days (10 Feb 26 to 11 Mar 26). The card fires alerts on the Spar at Ealing Common (8.2%). Five things to notice:
  1. One specific ParcelShop is driving most of the failure count. 18 of 29 failures are at the Spar at Ealing Common. The aggregate looks bad (3.1 percent above alert) but the actionable signal is “switch this ParcelShop”. Move the merchant’s drop-off routine to the nearby Co-op or Premier; both run below 3 percent.
  2. Why does one shop fail at 8 percent? Three usual reasons. (a) The shop staff don’t always have parcels ready when the courier arrives, parcels sit in the back and the courier can’t wait. (b) The Evri courier on this round skips the shop occasionally, particularly if it adds a detour to their route. (c) The shop staff are not properly scanning parcels into Evri’s system, the parcel “exists” in the dispatch system but Evri’s network has no record of it being deposited.
  3. The 8.2 percent shop is near the merchant’s warehouse, which is why it gets used most. Convenience drives habit; staff drop at the closest shop. The fix requires explicit instruction to use a different shop, ideally with the same out-of-hours availability.
  4. Each pickup-no-show is a 24-to-48-hour delay on the parcel. The customer experience is worse than Standard service: the dispatch system shows “shipped” but there is no Evri tracking event for 24+ hours, generating premature WISMO tickets. Pair with the merchant’s CS ticket-volume metric.
  5. Compare against driver-collection failure rate, typically ~1 to 2 percent on the Exception Rate NOT_LOADED code. ParcelShop adds an extra hop in the chain of custody, which is why it runs slightly higher than driver-collection. If the gap is more than 2 to 3 points, the ParcelShop choice is the culprit.

Sibling cards merchants should reference together

ParcelShop failure rate is a process-attribution view. Pair with these:

Reconciling against the vendor’s own dashboard

Where to look in Evri’s own portal: Evri’s portal does not surface this metric directly. The closest equivalent is the Reports → ParcelShop Performance view, which shows per-shop deposit count and pickup count but does not aggregate into a failure-rate per shop. For account-managed customers, the Evri account team can pull a custom report breaking down ParcelShop performance by ID; ask the account manager. Why our number may legitimately differ from any Evri-side report: Internal identity (within Evri): hermes_parcel_shop_failure_rate ≤ her_exception_rate filtered to PARCELSHOP_NOT_PICKED_UP. The two should track each other; large divergence indicates a classification gap. Cross-connector reconciliation:
Documentation cross-reference (Evri-specific). This card is unique to Evri because the ParcelShop drop-off model is unique to Evri among major UK couriers; only Royal Mail’s Post Office handover model is comparable structurally.

Known limitations / merchant FAQs

My ParcelShop failure rate is 8 percent at one specific shop, what should I do? Stop using that shop. Spot-check the failures: if 80+ percent are at one ID, route the merchant’s drop-off routine to a different ParcelShop. Evri has 6,500+ ParcelShops and most have alternatives within walking distance. Why does the same Evri courier sometimes skip a ParcelShop? Self-employed courier model. Each courier optimises their own route to maximise per-parcel earnings; a ParcelShop with low deposit volume can be skipped if it adds material detour time. Evri’s network is supposed to enforce daily collection, but enforcement is uneven. Should I switch from ParcelShop drop-off to driver-collection? For high-volume merchants, yes. Driver-collection has lower failure rate (~1-2 percent on Evri) than ParcelShop (~3-5 percent). Cost is similar. The ParcelShop model is best suited to low-volume merchants without the daily volume to justify a scheduled courier collection. Why is the alert per-shop in addition to overall? Because a single bad shop drives most of the failures. The overall rate at 3.1 percent looks marginal, but the per-shop view at 8.2 percent is actionable. Always look at both. Can I see real-time which ParcelShops are reliable in my area? Evri publishes ParcelShop performance ratings via their merchant portal (5-star scale per shop). The card’s per-shop failure rate is more granular and current; use both. My ParcelShop failure rate spiked from 2 percent to 6 percent overnight, what happened? Almost certainly a courier event. Either (a) the regular Evri courier on this round quit / went on holiday and the backup is skipping shops, (b) the route was reallocated to a less-experienced courier, or (c) the depot consolidation altered the route schedule. Wait 1 to 2 weeks for stabilisation; if the rate stays elevated, escalate. Does the card cover both outbound and customer returns drops? This card is outbound only (merchant deposits parcels for delivery). Customer returns deposited at ParcelShops use a separate flow and are not in scope. The card classifies a parcel as failed at 24 hours, but Evri picked it up at 28 hours, was it really a failure? By the card’s threshold, yes. The customer experience is “the parcel disappeared for 24 hours after I dropped it off”. Even if Evri eventually collects, the 24-hour gap drove WISMO ticket volume and customer anxiety. The 24-hour threshold is calibrated to the customer-visible signal, not Evri’s contractual SLA. My biggest ParcelShop is a Co-op that has been reliable for years, why is it suddenly at 5 percent failure? Probably the local Evri courier round changed. Check whether the parcel deposit-to-pickup gap has shifted from typical 4-6 hours to 12+ hours in the last 2 weeks. Also check whether the Co-op staff have changed (new staff sometimes skip the daily Evri scan-in routine).

Tracked live in Vortex IQ Nerve Centre

ParcelShop Drop-off Failure Rate is one of hundreds of KPI pulses Vortex IQ tracks across Evri (formerly Hermes UK) and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.