Skip to main content
Card class: HeroCategory: Shipping & Courier

At a glance

Live count of open claims filed against PostNord (lost in transit, damaged, contents missing) where the claim is currently unresolved AND has been open more than 7 days. Money on the table, each open claim represents lost or damaged inventory the merchant has refunded or replaced for the customer but not yet recovered from PostNord. The 7-day age filter excludes the normal claim-processing window and surfaces only the cases that have stalled.
What it countsCOUNT(claims WHERE status IN ('open','pending_documentation','under_review') AND age_days > 7). Pulled from GET /claims/v1/claims (PostNord Claims API).
Why 7 days?PostNord’s published claim-processing SLA is 5 to 10 business days for straightforward cases. The 7-day filter captures the normal window’s tail; claims older than 7 days are statistically those needing merchant escalation rather than waiting on routine processing.
Claim types coveredLOST_IN_TRANSIT (parcel never arrived), DAMAGED (arrived damaged, supported by photo evidence), CONTENTS_MISSING (parcel arrived but contents incomplete), WRONG_ITEM (rare, only when merchant fault is excluded), DELAY_COMPENSATION (Service Level Guarantee credit for missed Express SLA).
CurrencyAccount currency. The peer card Claim Value shows the monetary value of the open queue; this card is the count (because operational workload scales with count, not value).
Recovery rate contextPostNord’s published claims-recovery rate for documented cases is ~80 to 90 percent for DAMAGED, ~60 to 75 percent for LOST_IN_TRANSIT, ~40 to 60 percent for CONTENTS_MISSING (lower because evidence is harder). The card surfaces open claims; recovery happens when status flips to paid or partial_paid.
Refresh cadenceReal-time. PostNord’s claims endpoint updates within minutes of status changes; the card polls every 15 minutes.
Time windowRT (live unresolved >7d count).
Alert trigger>0 unresolved >7d. Any non-zero reading means the claims queue is stalled and money is sitting unrecovered.
Merchant impactEach open claim represents inventory cost the merchant absorbed (replaced or refunded the customer) plus the original shipping cost, money that PostNord owes but hasn’t paid. A 30-claim queue at typical Nordic AOV (€80) and full-replacement cost basis (€50 inventory + €8 shipping) is roughly €1,740 of unrecovered cost.
Rolesowner, operations, finance

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. The card displays:
17 open claims (>7 days unresolved)
Claim typeCountAvg age (days)Avg claim value (SEK)Estimated recoverable
DAMAGED811580~85% (€395 likely recovered per claim)
LOST_IN_TRANSIT614720~70% (€504 per claim)
CONTENTS_MISSING218410~50% (€205 per claim)
DELAY_COMPENSATION (Express SLA missed)19138~95% (€131)
Total open queue (this card)1712SEK 9,580~~SEK 7,250 (~~€660)
What this tells the merchant:
  1. 17 open claims at 12-day average age means the queue is moderately stalled. Healthy ops should drain claims to zero within 14 to 21 days from filing; 12 days average with 17 still open suggests roughly 30 percent of the active claim volume has stalled past PostNord’s normal processing window.
  2. The €660 estimated recoverable is real money. At this brand’s 60 percent contribution margin, that €660 recovered is equivalent to €1,100 of unfunded sales they’d otherwise need to make to net the same contribution. Worth the operational effort to chase.
  3. The 18-day-average CONTENTS_MISSING cases are the priority drain target. These have the lowest recovery rate (50 percent) AND the longest age, classic stalled-on-evidence pattern. PostNord typically requests photo evidence of the unboxed parcel and original packing manifest; many merchants don’t have that documentation captured at outbound, so the claim stalls. Action: implement an outbound-photo capture workflow at the warehouse for high-value SKUs.
  4. The 14-day-average LOST_IN_TRANSIT cases are routine. PostNord’s process for lost-parcel claims includes a 14-day “search window” before declaring the parcel lost; some of these will resolve naturally as the parcels are eventually found. Watch for cases past 21 days, those are unlikely to resolve and should be escalated to a human PostNord account manager.
  5. The 1 DELAY_COMPENSATION case is the easiest win. Service Level Guarantee credits on missed Express SLA are administratively simple, the SLA either was or wasn’t met, evidence is on PostNord’s own scan record. 95 percent recovery rate. If multiple Express-SLA misses are accumulating without claims being filed, the merchant is leaving money on the table; automate the filing workflow.
  6. The “queue suddenly grew” debug case. If the open count jumps from 5 to 25 in a single week, the cause is usually upstream: a major weather event 14 to 21 days earlier produced a wave of LOST or DELAYED claims that are now stalled at PostNord’s processing centre because the storm overwhelmed the team’s capacity. Plan additional ops capacity 2 weeks after every major weather event to chase the inevitable claims wave.

Sibling cards merchants should reference together

CardWhy pair it with Open ClaimsWhat the combination tells you
Claim Value (open)Monetary value of the open queue.Count drives operational workload; value drives finance escalation priority.
Exception RateUpstream signal.Exception rate up today predicts claim volume up in 14 to 21 days.
Late ShipmentsAdjacent CS-workload signal.Late count and claim queue compete for the same CS / ops attention.
Returned to SenderDifferent exception type.RTS shipments occasionally trigger CONTENTS_MISSING claims if returned items don’t match.
OTD RateOperational quality.Sustained OTD drops correlate with claim queue growth at 21-day lag.
Cross-connector: shopify.refund_rate, bigcommerce.bc_refund_rateRefunds the merchant has issued.Refund-rate spike paired with claim-count spike means the merchant absorbed losses for which PostNord may pay; chase claims aggressively.
Cross-connector: shopify.cogs_at_riskInventory cost exposure.Open-claim count × avg-COGS gives the unrecovered-cost exposure.
Cross-connector: bring.bri_open_claimsAdjacent Nordic carrier.Compare carrier claim-recovery efficiency for portfolio decisions.

Reconciling against the vendor’s own dashboard

Where to look in PostNord’s own portal: PostNord Business PortalClaims, filter on Status = Open and sort by Filed Date ascending. Apply a date filter for “Filed >7 days ago” to match this card’s threshold. The card’s headline count should agree with the portal to within 1 to 2 claims. Smaller divergences trace to the timing of status transitions during the 15-minute polling cycle. Why our number may legitimately differ from PostNord’s portal:
ReasonDirectionWhy
Polling cadenceOurs up to 15 minutes staleCard polls every 15 minutes; portal is real-time.
Time zoneBoundary days offPortal uses local TZ; card uses UTC. The “7-day age” threshold can shift by a day at TZ borders.
Status transition mid-pollEitherClaims that flipped from open to paid between polls show in the card briefly after the actual resolution.
Multi-account aggregationEitherMulti-country PostNord accounts aggregate to a single count on the card; per-account counts differ in each portal.
Manual claims (filed by phone / email)Ours lowerSome merchants file claims by phone with a PostNord account manager rather than via the API; those don’t show in the API until manually entered, leading to under-counting.
Claim categorisationSameBoth card and portal use PostNord’s published claim-status taxonomy; categories agree.
Cross-connector reconciliation:
CardExpected relationshipCauses of legitimate divergence
bring.bri_open_claimsSame metric, adjacent Nordic carrier.Different processing speeds and recovery rates by carrier; absolute counts not comparable, but the “queue stalling” pattern is universal.
shopify.refund_rate, bigcommerce.bc_refund_rateRefunds issued by the merchant.Each open claim corresponds to a refund or replacement the merchant absorbed; ratio gives the carrier-cost-pass-through rate.
shopify.cogs_at_riskInventory cost exposure.Open-claim count × avg COGS gives the unrecovered-inventory exposure.
PostNord Exception Rate and Late ShipmentsUpstream operational signals.Exception spikes drive claim volume at 14 to 21 day lag.

Known limitations / merchant FAQs

Why is the threshold 7 days? Shouldn’t I track all open claims? PostNord’s published processing SLA is 5 to 10 business days for routine claims. Tracking all open claims (including ones in normal processing) creates alert fatigue, the queue is always non-empty even when nothing is actually wrong. The 7-day filter surfaces only the stalled cases that need merchant action. Use Claim Value (open) for the total queue including in-processing. My open-claim count is 17 but I only filed 5 claims in the last 30 days. Why is the count higher? Claims persist in the open queue until they’re resolved (paid, partially paid, or rejected). The 17 represents the cumulative stalled queue across all unresolved historical claims that crossed the 7-day age threshold. If your queue is growing faster than you can resolve, the count grows faster than the filing rate. Pair with Claim Value to see the cumulative monetary exposure. What’s the playbook when the queue is growing? In order of impact: (1) Identify the oldest claims (>21 days) and escalate to your PostNord account manager directly; phone or email is more effective than portal messaging. (2) Identify the missing-evidence claims (CONTENTS_MISSING typically), and either supply missing photos / packing manifests or accept the loss. (3) Implement upstream evidence capture, outbound photos for high-value SKUs, packing-list snapshots, courier-handover scans. The cost of capture is small versus the cost of unrecoverable claims. (4) Quarterly account review with PostNord, large merchants (>10k parcels/month) typically negotiate a dedicated claims-handler relationship that meaningfully reduces stall rate. A claim has been open 25 days. Will I still recover the value? For DAMAGED with photo evidence: probably yes, escalate now. For LOST_IN_TRANSIT past 21 days: PostNord will usually pay if the parcel hasn’t been found by then; the search window is 14 days plus a 7-day documentation window. For CONTENTS_MISSING: depends on evidence quality; without strong evidence (warehouse photo of packed contents, shipping-weight discrepancy report) the recovery rate drops sharply after 14 days. Aged-out claims are not auto-rejected but become harder to substantiate. How does this differ from the customer-side refund I issued? This card tracks merchant-facing claims with PostNord. The refund or replacement to the customer was a separate transaction; the merchant has already absorbed that cost. The claim is the recovery process against PostNord. Open-claim count of 17 typically corresponds to 17 customer refunds the merchant has already paid; this card surfaces the unrecovered tail. Can I auto-file claims from Vortex IQ? Partial. Vortex IQ can identify claim-eligible events (DAMAGED scans, LOST_IN_TRANSIT timeouts, missed Express SLAs) and surface them for filing; the actual filing requires a human-in-the-loop step because PostNord’s claim form requires merchant-side documentation (purchase value, customer impact narrative, evidence files). Some merchants automate the easy SLA-credit cases; DAMAGED and LOST cases usually need human attention. My recovery rate is 50 percent. Is that good? Below the published norm. Healthy DTC merchants on PostNord recover 70 to 85 percent of claim value across all categories. 50 percent suggests either: (1) high CONTENTS_MISSING share (lower-recovery category by structure); (2) poor documentation discipline (claims filed without strong evidence); or (3) an account-relationship issue where PostNord’s claims team is treating your filings as low-priority. The fix is documentation upstream and account-manager relationship. Multi-account, does the card aggregate across PostNord SE / DK / NO / FI? Yes, FX-converted to display currency. Per-country drill-down shows native counts. Different countries have different claim-processing cultures; Sweden is typically faster than Finland; Denmark sits in the middle. Use per-country drill to compare. Does industrial action affect the claim queue? Yes, indirectly and significantly. Strikes during 2020 (Sweden) and 2022 (Denmark) produced 3 to 5× normal claim volume in the 14 to 30 days following the strike, as the LOST and DAMAGED tail surfaced. PostNord’s claims-processing capacity didn’t scale to match, so the open queue stalled. Plan for a 4 to 6 week stalled-queue window after any major industrial action. Should claim count be on a finance dashboard or operations dashboard? Both. Operations needs the count for workload planning; Finance needs the value (peer card) for cash-flow recognition (most accounting frameworks require recognising the recoverable as an asset only when probability of recovery is high; an aged stalled claim may need to be written off). The two dashboards serve different decisions on the same underlying data. Why include DELAY_COMPENSATION (Express SLA credits) here? Aren’t those automatic? They’re supposed to be automatic but in practice many merchants don’t claim them, leaving SLA credits unredeemed. The card surfaces them so the merchant can reconcile against PostNord’s auto-applied credits and chase any missing. Express SLA credits are the easiest claim category to recover (95 percent rate) but the most often forgotten.

Tracked live in Vortex IQ Nerve Centre

Open Claims 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.