Nine days without a scan: two checks before you write anything
Nine quiet days feels like a lost parcel and usually is not one. Before sending a message, do two checks that cost 5 minutes each. First, confirm the number you are refreshing belongs to the leg the parcel is on, because a consignment of 1.8 kg can carry two numbers and the first one stops reporting the moment the parcel changes carrier. Second, count the scans you have rather than the days: a number with four scans and nine quiet days is a different situation from a number with one scan.
| Where it stalled | Signal you can see | Who can answer | Move to make |
|---|---|---|---|
| Before the warehouse handover | One entry saying the label was created, and nothing physical | The warehouse, through the operator thread | Ask for the handover date and the receipt |
| On the export line | An export scan, then nothing for 4 to 6 days | The freight forwarder holding the consignment | Ask for the consignment reference and the booked departure date |
| In destination clearance | A held or awaiting-clearance status, unchanged | The destination customs authority, then the carrier | Read the authority notice and answer any document request inside its own stated deadline |
| After the last-mile handover | Arrived at destination facility, then silence | The destination carrier, who holds a different number | Ask for the second number in writing |
| After a delivered scan | Delivered, with no signature recorded | The carrier first, then the operator claim route | File the claim inside the window your terms state |
Those 5 rows cover almost every silence, and only 2 of them are answered by the operator you paid. That is the part people miss: from the moment the parcel leaves the warehouse, the operator is a messenger for a chain of carriers, and the messenger is rarely the fastest source.
Stuck between the warehouse and the aircraft
The first stall happens while the parcel is still inside the building. A label exists, the number resolves, and no physical scan exists because the box has not been handed to anybody. If freight was paid on day 8 and the only scan on day 11 still says the label was created, the parcel has not left. Ask one question with a date in it: on which day was this parcel handed to the carrier, and what is the receipt reference.
The second stall starts after the export scan. Consolidated freight moves under a master consignment, and the tracking number in your account frequently belongs to the collecting carrier rather than to the aircraft. That is why a parcel can sit for 5 days with a valid number and no update: the piece-level number has nothing to report until the consignment is broken down at the other end.
- Compare the last scan date with the date you paid freight; a gap over 4 days at this point is worth one message
- Ask for the consignment reference, not for a promise that the parcel is fine
- Log every scan with its date in one place; the [transit-log](/rig/transit-log/) rig is built for exactly that
- Keep the reply, because a 3-day gap explained in writing is evidence later if the gap becomes 3 weeks
A useful message asks for a date, a reference or a document. A message that asks whether the parcel is fine produces a sentence you cannot use anywhere.
In clearance, where the operator is the slowest source available
Customs is the one stage with a public text behind it. Duty thresholds, prohibited categories and the documents a clearance needs are set by the destination country, published by its customs authority, and changed on that authority’s schedule rather than on yours. The [customs](/table/customs/) page keeps the general shape of that process; the current numbers come from the authority itself, and no threshold is printed on this page because the figure that applied 12 months ago may not apply to your parcel.
The practical mistake at this stage is asking the operator to explain a hold. A customs notice goes to the consignee or the broker, states what it wants, and carries its own response deadline. Missing that deadline is the expensive error, not the hold itself, and 3 messages to an operator in 1 week will not move a document request that only you or your broker can answer.
One timeline puts the silence in proportion. On the stage list, clearance occupies roughly day 12 to day 25, which means a parcel with no scan on day 14 is 2 days into a window that can legitimately stay quiet for longer. Panic on day 14 and a claim on day 40 are different actions with different evidence requirements.
Document requests arrive by email or in the carrier portal, and the [customs-clear](/steps/customs-clear/) step lists the order in which they are usually answered, which is 1 document at a time. Reply through the channel the notice names, and copy the operator only so that the thread stays complete.
After the last handover, the number you are refreshing is dead
The fourth handover is the one that produces the angriest messages, and it is not a failure at all. When the international carrier passes the parcel to a domestic partner, the original tracking number stops updating permanently. It is not stuck; it has finished. A parcel can sit at this point for 6 days showing a destination-facility scan while a second number, held by the partner, shows it moving.
- Ask for the second tracking number in writing, with the partner carrier named
- Check the partner carrier’s own site directly; resellers of tracking data update later
- Expect the last mile to take 1 to 3 days after the partnership scan, longer over public holidays
- Keep both numbers in the same log entry so the handover date is visible
The 5th stall comes after a delivered scan with no signature. From that scan the claim window starts counting, and the window is stated in the operator’s own terms rather than on this page. Photograph the parcel before opening it if the outer box is damaged, keep the packaging for the stated holding period, and file inside the window rather than at the end of it.
A number that stops updating at a handover is finished, not lost. Ask for the successor number before you ask anyone to investigate anything.
What not to do while the number sits still
- Do not open a payment dispute on day 3 of a clearance window; the dispute route has its own evidence standard and its own deadline, published by the scheme and your bank
- Do not send three tickets in one week; one thread with dated messages reads as a record, three threads read as noise
- Do not accept a verbal assurance that the parcel is on the way; ask for a scan, a date or a reference instead
- Do not pay a second time for a replacement shipment before the first is formally written off
- Do not rely on a forum for the chargeback deadline; read the rules your payment route publishes
The [transit](/table/transit/) topic page groups the same silences by carrier type rather than by stage, which helps when you cannot tell which row of the table above you are in. One habit beats all of it: write the date, the scan text and the source into one line every time you look, so that on day 20 you are reading 6 lines instead of remembering 3 weeks.
If the silence passes the outer edge of the stage window and no reference exists, the escalation is a written request for a formal trace, sent once, naming the parcel number, the last scan date and the two references you already collected. A trace request with 3 facts attached is answered; a trace request without them is a queue position.
Flow dependency: a parcel changes hands four times after packing — warehouse handover, export line, destination clearance and the last-mile partner — and each carrier reports only the legs it operates, so a nine-day silence inside a clearance stage that runs to day 25 is a gap between two systems rather than evidence that the parcel is lost.
This note explains the mechanics; the list is where the items are.