How do you trace a parcel whose tracking stopped moving?

Tracking silence on express air

Express air lanes scan at every handover, so silence is informative. On those lanes a gap of a week without a scan is genuinely abnormal and worth a trace request, because the parcel should have passed at least two scan points in that time.

The exception is the origin build. A parcel waiting for a consolidation cut-off can sit unbuilt for several days with no scan at all, and that period is counted inside the window rather than added to it. Check whether the parcel was ever handed to the line before you conclude anything from the quiet page.

Block updates on rail and sea lanes

Rail and sea freight update in blocks rather than scan by scan. A container is loaded, moved and discharged at points where somebody scans a manifest, and between those points nothing happens on the tracking page for a fortnight. A two-week silence on a sea lane is the normal shape of the lane, not evidence of a problem.

On those modes the useful question is not where the parcel is but whether the block it belongs to has moved. Ask the carrier which block or vessel the parcel is assigned to, and whether that block has already been discharged, because that answer tells you more than any scan date.

Milestone gaps worth chasing

Every journey has four milestones that matter: the origin build, the gateway arrival, the clearance start, and the final delivery scan. A stall between origin and gateway is usually a consolidation issue. A stall at the gateway is usually a clearance issue, and a stall after clearance is usually a last-mile issue with the local delivery partner.

Naming the milestone in your message gets a faster answer than describing the delay, because it routes the question to the team that can actually see the record. A message that says the parcel has been at the gateway for nine days is answered by a different desk from one that says the tracking looks stuck.

1. Origin build: has the parcel been handed to the line at all.
2. Gateway arrival: which flight, vessel or block it was assigned to.
3. Clearance start: whether a document request is outstanding.
4. Final delivery: which local partner holds it and under what reference.

Carrier-side tracing requests

A trace is an instruction to search, and it produces a written answer. Ask for it in the platform thread so that the request and the reply sit in the same record, and include the tracking number, the last scan with its date, the contents and the declared value. Without the last scan and its date the request is processed as a status enquiry and answered with what you already have.

Expect the first reply to restate the last scan. The second message is the one that matters, and it should ask a specific question: was the parcel scanned at the destination gateway, and if not, where was it last physically seen. That phrasing asks for a search rather than a restatement.

Sample counts behind a quiet window

How much a quiet page tells you depends on the lane. The desk counts reported arrivals per lane and prints the count beside every window, because a window with two hundred arrivals behind it and a window with twenty-nine are different strengths of evidence. The thin lanes are the ones where a stall is hardest to read and where widening your own expectation is the honest move.

On the thin lanes a late arrival is common enough that a trace is worth opening early rather than late, simply because there is less history to tell you whether the silence is ordinary. On the well-reported lanes the window is a better guide, and a parcel inside it usually needs patience rather than paperwork.

When a trace becomes a claim

A trace looks for the parcel. A claim declares it lost or damaged and starts a money process, and once a claim is open the carrier usually stops tracing. That is why the sequence matters: trace first, claim second, and only after the trace has come back without an answer or the lane window has closed outright.

Filing early is not free. A claim filed while the parcel is still moving is normally declined and closed, and the closed file makes a second filing harder because the first one recorded the parcel as found-in-transit. Wait for the empty trace, then file once with everything attached.

1. Trace: open on an express lane after 7 days without a scan.
2. Trace: open on an economy lane after 14 days without a scan.
3. Claim: file 30 days from the last recorded scan.
4. Insurance notification: 14 days from the outer edge of the lane window.

Deadlines that decide the outcome

Where the numbers in this entry come from

Origin: KB-2026-06 window counts — thirteen destination-and-mode lanes each carry the number of reported arrivals that produced the window, from 214 reports on the United States air economy lane down to 29 on New Zealand. The count is printed beside the window rather than behind it.

◇KB-2026-11· 2026-09-30 See the batch ledger · Challenge a figure

Entries filed next to this one

• How often does tracking update on each transport mode?

  Update rhythm follows the mode, not the parcel. Express air reports step by step, air economy reports at a few hubs, and rail and sea report in blocks at handovers, where several days of silence is ordinary.

• How do you file a missing-item claim that gets answered?

  A missing-item claim is decided on the receipt, the parcel record and the timeline, so file inside the short window with those three attached. State one item, one order number and one outcome. Ask the warehouse for a recount before you accuse anybody, because miscounted parcels are common.

• What happens when QC rejects an item?

  A rejection means the warehouse will not store or ship the item as received, so the order pauses inside the handling window. You can ask for a re-check, a return to the seller, an exchange, or a refund through the platform, and the window — not the rejection itself — decides what stays available.

Gauges this entry points at

• Line picker

  Rank the lanes that exist for your destination against two weights you set.