The tracking page stops. The customer asks where their order is. The parcel is moving normally the whole time — under a number you have never seen.
When a parcel leaves the country it was posted in, it is often handed to a completely different carrier for the last leg. That carrier issues its own tracking number. The original number stops updating — not because anything went wrong, but because the first carrier's job is done and it has nothing left to report.
Nobody tells you the new number. Not the carrier's public tracking page, not the marketplace, not your store. The two halves of the journey exist in separate systems, and joining them is left to whoever notices.
Here is a real example from a parcel we followed end to end.
| Leg | Carrier | Tracking number |
|---|---|---|
| Origin (UK) | Evri | H07LSC0000020241 |
| Destination (Ireland) | An Post | TP306194170IE |
Two numbers, two carriers, one parcel. The Evri number stops at the border. The An Post number starts there. There is no public page anywhere that shows both, and the customer holding the first number sees a tracking history that simply ends.
We asked the aggregator. We put this specific pair to 17TRACK, whose whole business is joining carrier data together. Their answer was that Evri does not supply them with the mapping between the two numbers.
That is worth sitting with: if the company whose job is to connect tracking numbers cannot connect these, no tracking tool can. The information does not exist outside the carrier's own support desk.
The tell is not the silence. Plenty of parcels go quiet for a couple of days and then carry on. The tell is what the last event says.
A handover leaves a fingerprint. Look for wording along these lines as the final scan:
All three describe the parcel leaving the origin carrier's network. Once you see one of those as the last line, the parcel has almost certainly been passed on, and waiting for the old number to update is waiting for something that will not happen.
Compare that with a parcel whose last scan is an ordinary domestic hub event with no border wording anywhere in the history. That one has not been handed over. It is a different problem and wants a different response.
Do not open a "where is my parcel" enquiry. That puts you in a queue for an investigation nobody needs to run. Ask a narrower question instead, because it has a specific answer sitting in their system:
Consignment H07LSC0000020241 shows "Loaded to International Trailer" as its last event on [date], destination Ireland. Please confirm the partner carrier and the successor tracking number so I can follow the remaining leg. I am not asking you to investigate a delay.
Naming the handover event in your first message matters. It tells the agent you already know the parcel left their network, which skips the round of questions about whether it was collected.
The customer is looking at a dead tracking page and drawing the obvious conclusion. Say the thing that page cannot:
Your order has crossed into [country] and is now with [carrier], who handle the final delivery there. That means the original tracking number has stopped updating — it only covers the first half of the journey. I am getting the new number and will send it as soon as I have it. Nothing has gone wrong.
It is tempting to assume this is a gap somebody will close. Here is why it persists.
The order in your store was fulfilled with one tracking number, and that is the number your customer sees. Marketplaces behave the same way — eBay does not link the segments either. The second carrier has no idea which order the parcel belongs to; it has a consignment, a barcode and an address. Neither system is wrong. They were never connected in the first place.
So the join has to be made by a person, once, per parcel — and only if somebody notices the tracking has stopped in the first place.
What we cannot tell you. We do not know how many carriers do this, or for which routes, or how often. We have watched it happen on a specific UK-to-Ireland lane and confirmed the cause with the aggregator. Treat the pattern as real and the scope as unknown — if a parcel of yours goes quiet on a different route, check the last event before assuming it is the same thing.
Read the last event, not the gap. A parcel that has been silent four days after "Loaded to International Trailer" needs a phone call and a new number. A parcel silent four days after a routine domestic scan needs something else entirely. The silence looks identical; the last line tells you which one you have.
It watches every tracked parcel your Shopify store ships and surfaces only the ones that have gone quiet longer than their route should allow, been refused, held at customs, or started heading back to you — with the reason and a customer message ready to send.
It doesn't message anyone automatically. It tells you which parcels need you, so you're not opening tracking pages one by one.
See it on the Shopify App StoreWe'd like to measure how people find this site. We use Google's advertising cookies to see which searches and ads bring merchants here. Nothing runs until you choose, and declining changes nothing about how the site works. Read the privacy policy.