> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Exception Rate, Deutsche Post > Exception Rate for Deutsche Post stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Exceptions & Claims](/nerve-centre/connectors#connectors-by-type) ## 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. | | | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `COUNT(shipments WITH >=1 exception scan) / COUNT(shipments WITH >=1 tracking event)` over the rolling 30-day window. Each consignment is counted once even if it threw several exception scans, so the denominator is shipments seen by the network, not raw scan events. | | **Data source** | DHL Paket / Parcel DE Sendungsverfolgung (tracking) feed. Vortex IQ ingests events through the DHL Parcel DE Tracking API (`/track/shipments`) keyed on the Sendungsnummer, and maps each event's `statusCode` / `standardEventCode` to one of the exception buckets. Shipment counts come from the DHL Paket Shipment API (`/parcel/de/shipping/v2/orders`). | | **What counts as an exception** | Empfänger nicht angetroffen (recipient not home), unzustellbar / Adresse fehlerhaft (undeliverable, address fault), Zoll / customs hold on EU and Welt lanes, Sendung beschädigt (damaged), Verlust (loss), Rücklauf an Absender initiated (return to sender), held at Paketzentrum past its normal dwell. A successful Packstation or branch redirect is **not** an exception; it is a normal alternative-delivery path. | | **Service scope** | DHL Paket (domestic DE), DHL Parcel EU (Inland to EU lanes), and DHL Warenpost where tracked. DHL Express is a separate product on a separate API and is excluded; see [DHL Express vs DHL Parcel Volume Split](/nerve-centre/kpi-cards/deutsche-post/dhl-express-vs-dhl-parcel-volume-split). | | **Return-leg inclusion** | **Outbound only.** Retouren-Etikett (prepaid return label) consignments carry the inbound flag and are excluded; their exceptions sit on [Returned to Sender](/nerve-centre/kpi-cards/deutsche-post/returned-to-sender). | | **Time window** | `30D vsP` (rolling 30 days, compared against the prior 30-day block). Daily readings are noisy below roughly 300 consignments per day. | | **Alert trigger** | `>3%`. The healthy German domestic baseline is 1.5 to 2.5 percent; EU cross-border lanes run higher because of customs holds. A reading above 3 percent across the blended book is the page-the-ops-team line. | | **Roles** | owner, operations | ## 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). | Lane | Consignments (30D) | With an exception scan | Exception rate | | ------------------------- | ------------------ | ---------------------- | -------------- | | DHL Paket domestic (DE) | 34,200 | 615 | 1.8% | | DHL Parcel EU (DE to AT) | 2,140 | 124 | 5.8% | | DHL Parcel EU (DE to CH) | 980 | 142 | 14.5% | | **All lanes (this card)** | **37,320** | **881** | **2.4%** | 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)](/nerve-centre/kpi-cards/deutsche-post/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](/nerve-centre/kpi-cards/deutsche-post/late-shipments) in 24 to 48 hours and on [Failed Deliveries](/nerve-centre/kpi-cards/deutsche-post/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](/nerve-centre/kpi-cards/deutsche-post/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](/nerve-centre/kpi-cards/deutsche-post/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: | Card | Why pair it with Exception Rate | What the combination tells you | | --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Failed Deliveries](/nerve-centre/kpi-cards/deutsche-post/failed-deliveries) | The subset of exceptions that ended in a genuine non-delivery. | Typical conversion is 15 to 30 percent: most exceptions self-resolve via redirect, the rest become failures. A rising ratio means the network is not recovering exceptions. | | [Late Shipments](/nerve-centre/kpi-cards/deutsche-post/late-shipments) | The downstream timing impact 24 to 48 hours later. | An exception spike today is a late-shipment spike tomorrow. Watch the lag. | | [Open Claims](/nerve-centre/kpi-cards/deutsche-post/open-claims) | Damage and loss exceptions escalate into Nachforschungsauftrag claims. | Only damage / loss exceptions feed claims; recipient-not-home does not. Use this card to predict claim inflow. | | [Returned to Sender](/nerve-centre/kpi-cards/deutsche-post/returned-to-sender) | Unresolved exceptions eventually trigger an automatic Rücklauf. | After the DHL retention window, an undeliverable parcel returns to the warehouse: lost margin plus a refund. | | [First-Attempt Delivery Rate](/nerve-centre/kpi-cards/deutsche-post/first-attempt-delivery-rate) | The inverse view of the recipient-not-home bucket. | Low first-attempt success and high exception rate together point to a home-delivery (rather than locker) addressing problem. | | [Label Generation Success](/nerve-centre/kpi-cards/deutsche-post/label-generation-success) | Upstream label-data quality. | Bad address data on the label is the most common controllable cause of an undeliverable exception. | | Cross-connector: [`shopify.refund_rate`](/nerve-centre/kpi-cards/shopify/refund-rate) | Downstream commercial impact. | An exception-rate spike of 1 point typically precedes a 0.3 to 0.8 point refund-rate rise at 7 to 14 days. | | Cross-connector: [`australia_post.exception_rate`](/nerve-centre/kpi-cards/australia-post/exception-rate) | Adjacent single-carrier peer for agencies running both. | Compare rates, not raw counts; the carriers handle different volumes and exception taxonomies. | ## Reconciling against the source **Where to look in Deutsche Post / DHL's own tooling:** The merchant-facing record lives in the [DHL Geschäftskundenportal](https://www.dhl.de/de/geschaeftskunden.html) (Business Customer Portal) under **Sendungsübersicht → Status / Ereignisse**, filtered to exception statuses. The public per-parcel scan history is the [DHL Sendungsverfolgung](https://www.dhl.de/de/privatkunden/dhl-sendungsverfolgung.html) 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:** | Reason | Direction | Why | | ---------------------------------- | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Time zone (CET/CEST vs UTC)** | Boundary days off | DHL scan timestamps are in carrier-local German time (CET in winter, CEST in summer). The card stores in UTC. Over a 30-day window this washes out to under 1 percent, but a single-day comparison can shift parcels across the date boundary. | | **Tracking-event ingestion lag** | Ours can lag | The DHL tracking feed publishes scans in batches; latency runs from a few minutes to several hours at peak. A parcel that threw an exception 30 minutes ago may not yet be in our index, so a live comparison against the portal can show us slightly low. | | **Exception taxonomy mapping** | Either | DHL exposes dozens of `standardEventCode` values; we collapse them into a smaller set of buckets. If the portal counts a status we treat as a normal redirect (or vice versa), the totals diverge. The mapping is documented and stable. | | **Once-per-shipment vs per-event** | Ours lower | The portal's event log lists every exception scan; this card counts a shipment once no matter how many exception scans it threw. A parcel held, then re-attempted, then held again is one exception here, three lines in the portal. | | **Return-leg inclusion** | Ours lower if returns-heavy | The portal's default view often includes Retouren-Etikett consignments. The card excludes inbound. | **Cross-connector reconciliation:** | Card | Expected relationship | Causes of legitimate divergence | | ---------------------------------------------------------------------------------- | --------------------------- | ------------------------------------------------------------------ | | [`shopify.unfulfilled_orders`](/nerve-centre/kpi-cards/shopify/unfulfilled-orders) | Upstream input. | Webhook failures, manual fulfilment delays, B2B / pre-order flows. | | [`shopify.refund_rate`](/nerve-centre/kpi-cards/shopify/refund-rate) | Downstream sentiment proxy. | Refund rate has many drivers; exceptions are one input. | ***
Documentation cross-reference (for agencies running multiple carriers) Exception-rate metrics exist with conceptually similar definitions across other carriers. These are not parallel measurements of the same shipments. * [`australia_post.exception_rate`](/nerve-centre/kpi-cards/australia-post/exception-rate) (single-carrier peer) * [`royal_mail.exception_rate`](/nerve-centre/kpi-cards/royal-mail/exception-rate) (single-carrier peer)
## 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)](/nerve-centre/kpi-cards/deutsche-post/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](/nerve-centre/kpi-cards/deutsche-post/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](/nerve-centre/kpi-cards/deutsche-post/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](/nerve-centre/kpi-cards/deutsche-post/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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.