The Van Is Not the Destination: Decoding the Depot Diary Behind UK Parcel Tracking

At some point this week, a parcel you ordered will enter the UK carrier dimension. The tracking page will say something like “In transit”. It will keep saying it. The page is not lying. It is simply reporting the carrier’s internal diary to a customer who asked a different question: will it arrive tomorrow, and should I stay in?

Royal Mail, Evri, DPD and their peers are good at moving boxes. They are less good at telling you what their own scans mean. The status feed is a receipt for a handoff between machines, vans and depots. You want a prediction. They give you a receipt.

The status is a receipt, not a forecast

Most tracking labels map to internal checkpoints: accepted, sorted, trunked, received at depot, routed, loaded, delivered. Those words are useful if you run the depot. They are close to useless if you are waiting for a birthday present and wondering whether to nip out for milk.

“In transit” can cover 400 miles, a weekend in a roll cage, or a subcontractor who has not scanned anything since Tuesday. “At local depot” may mean it arrived at 2am and will not be touched until tomorrow afternoon. The customer cannot distinguish progress from storage. That is a signal problem: lots of updates, very little information.

A timestamp does not fix it. “Updated 14:32” tells you when the carrier’s system blinked, not when the van will blink at your door. The page is optimised for the carrier’s paperwork, not your decision.

Why the vagueness survives

This is not a conspiracy. Legacy systems, batch uploads, subcontractor networks and liability rules all push in the same direction. Carriers avoid promising windows because missed promises cost money and trust. Statuses are designed to answer “where is my parcel?” at call-centre volume, not “when will it arrive?” at human precision.

There is also a split incentive. The retailer owns the brand; the carrier owns the data. The tracking page becomes a compromise: enough to reassure, not enough to commit. DPD has shown that a narrow delivery window is possible in many cases. That proves the product can be better. It does not prove the rest of the market is in a hurry to ship it.

Refresh is not a feature

People refresh because the page withholds the only useful signal. A notification that says “we’ll deliver today” without a window is worse than silence: it turns your day into standby. A good tracking page should reduce checking, not reward it. If you check five times and learn nothing, the page has failed.

The same goes for app prompts and account walls bolted onto a simple delivery. Tracking should not require a login to answer a question the carrier already knows the answer to. Signal over noise applies here as much as anywhere else.

A four-event model that would fix most of it

Carriers do not need to expose every scan. They need to translate custody into decisions. Four customer events plus an exception path would do more than a hundred vague statuses:

1. We have it. Timestamp, coarse location, expected delivery date. No “in transit” fog.
2. It is moving. Surface this only if the expected date changes or a delay is likely. Otherwise keep quiet.
3. It is at your local depot. Confirm the delivery date and give a window confidence: “High, 14:00–16:00” or “Low, sometime Thursday”.
4. It is on the van. Give a two-hour window and a fallback: “If we can’t deliver, here is what happens next.”

Then the exception event: “We missed a scan”, “address issue”, “weather”. Include the reason, the revised promise and one action. No dead ends.

The page should lead with one sentence: “Arriving Thursday, 14:00–16:00. Last scan: local depot, 06:12.” If there has been no scan, say: “No news is normal until 10:00 tomorrow.” That is confidence, not clutter. Rho’s rule: if a status does not change what you do next, it is decoration.

What carriers and retailers should ship

Translate internal codes into customer states. Share the same event model between retailer and carrier so the tracking page does not contradict the confirmation email. Send push notifications only when the decision changes: date, window, exception. Let people opt into “tell me when it is two hours away” rather than “notify me about every scan”. Publish a simple schema so retailers do not have to scrape.

The technology is not the hard part. The incentives are. A carrier that says “we don’t know yet” is more trustworthy than one that says “in transit” for three days. In 2026, the UK parcel-tracking page should be a small, honest signal product: one promise, one window, one exception path. Everything else is depot diary. Useful to the depot. Noise to you.

The van is not the destination

The destination is knowing whether to stay in. Britain’s carriers have spent years optimising for their own handoffs and calling it customer service. That is not good enough anymore. Tell people what you know, when you know it, and when you do not know. Then let the van do the rest.