At a glance
Count of Parcelforce Worldwide consignments that missed their service-day delivery promise in the period. Parcelforce, Royal Mail’s express arm, sells time-definite SLAs (Express9, Express10, ExpressAM, Express24, Express48, Globaldirect for international). “Late” is judged against each service’s specific cutoff time on the promised day. Each shipment that overruns scores 1.
| What it counts | COUNT(shipments WHERE actual_delivery_datetime > promised_delivery_datetime AND status IN ('DELIVERED','FAILED')) over the rolling 7-day window. Still-in-transit parcels are not counted yet; they flip into the count only when a final scan lands. |
| Delivery success criterion | Parcelforce delivery scan or signature-on-glass event captured by the driver. A consignment with a “Delivered” status but no scan still counts as delivered (rare but happens in remote depots). Carded / failed-attempt parcels do not satisfy on-time until rescheduled and successfully delivered. |
| On-time threshold | Promised cutoff time on the promised date. Parcelforce Express9 missing 09:00 by even 5 minutes is late. Express10 (10:00), ExpressAM (12:00), Express24 (end-of-day next working day), Express48 (end-of-day day-2). No grace period is applied. Parcelforce’s published service definitions are the contract; Vortex IQ honours them as written. |
| Returns / RTO | Returns to sender are excluded (tracked on par_returned_to_sender). Failed-and-redelivered parcels score against the first attempted delivery; a parcel re-attempted on day 2 and successfully delivered is late. |
| Service level scope | All services pooled. Express9, Express10, ExpressAM, Express24, Express48, plus Globaldirect international and any Saturday uplift, are all in the headline count. Service-by-service split is on par_shipments_by_service; the dedicated Express24 SLA card is parcelforce_express24_otd. |
| Money-back-on-late eligibility | Parcelforce offers service-failure refunds on its time-definite tiers (Express9, Express10, ExpressAM, Express24) where Parcelforce was at fault. International Globaldirect has a separate SLA structure with different refund terms. Filing window typically 30 days from the failed POD (longer than APC’s 14-day window). The card surfaces candidates; pair with par_open_claims. |
| B2B vs B2C | Pooled. B2B accounts use Express9 / Express10 / ExpressAM heavily; B2C uses Express24 and Express48. Same parcel that is “5 minutes late at 9:05” is critical for a B2B audience and immaterial for a Saturday consumer; the count treats them identically. |
| Failure-cause attribution | Parcelforce publishes a failure_reason per failed attempt: most common are recipient absent, no safe place / no neighbour, access denied, out for delivery, not delivered (driver returned to depot). Customer-fault and carrier-fault sit in the same headline; par_exception_rate splits. |
| Royal Mail vs Parcelforce relationship | Parcelforce is Royal Mail’s premium parcels arm and operates a separate network from Royal Mail’s tracked-letter service. A merchant using Royal Mail Tracked-24 alongside Parcelforce Express24 should treat them as different carriers with different SLAs; this card covers Parcelforce only. |
| Time zone | All scan timestamps in UK local time (GMT or BST). Globaldirect international scans are in destination time and are not yet normalised. |
| Time window | 7D (rolling 7 days, period-over-period vs the prior 7 days). |
| Alert trigger | >5% of total, the count tripping more than 5 percent of total shipments in the same 7-day window flips amber. For Parcelforce premium volume that target is roughly twice as strict as standard parcel networks would tolerate. |
| Roles | owner, operations |
Calculation
Calculated automatically from your Parcelforce Worldwide 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 merchant: £320 average-order-value laptops and accessories, mix of consumer DTC and corporate B2B sales (a small reseller channel). Parcelforce Express24 is the consumer carrier (signature-required, fully-tracked, end-to-end scans); Parcelforce Express9 is used for the B2B reseller book where corporate IT teams need stock before staff start the working day. Reading taken at 09:00 GMT on 13 Mar 26 for the trailing 7 days (06 Mar 26 to 12 Mar 26).| Service | Shipments (7D) | Late (POD after promised cutoff) | Late % | Notes |
|---|---|---|---|---|
| Express24 (consumer DTC) | 920 | 38 | 4.1% | 30 delivered same-day after 17:30; 8 delivered day-2. |
| Express9 (B2B reseller) | 142 | 4 | 2.8% | All four delivered between 09:01 and 09:18; service-failure refund candidates. |
| ExpressAM (mixed) | 56 | 2 | 3.6% | Both day-2 deliveries in the South-West. |
| Globaldirect (international, EU) | 28 | 3 | 10.7% | Customs-clearance delay on three Italy parcels; not Parcelforce’s fault but counts. |
| Total (this card) | 1,146 | 47 | 4.1% |
>5% of total is not tripped at the aggregate level. Five things to notice:
- Money-back-on-late candidates: ~38 Express24 + 4 Express9 = 42 domestic premium shipments. Each is a candidate for Parcelforce service-failure refund on the carriage charge (typically £6 to £14 per shipment for Express24 / Express9). At an estimated £9 average refund, that is £378 of recoverable carriage if the merchant files within Parcelforce’s 30-day window.
- The 8 day-2 Express24 parcels are worse than the 30 same-day-late. Customer paid for “by end of next working day”; receiving the parcel on day 2 is a clean broken promise. These are likely £20 to £40 goodwill credits on the order itself, ~£200 of margin loss across 8 orders, plus the £72 Parcelforce refund.
- Globaldirect 10.7% is mostly customs, not Parcelforce. International EU parcels post-Brexit run customs-clearance delay risk on every consignment. Parcelforce’s API publishes a
failure_reason: customsin these cases. Vortex IQ counts them in the headline because the customer experiences the lateness regardless; for refund eligibility, customs delays typically don’t qualify. - The 4.1% headline does not fail the alert, but is uncomfortable on a multi-thousand weekly volume. Parcelforce’s network is one of the most reliable in the UK premium tier; if late% is at 4.1% week-on-week, look at dispatch-cutoff slippage on the merchant side (see
par_route_otd). - Compare against the same week last year. 13 Mar 25 reading was 2.4 percent; the rise to 4.1% is the real story. Most likely cause: the recent product launch lifted DTC volume past the merchant’s negotiated daily collection capacity, pushing afternoon orders into next-day-collection cohorts. Pair with
par_shipments_totalfor volume confirmation.
Sibling cards merchants should reference together
Late count is a count, not a rate. To act, pair it with these:| Card | Why pair it with Parcelforce Late Shipments | What the combination tells you |
|---|---|---|
| On-Time Delivery Rate | The percent companion. Late count rising while OTD% stays flat means volume up, not service. | If OTD% drops and late count rises, both proportional and absolute degradation, that is the real ops issue. |
| Express24 Service Day Promise | Parcelforce’s most-used premium service. Late count is dominated by Express24 in most DTC merchants. | An Express24 SLA dip drives most of the late count even when the network looks healthy. Always check Express24 first. |
| OTD by Route | Splits the count by Parcelforce’s depot-and-route network. | One-route drops are an account-team conversation; network-wide drops are a peak-period or weather event. |
| Open Claims | Each late premium shipment is a service-failure-refund candidate. Filing rate vs late count tells you if you are recovering carriage. | If late count is 50 and open-claims is 8, the merchant is leaving £350+ of carriage refunds per week unclaimed. |
| Failed Deliveries | Sister metric. Some late shipments are also failed-first-attempt; some failed parcels are still on-time after rescheduling. | Late minus Failed roughly equals “would-be-on-time-if-rescheduled-faster” parcels, the controllable bucket. |
| Saturday Delivery Uplift ROI | If you pay Saturday uplift to recover Friday-late parcels, this card tracks that economic decision. | Late-shipment rise on Fridays + low Saturday-uplift ROI = the uplift is not solving the right problem. |
| Parcelforce OTD by Sales Channel | Cross-channel. A late spike that is all DTC and zero B2B reseller tells you it is a consumer-experience problem first. | Channel mix in the late count matches the channel mix of customer-service tickets a day later. |
Cross-connector: shopify.unfulfilled_orders | Upstream. Shopify orders booked too late in the day cannot make Parcelforce’s same-day collection cutoff. | A creep in late-day Shopify orders predicts a 1 to 3 day late-shipment rise on this card. |
Cross-connector: apc.apc_late_shipments_count | Peer UK premium shipper. Useful only on multi-carrier merchants. | If APC and Parcelforce both spike at the same time, the cause is upstream (warehouse, dispatch); if only one, it is carrier-specific. |
Reconciling against the vendor’s own dashboard
Where to look in Parcelforce’s own dashboard: Parcelforce ParcelManager → Reports → Failed / Late Deliveries. Filter by All services / All depots / Last 7 days. The closest like-for-like view is the Service Failure Count report. ParcelManager also exposes a per-consignment audit at Track and Trace → Failed Deliveries with the gap between scheduled and actual POD. Why our number may legitimately differ from Parcelforce’s portal:| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary days off | ParcelManager defaults to UK local time. The card defaults to UK local time. DST-transition Sundays cause one-hour boundary noise. |
| Refund-eligible vs all-late | Ours higher | Parcelforce’s account-team often quote a service-failure count that excludes customer-fault, address-fault, customs delays. The card’s count is all consignments delivered after promised cutoff regardless of fault, because that is what the customer experienced. |
| In-transit consignments | Ours rolling | Consignments without a final POD are not counted yet (cannot be late while still in transit). As they deliver, the count grows. ParcelManager’s tile may include “in-transit, predicted late” as a separate slice; the card does not. |
| Globaldirect customs | Ours higher | Customs holds add transit days that Parcelforce attributes to failure_reason: customs. The card counts the customer-experienced lateness regardless. The Parcelforce-fault-only view in ParcelManager will show a lower count. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
shopify.fulfillment_lead_time | Upstream causation. Late Shopify fulfilment cannot make Parcelforce’s same-day collection cutoff. | App-install events, manual fulfilment overrides, B2B / pre-order workflows. |
apc.apc_late_shipments_count | Peer UK premium shipper. | Different consignments. Useful for shop-around, not reconciliation. |
royal_mail.rm_late_shipments_count | Value-tier sister carrier, same parent group. | Different parcel populations. |
Known limitations / merchant FAQs
Why is the count more useful than the rate for our weekly ops review? Counts are absolute; rates compress. A 4.1% late rate at 1,000 weekly shipments is 41 misses; the same 4.1% at 5,000 weekly shipments is 205 misses. The CS-team workload, the carriage-refund opportunity, and the customer-perception cost all scale with the count, not the rate. Use the rate (par_otd_rate) for trend; use the count for capacity-planning the response.
How do we file Parcelforce service-failure refunds at scale?
ParcelManager exposes a Service Failure Claim form per consignment. Most merchants over a £5K-per-month spend negotiate with their Parcelforce account manager to enable bulk-claim CSV upload (an account-team feature, not self-serve). The card surfaces candidates; the workflow lives in Parcelforce’s portal. Filing window is 30 days from the failed POD, longer than APC’s 14-day window. A reasonable target is to claim 60% of eligible misses; below that, you are leaving carriage refunds on the table.
Why does the count look fine but customer-service tickets are climbing?
Two reasons. First, complaint mass scales with premium-paid cohort size. A handful of missed Express24 Christmas parcels generates a disproportionate complaint load because customers chose the premium-paid tier specifically to avoid lateness. Second, social-media echo: a single visible tweet about a missed parcel multiplies the perceived issue. Counts of 10 to 30 per week can feel like 200 if they cluster on premium-paid weekend orders. Pair with parcelforce_express24_otd to see the premium-paid-cohort-only count.
Saturday delivery is expensive; is the lateness count justifying the spend?
Track parcelforce_saturday_uplift_roi. The Saturday uplift recovers Friday-late-cohort consignments that would otherwise fail Express24’s “next working day” promise. If the uplift is recovering 80% of weekend-paid parcels, it pays for itself; if it is recovering 30%, drop it and let Friday-cohort consignments fail openly so customers self-select into Express48 instead.
A consignment was delivered “Out for delivery, returned to depot” then again the next day. Does it count once or twice?
Once. The card scores each consignment by its final successful POD datetime. A failed first attempt that re-attempted and delivered on day 2 of an Express24 is one late consignment. Failed-and-redelivered counts are split on par_failed_delivery_count; that card may run higher than this one because of repeats.
B2B Express9 misses cost more than B2C Express24 misses; how do we surface that?
The card is a count, not a value. Use par_open_claims for the financial-exposure view (claim value of B2B contract penalties dwarfs consumer goodwill credits) and parcelforce_xc_otd_by_channel for the channel split. A 5-shipment B2B Express9 miss week may carry more business risk than a 50-shipment B2C Express24 miss week.
Globaldirect international customs delays inflate our count; can we filter?
Today, no automatic filter; track international separately on par_shipments_by_destination. Most multi-destination merchants set up two weekly reviews: domestic-only against the alert threshold, international as a separate line. Customs delays are typically not service-failure-refund eligible; tracking them in the same dial as domestic misses would mask the controllable signal.
What is the relationship to par_otd_rate?
par_late_shipments_count is the absolute numerator over the denominator’s complement. If late count is 47 and total shipments is 1,146, OTD rate = (1,146-47)/1,146 = 95.9%. The two cards are mathematical mirrors; what differs is the time window (this card 7D, OTD card 30D) and the response. Counts trigger CS-team capacity decisions; rates trigger account-team conversations.
During Q4 peak, the count triples. Do we widen the alert threshold?
No. Widen the seasonal context in your weekly review instead. The alert is a fixed threshold so the system does not “learn to ignore” Q4 degradation. The action is to pre-position dispatch capacity in October, negotiate Q4 surcharges with Parcelforce in advance, and update checkout copy to set realistic delivery dates. The count card is intentionally honest during peak.