Skip to main content
Metrics type: Key Metrics • Category: Shipping & Courier

​
At a glance

Share of PostNord shipments that threw a tracking exception (held at delivery office, address invalid, weather delay, customs clearance issue, attempted-no-answer, recipient refused, damage detected, etc) at any point during their transit. The leading indicator for Late Shipments and OTD Rate drops, exceptions today predict late deliveries 24 to 72 hours from now.

​
Calculation

Calculated automatically from your PostNord data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

The Stockholm outdoor-apparel brand. Reading taken at 09:00 CET on 14 Mar 26 for the trailing 30 days. What this tells the merchant:
  1. 2.76 percent exception rate, alert at >3% just clear. The card sits in WARN-near territory; weather-driven exceptions push the rate close to threshold during winter, which is normal seasonal variation.
  2. Weather is half the exceptions. 142 of 278 (51 percent) are WEATHER_DELAY. The card does not auto-exclude weather-affected days; the 2.76 percent rate is the actual experienced rate including weather. If you reset thresholds for winter (Dec to Feb) to 4 percent, the alert framing matches reality. Open Settings → Alerts → PostNord Exception Rate to apply seasonal thresholds.
  3. The address-invalid 10 percent share is the actionable trim. 28 exceptions caused by wrong addresses at checkout. Each costs roughly 2 days of redelivery cycle plus a customer-service ticket. The fix is upstream: enable PostNord’s address-verification widget at checkout (or use Klarna’s Nordic-aware address autocomplete). A typical implementation reduces address-invalid by 60 to 80 percent within 4 weeks.
  4. The recipient-not-home 23 percent share is partially preventable. Either ship more volume via MyPack Collect (pickup-point) where this exception cannot happen, or invest in a more aggressive delivery scheduling tool (e.g. PostNord’s “Choose your delivery time” feature when offered for the route). Recipient-not-home is structurally lower in dense urban areas and structurally higher in rural Sweden / Norway.
  5. The 18 customs-held cases are the cross-border specific issue. Norway (not in the EU customs union) requires a customs declaration on cross-border parcels; ensure your fulfilment integration is sending complete CN23 data. Missing or incomplete customs data is the primary cause of CUSTOMS_HELD, fixable upstream of PostNord.
  6. The leading-indicator behaviour. This brand’s reading 14 days ago was 1.92 percent. The rise to 2.76 percent over 14 days is the early-warning shape that predicted the late-shipments spike on 14 Feb (peer card showed 13.1 percent late on that week). Watch this card daily during winter; act on a 0.5pp daily rise before it cascades.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in PostNord’s own portal: PostNord Business Portal → Reports → Tracking Events, filter on event-type categories matching the exception taxonomy. PostNord doesn’t publish a single “exception rate” dial; the merchant must aggregate event-types per shipment manually. This card automates that aggregation. For service-status during weather events: postnord.se/driftinformation (Swedish), postnord.dk/driftinformation (Danish), and equivalents on .no and .fi. Why our number may legitimately differ from a manual aggregation: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

My exception rate just spiked from 1.5 percent to 4 percent overnight. What’s happening? Almost certainly weather (Nov to Mar window) or industrial action. Check postnord.se/driftinformation for service alerts; if a major snowstorm or strike is announced, the spike is climate / labour driven and recovers as conditions normalise. Outside winter, sudden 2pp+ spikes usually trace to: (1) sortation incident at a major hub (Hallsberg in Sweden, Brøndby in Denmark) creating MISSORT spikes; (2) a fulfilment-side address-data issue (e.g. Shopify webhook failure caused a batch of orders to ship with corrupt addresses); or (3) a customs-rule change (Norway VAT changes have caused CUSTOMS_HELD spikes historically). Why is exception rate the leading indicator and OTD the lagging? An exception event is a signal during transit (parcel held, redelivery scheduled, customs queued); the late-vs-on-time judgment can only be made when delivery completes. Exceptions happen Day 2-3, late status determines Day 3-5. Acting on the leading signal is cheaper than acting on the lagging one, you can reroute or pre-emptively message customers based on exception status before the parcel is officially late. How should I tune the threshold for Nordic winter? Default 3 percent is calibrated for year-round average. For Dec to Feb consider raising to 4 percent (still alerts on operational issues but suppresses weather-driven false positives). Tune in Settings → Alerts → PostNord Exception Rate → Seasonal Override. Reset to 3 percent in March. A “weather delay” exception persisted for 4 days. Did the parcel get lost? Probably not, but it’s worth investigating. Most weather delays clear within 48 to 72 hours of the storm passing. If the exception persists past 4 days post-storm, the parcel may be: (1) still queued at a regional hub waiting for the recovery backlog to drain (typical for Norrland after major snowstorms); (2) genuinely misplaced during chaotic sortation; (3) blocked at a customs checkpoint awaiting documentation. Contact PostNord business support with the consignment ID; persistent post-event exceptions usually resolve via human escalation. The address-invalid share is growing. What’s the fix? Upstream of PostNord. Three options: (1) Address verification widget at checkout (PostNord publishes one for Sweden / Denmark; Klarna’s Nordic-aware checkout includes it). (2) Per-country address validation in your checkout JS (Norway and Finland have different postal-code formats; some merchants accept any string and PostNord’s intake fails). (3) Manual address-correction workflow for the address-invalid bucket; CS team reaches out to customers within 24 hours to confirm correct address before parcel is returned. How does cross-border CUSTOMS_HELD work? Norway and Iceland are not in the EU customs union; cross-border consignments require a CN23 customs declaration. PostNord’s intake validates basic fields; if the declaration is incomplete (missing HS code, missing recipient ID, value mismatch), the parcel is held at the destination’s customs checkpoint until the merchant or recipient provides the missing data. Most merchants automate CN23 generation via their fulfilment integration; gaps in the integration produce customs-held spikes. RECIPIENT_NOT_HOME on MyPack Home is part of the model. Why does it count as exception? Because it triggers redelivery, customer communication, and potential re-routing to a pickup point. From a merchant-impact perspective it’s an exception, even if PostNord’s contractual SLA tolerates a single retry. If your checkout copy promises home delivery on Day X and the customer experiences a Day X+2 redelivery, the perception is “late” even if the contract says “on-time after retry”. Pair with First-Attempt Delivery Rate to size this specifically. Multi-account aggregation (separate marketer accounts per Nordic country), how does this card aggregate? The card sums exceptions across all configured PostNord accounts, displayed as a single rate against total shipments. Per-account breakdown via the dashboard’s drill-down. Different country-accounts often have different exception shapes, Norway’s CUSTOMS_HELD share is structurally higher than Denmark’s, since DK is in the EU customs union. Is there a per-exception-type alert? Not from this card directly; the card is the aggregate. Per-type alerts (e.g. “alert when WEATHER_DELAY share exceeds 60 percent”) are configurable in Settings → Alerts → PostNord Exception Type Breakdown, and they fire on the Exception Rate by Type detail card (when present in the merchant’s dashboard). Does an exception that resolves before delivery still count? Yes. The card measures whether an exception occurred, not its outcome. A parcel that was held at a delivery office for an extra day but still arrived on the aim date still throws an exception event; the card counts it. This is correct behaviour: exceptions are signals about transit health regardless of final outcome. My exception rate is 0.8 percent year-round. Is that suspiciously low? Possibly. Either you’re operating in a structurally low-exception lane (urban Stockholm-only, all MyPack Collect, no cross-border) or PostNord’s exception-event ingestion is incomplete for your account (some legacy contracts have reduced event detail). Verify by spot-checking 10 random recent shipments against PostNord’s portal event-stream; if events match, the rate is genuinely low and the operation is well-tuned.

​
Tracked live in Vortex IQ Nerve Centre

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