Skip to main content
Card class: Hero • Category: Shipping & Courier

​
At a glance

Share of USPS shipments that received an exception scan in transit. Exception scans are non-routine events such as “delivery attempted, addressee not in”, “delivery exception, address unknown”, “delivery exception, no access to delivery point”, “carrier unable to deliver”, “weather embargo”. The exception-rate is the leading-indicator card for late deliveries: an exception scan precedes a late-or-failed delivery by 12 to 48 hours, sometimes longer for rural routes.
What it countsCOUNT(shipments WHERE tracking events INCLUDE any exception code) / COUNT(shipments) over the trailing 30 days. Exception codes are USPS Tracking event codes outside the routine acceptance/processing/in-transit/delivered set.
Exception event types(1) Delivery attempted (recipient absent, no safe drop-off location). (2) Delivery exception (insufficient address, addressee unknown, refused). (3) Forwarded (recipient moved, USPS forwarding service active). (4) Held at facility (recipient pickup required, hold mail in effect). (5) Weather embargo (route suspended for storm or natural disaster). (6) Damaged (parcel torn, contents leaking, requires repackaging).
Lead-indicator semanticsEach exception is a yellow flag, not a confirmed late. Many resolve on next-day-attempt and deliver on time; others escalate to delays of 1 to 7 days. The card is most useful as a 24 to 48 hour early warning for the on-time number.
Service level scopeAll USPS services pooled. Priority Mail, Priority Mail Express, First-Class Package, Ground Advantage, Parcel Select, Media Mail. Exception rates are similar across services since they reflect address quality and customer behaviour rather than service speed.
Returns / RTOExcluded. RTS shipments have their own Returned to Sender tracker.
Holiday/election surgeException rates spike during November-December and around US elections. Drivers: address-quality pressures from hand-written gift labels, recipient-not-home from holiday travel, weather embargoes from Q4 storms, suspended routes during named-storm events. Expect 1.5x to 2.5x normal exception rate in November-December.
Address-quality signalA persistently high exception rate often points to upstream address-validation problems. If the merchant’s checkout doesn’t validate ZIP+4 or apartment numbers, exception rates run 2 to 3x higher than for merchants with USPS-API-validated addresses at checkout.
Time window30D vsP (rolling 30 days, period-over-period comparison)
Alert trigger>3% (warn). Steady-state DTC merchants run 1 to 2.5%; above 3% signals systemic address-quality, route-coverage, or weather-surge issues.
Sentiment keygauge with thresholds good=1, warn=3 (lower is better)
Rolesowner, operations

​
Calculation

Calculated automatically from your USPS 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 apparel merchant shipping out of Seattle, primarily USPS Ground Advantage and Priority Mail. Reading taken at 09:00 PT on 12 Mar 26 for the trailing 30 days vs the prior 30 days.
Exception typeShipments affected% of totalVs prior 30D
Delivery attempted (recipient not in)2851.8%+0.3 ppt
Delivery exception (address)1681.1%+0.6 ppt
Forwarded620.4%flat
Held at facility410.3%flat
Weather embargo380.2%-0.1 ppt
Damaged120.1%flat
All exceptions (this card)6063.9%+0.8 ppt vs 3.1%
The card reads 3.9% with sentiment red (above warn=3); the alert at >3% has tripped. Five things to notice:
  1. The +0.6 ppt rise in “Delivery exception (address)” is the headline. Investigation: the merchant added a new product page in late February that auto-fills shipping address from a third-party widget. The widget is dropping apartment numbers on roughly 8% of orders. Fix: switch to a USPS-API-validating address widget, or add a post-checkout validation step. Expected drop: 0.4 to 0.6 ppt within 2 weeks.
  2. “Delivery attempted” at 1.8% is normal but climbing. Recipient-not-home is irreducible to about 1.5%; the +0.3 ppt suggests holiday-season vacationers (typical for Spring Break). Will normalise within 2 weeks.
  3. Each exception is a 1-to-3-day on-time risk. The 606 exceptions in the period generated roughly 280 to 380 late deliveries downstream. The exception rate today is the on-time rate slip in 24 to 72 hours.
  4. Weather embargo at 0.2% is low for the season. Pacific Northwest had a mild February. Compare against December readings (typically 0.8 to 1.5%) for context.
  5. Damaged at 0.1% is operational. 12 damaged parcels per 30 days is normal at this volume; if it climbs above 0.3%, investigate packing process or carrier handling. The damaged-parcel rate also feeds Open Claims for parcels declaring contents over $50.
Note: the most actionable subset of exceptions is “Delivery exception (address)”. Address-quality improvements at checkout typically cut this exception type by 50 to 70% within a billing period, with cascading benefit to on-time and refund-rate cards.

​
Sibling cards merchants should reference together

CardWhy pair it with Exception RateWhat the combination tells you
On-Time Delivery RateLagging confirmation.Exception rate climbing 24 to 72 hours before on-time-rate drops is the early-warning signal. Act on the exception, not the on-time number.
Late ShipmentsLagging count.Roughly 50 to 65% of exceptions become late deliveries; the rest resolve on next attempt.
Returned to SenderWorst-case outcome.Address exceptions that fail correction roll forward into RTS within 5 to 15 days.
Failed Delivery CountSevere-end of the exception spectrum.Failed delivery is a confirmed-cannot-deliver disposition; exception is the upstream signal.
Cross-connector: shopify.refund_rateCustomer-impact lag.Address-exception rate predicts a refund-rate climb at 10 to 20 day lag (the exception, then the failed delivery, then the customer dispute).
Cross-connector: address-validation tool data (USPS Web Tools, Google Address Validation)Upstream root cause.High address-exception rate often indicates checkout-side address validation isn’t firing.

​
Reconciling against the vendor’s own dashboard

Where to look in USPS’s own dashboard: USPS does not surface an aggregate exception-rate report in PostalOne! by default. Per-shipment exception scans are visible at USPS Tracking for each tracking number; aggregate views require either PostalOne! reports filtered to non-routine event codes, or third-party tracking aggregators (AfterShip, ShipBob, EasyPost). The card is the primary aggregate view for most shippers. Why our number may legitimately differ from the vendor’s:
ReasonDirectionWhy
Event-code scopeEitherThe card includes any non-routine scan (delivery attempted, exception, forwarded, held, weather, damaged). USPS’s portal sometimes excludes “delivery attempted” from exception reports because it is so common.
Tracking-data qualityCard may show lowerUSPS sometimes posts partial scans that don’t reach the Tracking API. Rural routes have the worst scan-event coverage.
Time zone<1 day offUTC vs local-time boundary.
Cross-connector reconciliation:
CardExpected relationshipWhat causes legitimate divergence
fedex.fed_exception_ratePeer carrier.Different parcel-weight distribution and customer-mix; FedEx tends to run lower exception rates because of better address-validation at booking.
easypost.eas_exception_rateAggregator view.EasyPost includes USPS exceptions plus all other carriers; filter to USPS for like-for-like.

​
Known limitations / merchant FAQs

My exception rate jumped from 2% to 4% overnight. What happened? Three diagnostic steps. (1) Check whether one ZIP or region is responsible (a winter storm, a USPS facility outage). (2) Check whether one address-source is responsible (a recent checkout-flow change, a third-party widget update, a customer-import event). (3) Check whether the merchant’s sales-channel mix shifted (marketplace customers tend to have lower-quality address data than DTC). Most overnight shifts trace to one of these three. How do I cut “Delivery exception (address)” specifically? Implement USPS Web Tools address validation at checkout. The API standardises addresses to USPS-canonical form, fills in ZIP+4, and rejects undeliverable addresses before order placement. Roughly 30 to 60% of address-exception rate is preventable this way. Most ecommerce platforms (Shopify, BigCommerce, Adobe) have plugins for this; budget 4 to 8 hours of development for installation and testing. Why is “Delivery attempted” so high in March and December? Spring break and holiday travel. Recipients are away from home; carriers attempt and notice. The pattern repeats annually; not actionable on the merchant side. Just adjust the customer-service playbook to handle the inquiry volume. A parcel showed “delivery exception” but ultimately delivered on time. Why? Many exceptions resolve on the next-day attempt. “Delivery attempted, recipient not in” → carrier leaves notice → recipient arranges hold-for-pickup → parcel delivers within 1 to 3 days, often within service-standard window. The card counts the exception event regardless of subsequent delivery outcome; the on-time card scores delivery only. Should I worry about “Forwarded” exceptions? “Forwarded” means the recipient has a USPS Change of Address active. The parcel is being routed to the new address, typically adding 2 to 5 days. The card counts it as an exception. Long-term, encourage customers to update their account shipping address to avoid USPS-managed forwarding (which will lapse after 6 months and expose the original address). What’s a “Held at facility” exception? USPS holding the parcel at the destination Post Office for recipient pickup. Reasons: recipient on hold-mail status (vacation hold), parcel-too-large for delivery vehicle, attempted-delivery-failed-twice. The recipient must collect; if they don’t within the holding window (typically 15 days), the parcel returns to sender. Pair with Returned to Sender to track follow-on outcomes. The card says my exception rate is fine but my customers complain a lot. Why? Two possibilities. (1) Customer complaints are about damage or lost-in-transit, which are exception types but rare; the rate looks fine because most customers complain even on routine slow deliveries. (2) Customer expectations are tighter than USPS service standards; even on-time delivery (per service standard) feels late if they expected next-day. Review checkout copy and reset expectations. During Q4, what exception types climb the most? “Delivery attempted” climbs because of holiday travel. “Weather embargo” climbs in the Mountain West and Northeast. “Held at facility” climbs as cluster-box fill-rates exceed capacity. “Damaged” climbs slightly from increased volume strain. All exception types are higher; prepare for 1.5x to 2.5x the normal rate. Can I reduce exception rate by switching from USPS to FedEx? Slightly. FedEx’s address-validation at booking catches some bad addresses USPS would flag at delivery. Expected drop: 0.5 to 1.5 ppt. The cost increase typically outweighs the benefit unless the merchant’s exception rate is consistently above 5% (where the operational cost is significant).

​
Tracked live in Vortex IQ Nerve Centre

Exception Rate is one of hundreds of KPI pulses Vortex IQ tracks across USPS 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.