At a glance
Real-time count of DPDLocal compensation claims that are open and unsettled. Each claim represents a damaged, lost, mis-delivered, or significantly-delayed consignment where the merchant is seeking financial recovery from DPDLocal under the carrier’s liability terms. Cash trapped + customer trust at risk.
Calculation
Calculated automatically from your DPDLocal 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 UK premium-electronics DTC retailer ships ~3,000 DPDLocal NextDay parcels per month, AOV £180. Reading taken at 09:00 GMT on 12 Mar 26.
The card reads 11. The alert fires because 5 claims (the
under_review and awaiting_evidence rows) are >7 days old. Three things to notice:
- The 5 ageing claims are roughly £880 of cash trapped. At 11 open claims with average value £175 the total open exposure is ~£1,925; the >7d cohort is the actionable subset because the 14-day resolution SLA is at risk.
awaiting_evidenceis on the merchant, not DPD. Two claims are stalled because the customer has not yet sent damage photos via the CS workflow. A nudge email and a 7-day deadline-or-withdraw policy clears these. Pair with Open Claims Without Jira Ticket to surface CS-coverage gaps.- Premium-electronics merchants run claim rates 2 to 5 times higher than average. High-AOV, fragile goods see more DAMAGED claims. The threshold should reflect category baseline; 11 open is healthy for this merchant, would be elevated for a fashion DTC at the same volume.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in DPDLocal’s own dashboard: MyDPD Business Portal → Claims. Each claim has a status (open, under_review, awaiting_evidence, settled, denied, withdrawn). Filter on the open statuses to compare against this card’s count.
Why our number may legitimately differ from MyDPD:
Cross-connector reconciliation: