At a glance
A real-time count of orders that have passed their despatch deadline today without a PostNord label being generated or a manifest handover being recorded. This is the upstream warning that sits before every delivery metric: a parcel that misses its cut-off in your warehouse cannot meet PostNord’s transit aim no matter how well the carrier performs. The card fires the moment more than five orders sit past their deadline, so your despatch desk can clear the backlog before it becomes tomorrow’s late-delivery and “where is my order” workload.
| What it counts | Orders whose internal despatch-by time has passed in the current local day and that have no recorded PostNord label or manifest event. Each unfulfilled order counts once until a label is generated or the order is cancelled. |
| Data source | detail: alerts for Dispatch SLA Breach on N Orders Today. The count joins your order feed (Shopify / BigCommerce / Adobe unfulfilled_orders) against PostNord label and manifest events from GET /shipments/v1/manifests and the label-generation log. An order is “breached” when now > dispatch_deadline and no label_created or manifest_handover event exists. |
| Time window | RT (real time). The count is evaluated continuously through the working day and resets on your local despatch-day boundary. |
| Alert trigger | >5 orders past dispatch deadline. Five is a deliberately low floor: it catches a stalling despatch line early rather than waiting for a percentage of the day’s volume to slip. |
| Despatch deadline source | Your configured carrier cut-off (the time after which PostNord same-day collection is missed). For most Nordic merchants this is a single afternoon collection slot (commonly 14:00 to 16:00 local), so the breach window opens sharply once that slot passes. |
| Scope | Outbound orders only. Returns, cancellations, and orders flagged as pre-order / backorder are excluded so the count reflects genuinely shippable work. |
| Roles | owner, operations |
Calculation
Calculated automatically from your PostNord and order 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 Gothenburg-based DTC supplements brand on Shopify, around 600 orders a day shipped on PostNord MyPack Mailbox, single afternoon collection at 15:00 CET. Reading taken at 14:20 CET on 14 Mar 26.| Time (CET) | Orders awaiting label | Orders past 15:00 cut-off | Card reads |
|---|---|---|---|
| 11:00 | 180 | 0 (cut-off not yet relevant) | 0 |
| 14:20 | 47 | 0 (still before cut-off) | 0 |
| 15:05 | 31 | 31 | 31 (alert tripped) |
| 16:30 | 4 | 4 | 4 (alert cleared) |
>5 orders is firing. Five things to notice:
- This is a leading indicator, not a lagging one. None of these 31 orders is late yet: they have simply missed today’s PostNord collection. But every one of them will start tomorrow a day behind, which means On-Time Delivery Rate and Late Shipments will degrade in 24 to 72 hours unless the desk clears them.
- The cause is usually upstream of PostNord entirely. A breach spike at cut-off almost always means a picking bottleneck, a printer outage, or a stock-out holding orders open. Check Label Print Failures Spike first: if labels are failing, the orders are stuck at the print step, not the pick step.
- 31 breached orders is roughly 31 customer-service contacts in waiting. A despatch delay that pushes delivery past the promised date converts to WISMO tickets at a high rate for supplements buyers who reorder on a cycle. Treat the count as tomorrow’s CS workload.
- Clearing late beats missing entirely. By 16:30 the desk has cut the backlog to 4 orders by booking an ad-hoc PostNord pickup or driving the remainder to a PostNord service point. Four is below the alert floor, so the alert clears. A late-day manual handover saves the OTD hit even though the standard collection was missed.
- A persistent non-zero floor is a capacity problem. If this card sits at 8 to 12 every afternoon, the despatch line cannot clear the day’s volume by cut-off. That is a staffing or second-collection-slot decision, not a daily firefight. Use Shipments Over Time to confirm whether volume has grown past the line’s throughput.
Sibling cards merchants should reference together
Dispatch SLA breach is the earliest operational alarm in the PostNord chain. Pair it with these to find the cause and forecast the downstream cost:| Card | Why pair it with Dispatch SLA Breach | What the combination tells you |
|---|---|---|
| Label Print Failures Spike | Failed labels hold orders at the print step. | If breaches climb at the same time as label failures, the bottleneck is label generation, not picking. |
| PostNord Tracking API Unavailable / 5xx | API outages stop labels being created at all. | A breach spike with a concurrent API outage means PostNord is down, not your warehouse. Switch to a fallback carrier or hold. |
| Orders with Dispatch SLA Missed | The 7-day order-level view of the same breach. | This real-time card is today’s firefight; the cross-channel card is the trend and the revenue-at-risk total. |
| On-Time Delivery Rate | The downstream outcome a despatch breach feeds. | A despatch-breach day predicts an OTD dip 1 to 3 days later. |
| Late Shipments | The absolute count of parcels that arrived late. | Today’s breach count is a forecast of tomorrow’s late-shipment count. |
| Shipments Over Time | Volume trend against despatch capacity. | If breaches rise with volume, the line is at capacity; if breaches rise on flat volume, the process broke. |
Cross-connector: shopify.unfulfilled_orders | The raw pool of orders awaiting a label. | A climbing unfulfilled count is the reservoir this breach count draws from. |
Reconciling against the source
Where to look in PostNord’s own tooling: Open the PostNord Business Portal and the PostNord Customer Service / Booking (Kundeservice) area. The closest like-for-like view is the day’s manifest / booking list: count the orders in your store’s order feed with a despatch deadline before “now” today, then subtract the parcels that appear on today’s PostNord manifest with a label generated. The remainder is the breach count. The card also reads the manifest handover stream (GET /shipments/v1/manifests), so an order with a printed label that has not yet been handed to PostNord still counts as breached until the manifest event lands.
Why our number may legitimately differ from the portal:
| Reason | Direction | Why |
|---|---|---|
| Tracking-event ingestion lag | Ours can lag | PostNord pushes manifest and label events in batches; a label generated 5 minutes ago may not be reflected yet, so a just-cleared order can show as breached for a short window. |
| Carrier-local time | Boundary off | PostNord scan and manifest timestamps are recorded in carrier-local time (CET / CEST for SE / DK, plus the relevant local zone for NO / FI). An order booked near midnight can land on a different calendar day in the portal than in the card. |
| Despatch deadline definition | Either | The portal does not know your internal despatch-by promise; it only knows when a label was created. The breach is computed against your configured cut-off, so the two systems are measuring different things by design. |
| Manual / off-portal handovers | Ours higher briefly | A parcel driven to a PostNord service point clears the breach only once its scan ingests, which can lag the physical handover by minutes to a couple of hours. |