At a glance
Share of Shippo-printed shipments that hit a carrier exception event during transit (weather hold, address correction, customs hold, damage, refused, recipient-not-home retry, missort). The leading-indicator companion to Failed Deliveries and Late Shipments: exceptions logged today drive late and failed deliveries two to five days from now.
Calculation
Calculated automatically from your Shippo 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 US DTC supplements brand on Shopify, around 12,000 shipments per month via Shippo, split USPS Priority and UPS Ground with a thin DHL Express international tail. Reading taken at 09:00 ET on 12 Mar 26 for the trailing 30 days (10 Feb 26 to 11 Mar 26).
The card reads 3.7 percent on the dial with the alert at
>3% tripped at warn. Five things to notice:
- Address correction is 49 percent of exceptions and the most fixable bucket. Add address validation at checkout (Shopify Shop Pay native, or an app such as Address Validator) and you can halve this bucket within four weeks. Each prevented correction saves $16+ in carrier fees before CS time. Shippo also exposes
POST /addresses/validatefor pre-label verification. - Recipient-not-home is 21 percent and only partly fixable. Signature-required forces a scheduled redelivery on high-value parcels, and pickup-point delivery options remove the “nobody home” failure mode entirely where carriers support them.
- Weather is unavoidable but predictable. When a major weather event hits a hub region, expect a one to three day exception spike, then a late-delivery wave three to five days later. This card is your early warning for Late Shipments.
- The 3.7 percent rate implies roughly 13k of monthly recoverable cost. A focused four-week address-validation project could halve the largest bucket and pay for itself inside one month.
- The same brand read 6.4 percent in Dec 25. Q4 doubled the rate. The 30-day window in early March is the correct baseline; comparing March against December would double-count seasonality. Use the
vsPperiod-over-period view, not a year-on-year jump across peak.
Sibling cards merchants should reference together
Exception rate is a leading indicator. Pair it with these to act ahead of the wave:Reconciling against the source
Where to look in Shippo’s own dashboard: Shippo App → Tracking → Filter by status: Exception, or Shipments → Filter “Exception”. The closest like-for-like view is All Carriers, Last 30 Days, Status: Exception. Each tracking event is listed per shipment, so you can drill from the rate down to the individual scan codes. Because Shippo is a multi-carrier aggregator, the authoritative scan still lives in each underlying carrier’s portal (USPS Informed Visibility, UPS Quantum View, FedEx tracking, DHL); Shippo’s view is the normalised pool on top of those scans. Why our number may legitimately differ from Shippo’s report:
Cross-connector reconciliation:
Known limitations / merchant FAQs
My exception rate is at 4 percent but my OTD is fine. What is happening? Exceptions can recover. A “weather delay” scan today may resolve into an on-time delivery 24 hours later if the carrier catches up. This card surfaces upstream risk, not confirmed damage. Watch the next five days: if the late count climbs, the exception wave is converting to OTD damage; if late count stays flat, the carrier absorbed it. Address correction is half my exceptions. What is the cheapest fix? Three actions, in order of cost. (1) Free: tighten Shopify checkout copy (“verify your apartment or suite number before placing your order”), which cuts 10 to 20 percent of correction events. (2) Low cost: install a checkout address-validation app (80 per month), which cuts 30 to 50 percent. (3) Higher cost: pre-shipment verification via Shippo’sPOST /addresses/validate endpoint, which catches the edge cases the consumer-facing app misses for a fraction of a cent per call. The carrier correction fee (11 on USPS) usually pays for the app inside the first month at any reasonable volume.
International parcels generate customs-hold exceptions. Should I exclude those?
No. They are real exceptions and cost real money: transit delay, the customer chasing the parcel, and occasionally a loss. Use Shipments by Destination to view your international rate separately. A reasonable benchmark is 3 to 8 percent international, 1 to 3 percent domestic.
Recipient-not-home retries are not really my fault. Can I exclude them?
You can mentally set them aside, but the card includes them deliberately. Your customer’s experience is “the parcel did not arrive on the day promised”, and they will contact your CS team regardless of fault. Track preventable recipient-not-home separately (signature-required parcels, weekend deliveries) by service.
The good threshold of 1 percent feels aggressive. Is it realistic?
For domestic-only USPS Priority and UPS Ground, 1 to 1.5 percent is achievable with address validation in place. For international-heavy or USPS Ground Advantage shops, 2 to 3 percent is typical. Adjust the workspace threshold in the Alert Rules tab to match your service mix rather than relying on the generic default.
Q4 / BFCM doubled the rate. Should I disable the alert?
No, raise the threshold for the season instead. A reasonable seasonal setting is >5% warn and >8% critical for 25 Nov 25 to 5 Jan 26. Disabling the alert silences the signal of a genuine peak-on-peak event.
Damage exceptions, what do I do with them?
Two actions. (1) Check whether they cluster around a SKU (a packaging problem) or a carrier hub (a handling problem); High-Cost Shipment Outliers sometimes reveals re-ship cost spikes that line up with a damage cluster. (2) File a Shippo Insurance claim within 30 days of the ship date for any insured parcel. Shippo Insurance runs roughly 1.5 to 3 percent of declared value and covers damage, loss and theft.
My exception rate dropped to 0.5 percent suddenly. Is the data missing?
Possibly. Two checks. (1) Confirm Shippo tracking is still receiving carrier scans by looking at the last tracking_history event timestamp on a sample of recent shipments. (2) Confirm the Shippo API token has not expired, via Days to Token Expiry and API Error Rate. A near-zero rate is more often a feed problem than a real operational improvement.