Skip to main content
Metrics type: Key Metrics • Category: Shipping & Courier

​
At a glance

Absolute count of DHL InExpress shipments that delivered after their carrier-promised date in the last 7 days. The angry-customer gauge: each unit on this card is one customer who didn’t receive their parcel when you said they would. Companion metric to On-Time Delivery Rate, which measures the same population as a percentage.

​
Calculation

Calculated automatically from your DHL InExpress 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 homewares merchant shipping ~2,500 parcels per week via DHL InExpress, mostly to UK + IE + DE. Reading taken at 09:00 GMT on 12 Mar 26 for the trailing 7 days (06 Mar 26 to 12 Mar 26). The card reads 141 with the percentage in parentheses (5.6%). The alert at >5% of total is tripped. Five things to notice:
  1. 141 means 141 customers got a slip-of-paper “where is my order” email. That’s roughly 30 to 50 support tickets at the brand’s typical 25 to 35% complaint rate. Plan support-team capacity around the count, not the rate.
  2. Two cross-border lanes are doing all the damage. GB to DE and GB to FR together account for 87 of the 141 late shipments (62%) on only 27% of volume. The cross-border-customs story dominates: the customs leg is the differentiator, and the Customs Dwell Time by Lane card will tell you which side (UK export filing or destination clearance) is dragging.
  3. The 7-day window catches issues 30D smooths over. A burst of 60 late shipments on Tuesday 9 Mar (a customs-IT outage at Roissy, perhaps) is visible here; on the 30D card the same burst would barely move the needle.
  4. Compare to last week. If last week’s count was 88 (3.5%), this week’s 141 is a +60% jump. That’s the operational signal: investigate Tuesday 9 Mar specifically. Any sudden week-on-week jump >40% with the rate above 5% is worth a half-hour of root-cause work.
  5. 141 / 2500 = 5.6%, but 1 - 0.943 = 5.7% on the OTD card. Rounding artefact, the two are the same population. If they disagree by more than 0.5% the indices are out of sync; recheck period boundaries.

​
Sibling cards merchants should reference together

Late count is a volume number; it pairs naturally with the rate and the cause:

​
Reconciling against the vendor’s own dashboard

Where to look in DHL InExpress’s own dashboard: MyDHL+ portal → Track → Detailed View → Filter “Late deliveries” → set date range to last 7 days. Each row is one late shipment with its estimatedDeliveryDate, actualDeliveryDate, and the gap. The portal does not surface a single “late count” tile; the count comes from the row count of the filtered view. For UK exporters, the Customs & International report has a per-lane delay breakdown that is useful for diagnosing the cluster pattern this card surfaces. Why our number may legitimately differ from MyDHL+: Cross-connector reconciliation: Internal identity (within DHL InExpress): dhl_late_shipments_count = (1 - dhl_otd_rate) × dhl_shipments_total over the same window. If this card reads 141 over 2,500 shipments, On-Time Delivery Rate should be 94.4%. Discrepancies >1% indicate a sync gap.

​
Known limitations / merchant FAQs

My late count tripled this week. What do I check first? In order of likelihood:
  1. One bad lane. Slice by destination on OTD by Route. 80% of the time a single Brexit-era lane (UK to FR or UK to DE) caved while the rest held up.
  2. Customs documentation regression. A new SKU with missing HS codes, or a description-line change, can trigger holds for that SKU on every cross-border shipment. Check Duty-Billing Mismatch Rate.
  3. Carrier capacity. Pre-Christmas, pre-Easter, post-strike days run slow. Check the calendar, if it’s a known peak window, the dip is structural.
  4. Promised-date tightening. DHL revises transit-time tables periodically. If estimatedDeliveryDate is now tighter for the same lanes, late count rises mechanically.
Should I count “delivered late by 1 hour” the same as “late by 5 days”? The card scores both as 1. It does not weight by severity. For high-value shipments where a 1h slip is acceptable but a 5-day slip is a refund, look at the per-shipment audit table in MyDHL+. The card is the executive scoreboard, not the diagnostic deep-dive. Why is my late count higher in November and December every year? Q4 / Christmas peak puts customs queues, carrier networks, and DC operations all under simultaneous strain. UK to EU lanes typically run 2 to 3x the late count of a calm February week. Plan support-team capacity accordingly; don’t expect to clear the alert during peak. Is the count exclusive of cancellations? Yes. Cancelled shipments (intercepted before delivery, recipient refused at the door) are not counted as late. Returned-to-sender shipments are also excluded, they have their own card. What’s the difference between late shipments and failed deliveries? Late = delivered after the promised date. Failed = first delivery attempt failed (recipient not home, address invalid). A failed-delivery shipment usually delivers late on the second attempt; it then counts on both Failed Deliveries and this card. Does the card count B2B shipments? Yes. DHL InExpress is used for both DTC and B2B in many merchants’ setups. The card pools both. If you want to slice, the workspace admin can enable a customer_segment filter. Should I be worried if late count drops sharply with no operational change? Usually no, it tracks volume. A quiet week (post-promo, pre-launch) will have fewer total shipments and fewer late ones. Pair with On-Time Delivery Rate, if the rate held steady while count dropped, it’s a volume effect, not a performance change.

​
Tracked live in Vortex IQ Nerve Centre

Late Shipments is one of hundreds of KPI pulses Vortex IQ tracks across DHL InExpress 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.