Skip to main content
Metrics type: Key Metrics • Category: Shipping & Courier
DPD’s flagship ‘Predict’ promise - did the parcel arrive in the customer-notified 30-min / 1-hour window? Below 92% means the brand promise is breaking and customers paid premium for nothing.

​
At a glance

Share of DPD Predict consignments that arrived within the predicted 1-hour or 30-minute time window the customer was notified about. Predict is DPD’s flagship customer-experience product: the day before delivery, the recipient gets a 1-hour window (“your driver will arrive between 14:00 and 15:00”) via SMS / email / DPD app. The promise is concrete: arrival inside that window counts on-slot. Arrival before the window opens, after the window closes, or on a different day all count off-slot. The brand’s premium pricing on Predict-tier services is paid for this specific promise; if it breaks, customers paid extra for nothing.

​
Calculation

Calculated automatically from your DPD 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 DTC wine subscription brand based in West London, around 3,200 Predict NextDay consignments per month, 80 percent residential delivery, 20 percent office. Customers pay £6.99 for delivery on top of the subscription; the brand markets the 1-hour window as a key benefit. Reading taken at 09:00 GMT on 12 Mar 26 for the trailing 30 days (10 Feb 26 to 11 Mar 26). The card reads 93.7 percent on the dial, the alert at <92% is not tripped at the aggregate level. Five things to notice:
  1. The headline hides geographic spread. London is at 95 percent, Highlands at 82 percent, the aggregate sits comfortably above the alert because London is 59 percent of the volume. If the brand acquired 200 new customers in Inverness next month, the aggregate could drop below 92 percent without any operational change. Always look at the per-region split alongside the headline.
  2. “Off-slot” is mostly “delivered earlier than promised”, not late. Of the 201 off-slot deliveries, roughly 130 (65 percent) were delivered before the window opened (the driver was running ahead of schedule and chose to deliver rather than wait). DPD’s own definition counts this off-slot, customers experience it as “the parcel arrived before the SMS said it would”. Cross-reference with On-Time Delivery Rate: the same 201 parcels are mostly on-time on OTD but off-slot on this card. The two metrics tell different stories.
  3. The 71 truly-late (after window) deliveries are the customer-experience loss. A wine customer who was notified “between 14:00 and 15:00” and received the parcel at 15:42 is the customer who calls customer service. Each is a goodwill-credit candidate.
  4. The Predict promise is only as good as the SMS / email getting through. Of customer complaints about “Predict didn’t work”, 30 to 40 percent are not actually slot-accuracy issues, the customer never received the notification (filtered as spam, wrong mobile number, opted out of marketing emails). Pair with the merchant’s email-deliverability and SMS-OTP success rates.
  5. The “rate suddenly degraded” debug case. A 4 to 8 point sudden drop in Predict accuracy is rarely DPD’s network failing; it is almost always (a) DPD adding a new sortation hub that has not yet stabilised its routing, (b) a peak-period (Q4 BFCM, Christmas, Mother’s Day) where DPD pre-emptively widens windows to 2 hours but the dispatch system is still reading the 1-hour version, or (c) a depot capacity issue at one specific UK depot (Bristol, Hinckley, and Smethwick are perennial bottlenecks). Pair with OTD by Route to localise.

​
Sibling cards merchants should reference together

Predict slot accuracy is a customer-experience metric. Pair it with these to read the full Predict story:

​
Reconciling against the vendor’s own dashboard

Where to look in DPD’s own portal: DPD Customer Portal → Reports → Predict Performance. The portal exposes per-account Predict accuracy across the same 30-day window, broken down by depot. The aggregate matches the card. For account-managed customers, DPD’s QBR slides include a Predict accuracy breakdown by depot, by service tier (1-hour vs 30-minute), and by failure reason (driver early, driver late, slot mis-issued). Why our number may legitimately differ from DPD’s portal: Internal identity (within DPD): predict_off_slot_count = predict_consignments × (1 - predict_slot_accuracy). The breakdown of off-slot into “early”, “late”, and “wrong day” is on the deeper drill-down view; the card surfaces only the rate. Cross-connector reconciliation:
Documentation cross-reference (DPD-specific). Predict slot accuracy is unique to DPD on the UK shipping connector set; no peer card exists on Royal Mail, Evri, or APC because those carriers do not issue 1-hour customer-facing slots. The closest peer is APC’s NextDay-9am SLA, which is a hard cutoff rather than a window.

​
Known limitations / merchant FAQs

Why does DPD count “delivered early” as off-slot? The customer got the parcel. Because the customer was at home / in the office during the promised window and was not there earlier. A wine subscription customer who was promised 14:00 to 15:00, then received the parcel at 13:15 on their doorstep, often missed it (parcel was carded, refused, or stolen). DPD’s definition centres on “the customer is ready in the window they were told”; arriving outside the window misses that promise even if the parcel is delivered. My Predict accuracy is below 92 percent, what is the playbook? In order of likelihood: (1) Check OTD by Route, the drop is usually concentrated in 2 or 3 depots. (2) Check whether DPD has rolled out a routing-software change (DPD pushes route-optimisation updates roughly twice a year; the first 7 to 14 days after a rollout often see a 2 to 4 point dip while drivers adjust). (3) Check the merchant’s volume mix, a sudden surge of Highlands or rural orders pulls the headline down because rural slots are inherently noisier. (4) Check whether the dispatch system is using the latest Predict slot, if the system caches the original 1-hour slot and DPD has refined to 30 minutes, the card scores against the wrong window. (5) Open a ticket with DPD’s account team for depot-level escalation. Should I market the Predict promise to my customers? Only if the card sits at 95+ percent steady-state. Below 95 percent the marketing creates more disappointment than delight. The promise is concrete and customer-checkable; if the brand promotes “1-hour delivery window” but only hits it 90 percent of the time, the 10 percent are loud (review-site complaints, social media). Either market it heavily and run the network at 96+ percent, or do not market it and let the slot accuracy be a quiet bonus. Why is Predict only 82 percent in Highlands and Islands? Geography. Rural routes have longer drive times between deliveries; one delayed customer interaction (signature collection, conversation, finding the address) cascades through the rest of the round. A 1-hour slot in central Inverness has roughly the same accuracy as an urban slot; the moment the route extends to outlying farms and crofts, the cumulative slip per stop adds up. DPD’s published Predict accuracy on Highlands routes tracks this; expect 78 to 86 percent and treat it as the regional benchmark, not the network’s failure. My customer says the SMS came after the parcel, what happened? Three usual causes. (1) Mobile carrier delay, especially Three UK and overseas roaming. (2) The customer opted out of SMS marketing, which can suppress the Predict notification in some configurations. (3) The driver was significantly ahead of schedule and DPD’s app pushed the notification too late. The card scores the slot that was communicated, not the one that should have been; if the SMS landed 10 minutes after delivery, the slot in the SMS may still match the actual delivery time on paper. Does this card include 30-minute Predict? Yes. 30-minute Predict is a premium add-on (some merchants use it for high-value B2B parcels) and uses a tighter 30-minute window. The card uses whichever window was issued; 30-minute consignments are evaluated against their 30-minute window, 1-hour against 1-hour. Aggregating across both is fine; if 30-minute is small volume, the headline is dominated by 1-hour. Why is DPD’s portal showing higher Predict accuracy than this card? Most often: (1) Driver-early grace, DPD’s portal sometimes treats driver-early-by-5-minutes as on-slot. (2) Failed-delivery exclusion, DPD’s portal sometimes excludes failed-delivery consignments from the denominator; this card includes failed-attempt-then-redelivered as off-slot. (3) Slot definition, DPD’s portal sometimes uses the original 1-hour slot rather than the refined 30-minute slot. Predict went down 6 points overnight, is DPD broken? Probably not. Three more likely causes. (1) DPD added or moved a sortation hub, parcels are temporarily mis-routed during the cutover. (2) A peak-period flag was activated, DPD widens windows during BFCM, Christmas, and Mother’s Day; if the dispatch system reads the old narrow window, the wider actual delivery time scores off-slot even though DPD’s network is performing fine. (3) A specific depot has a capacity issue, check OTD by Route for the depot-level signal.

​
Tracked live in Vortex IQ Nerve Centre

Predict Slot Accuracy (30-min / 1-hour) is one of hundreds of KPI pulses Vortex IQ tracks across DPD 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.