Skip to main content
Metrics type: Key Metrics • Category: Exceptions & Claims

​
At a glance

Share of Deutsche Post / DHL Paket consignments that threw at least one exception tracking event in the trailing 30 days, measured period over period. An exception is any scan that diverts a parcel from the normal collection to delivery flow: addressee not reached (Empfänger nicht angetroffen), address undeliverable (unzustellbar), held at the parcel centre, customs hold, damage, or loss. This is the leading indicator for the Deutsche Post connector: a rising exception rate today predicts late deliveries, failed deliveries, and claims over the next 24 to 72 hours.

​
Calculation

Calculated automatically from your Deutsche Post 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 German DTC supplements brand based in Köln, around 9,000 outbound parcels per week, almost all on DHL Paket domestic with a thin EU cross-border tail into Österreich and the Schweiz. Reading taken at 09:00 CET on 14 Apr 26 for the trailing 30 days (15 Mar 26 to 13 Apr 26). The card reads 2.4 percent on the gauge. The alert at >3% is not tripped on the blended book, but the picture is misleading. Five things to notice:
  1. The blended number hides the customs problem. Domestic DE at 1.8 percent is healthy and well within baseline. The DE to CH lane at 14.5 percent is the real story: the Schweiz is outside the EU customs union, so every parcel needs a CN23 declaration and clears Swiss customs, and a paperwork gap throws a Zoll hold exception. Pair this card with EU Cross-Border Customs Clearance Rate (<3d) to isolate the customs component before assuming the network is at fault.
  2. 2.4 percent of 37,320 is 881 parcels. Each one is a customer who will, on average, contact support within 48 hours. At an estimated 7 minutes per Wo-ist-meine-Bestellung (where is my order) ticket, that is roughly 100 staff-hours of work over the month created by carrier exceptions alone. The percentage looks calm; the workload is not.
  3. The exception rate leads the lagging cards. A spike here today shows up on Late Shipments in 24 to 48 hours and on Failed Deliveries shortly after. Treat this gauge as the early-warning radar, not the post-mortem.
  4. Empfänger nicht angetroffen is the largest domestic bucket. For German home delivery, recipient-not-home is the dominant exception, and it usually resolves into a successful Packstation or branch redirect rather than a true failure. Read alongside Packstation Delivery Rate: merchants who nudge customers towards Packstation at checkout see this bucket shrink because the locker is always there to receive the parcel.
  5. A rising exception rate with flat volume points upstream. If shipment volume is steady but exceptions climb, the cause is usually label-data quality (bad Hausnummer, missing Postleitzahl) rather than network capacity. Check Label Generation Success and the address-validation step before escalating to the DHL account team.

​
Sibling cards merchants should reference together

Exception rate is the leading indicator. Pair it with these to find cause and quantify downstream cost:

​
Reconciling against the source

Where to look in Deutsche Post / DHL’s own tooling: The merchant-facing record lives in the DHL Geschäftskundenportal (Business Customer Portal) under Sendungsübersicht → Status / Ereignisse, filtered to exception statuses. The public per-parcel scan history is the DHL Sendungsverfolgung keyed on the Sendungsnummer. Programmatically, the same events come from the DHL Parcel DE Tracking API (/track/shipments), and shipment counts from the DHL Paket Shipment API. The closest like-for-like view is all DHL Paket products, last 30 days, outbound only, status group: Ausnahme / Problem. Why our number may legitimately differ from DHL’s portal: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

My domestic rate is fine but the blended gauge is amber, what is going on? Almost always an EU cross-border lane, most often the Schweiz, dragging the blend up via customs (Zoll) holds. The Schweiz sits outside the EU customs union so every parcel needs a CN23 declaration. Split the gauge by lane and check EU Cross-Border Customs Clearance Rate (<3d). Fix the paperwork generation step and the blend falls back into baseline. Is “Empfänger nicht angetroffen” really an exception if the parcel still gets delivered the next day? Yes, but it is the benign kind. Recipient-not-home throws an exception scan, then usually resolves into a Packstation drop, a branch (Filiale) deposit, or a neighbour handover. It inflates this card without necessarily becoming a failure. That is why you must read it alongside Failed Deliveries: the gap between the two is your network’s self-recovery rate. Nudging customers towards Packstation at checkout shrinks this bucket. Why does the exception rate spike around public holidays? German Feiertage are regional. A Paketzentrum serving Bayern may pause on a holiday that Berlin works through, so parcels routed through that centre sit and throw held-at-centre exceptions. The spike is calendar-driven, not a network failure. Annotate known holiday weeks and avoid re-baselining thresholds permanently around them. The rate moved but volume did not, where do I look first? Upstream label data. A flat-volume, rising-exception pattern is the signature of address-quality problems: bad Hausnummer, missing or wrong Postleitzahl, truncated street names. Check Label Generation Success and your address-validation step before you escalate to DHL. The network rarely degrades silently with flat volume; bad labels do. Does this card include DHL Express? No. DHL Express is a separate product on a separate API with its own SLA and event taxonomy. This card is DHL Paket / Parcel only. If you ship both, watch the split on DHL Express vs DHL Parcel Volume Split and treat Express exceptions separately. How do I plan for Weihnachten peak? Expect the exception rate to rise 1 to 2 points from late November through to the second week of January as the network runs hot and recipient-not-home climbs with people travelling. Three actions: push Packstation hard at checkout for the peak window, tighten address validation so undeliverables do not leak into a stressed network, and re-baseline the alert threshold temporarily so the ops team is not paged on every reading. Reset when volume normalises. Why does Shopify show shipped but DHL tracking shows nothing yet? Two-stage handover. Shopify marks the order shipped when the label is generated; DHL’s first scan (Einlieferung) is at parcel-centre induction or branch drop-off, typically 2 to 24 hours later. A never-scanned parcel is not yet an exception here; it only becomes one once it enters the network and diverges. If 48 hours pass with no first scan, the parcel was probably never inducted, which is a warehouse issue, not a carrier exception.

​
Tracked live in Vortex IQ Nerve Centre

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