The customer knows before you do
A customer rings to say their pallet was meant to be delivered today, and the tracking shows 'collected' and nothing since. You log into the network portal and see the same thing. It went out on last night's trunk; you have the manifest. But there is no hub scan, no outbound scan and no delivery depot scan.
Now you are ringing the hub, emailing the delivery depot and trying to reassure a customer at the same time. Half the time the pallet turns up, having been sorted without a scan. The other half, it has been sitting in the wrong bay.
Nobody is looking at the gaps
Tracking systems are built to show what did happen. They are not good at showing what should have happened and did not. A consignment with no hub scan looks exactly like one that is simply early in its journey unless someone checks it against the clock.
- The network portal is searched one consignment at a time, after someone asks.
- Scan compliance reports, where they exist, arrive after the fact.
- Your own system knows what went on the trunk but not what happened next.
- No one owns the job of checking every consignment each morning.
What missing scans cost
Every consignment with a gap becomes a phone call, often several. It also becomes a customer who thinks your depot has lost their goods. Some of those gaps are genuine: a pallet left on the hub floor or loaded onto the wrong trunk. Finding those a day earlier is the difference between a late delivery and a claim.
Scan compliance also feeds the network's view of your depot. You would rather see your own gaps than have them pointed out to you.
How we build the scan-gap monitor
- We take your trunk manifests as the starting list of consignments that left your depot, and inbound delivery lists for those coming to you.
- Tracking events are read from the network system wherever it offers an export, report or API, on a schedule through the night and early morning.
- Each consignment is checked against the scans expected by now for its service: hub in, hub out, delivery depot in.
- Anything missing an expected scan goes on a morning exceptions list, sorted by service and delivery date, with premium and timed consignments at the top.
- Staff record what they found and who they spoke to against the consignment, so the same one is not chased twice.
- A weekly view shows gaps by route and by stage, so you can raise a pattern with the hub rather than a single pallet.
| Gap | What it usually means | Who to ask first |
|---|---|---|
| No hub in scan | Not scanned off your trunk, or not on it | Your loaders, then the hub |
| Hub in, no hub out | Still at the hub or mis-sorted | The hub |
| Hub out, no depot in | On the wrong trunk or not unloaded | Delivery depot |
The monitor is only as good as the tracking data we can read, which is why we look at your network's access options first and tell you plainly what is possible.
How the morning changes
The office starts with a list instead of waiting for calls. The awkward ones get chased while there is still time to fix the delivery, and by the time a customer rings you can say what you already know and what you are doing about it.
Over a few weeks the pattern of gaps shows you which of your own loading habits cause them, which is the part you can fix.
Check your own depot against this
- Most tracking queries start with a customer call, not your own check.
- Staff search the network portal one consignment at a time.
- Consignments with no hub scan are found only when late.
- You cannot say which stage most gaps happen at.
- The network has raised your scan compliance with you.