Your order carries two reference numbers and only one is live
A Kakobuy order produces at least two tracking references: the domestic one created when the seller ships the item inside China, and the international one created when you pay freight out of the warehouse. They belong to different systems, use different formats, and are updated by different companies. Refreshing the domestic number on day 9 tells you nothing, because that reference stopped being fed data on the day the parcel was signed into the warehouse.
This is the single most common reason a tracking page looks frozen. In a normal order the domestic leg runs roughly three to seven days inside China, then the number simply ends. If you do not know which number sits on your clipboard, you cannot tell a dead reference from a stalled parcel. Open the parcel record, not the item page, and check whether the number you are refreshing is the one printed on the international label.
- Domestic number: created at payment, ends when the warehouse signs the item in.
- International number: created after freight is paid, live until delivery.
- Warehouse intake record: dates the arrival, and is the only proof the item physically landed.
- Parcel detail page: shows the current number, and is the page worth refreshing.
If the numbers disagree, the parcel record wins. The [warehouse intake stage](/steps/warehouse-in/) is the handoff point, and everything before it belongs to the domestic system.
Four layers report on the same box, and each one goes quiet at a known moment
Once the parcel leaves the warehouse, one box is described by up to four separate reporting layers. Each layer answers a different question, and each one goes silent on a schedule you can predict without knowing any specific company.
| Layer | What it records | When it goes quiet |
|---|---|---|
| Warehouse intake | Arrival scan, weight, storage start | The moment the parcel is packed out |
| Export processing | Departure scan and flight or vessel booking | When the export record is closed |
| Linehaul | Transit events between hubs | For days at a time, then in bursts |
| Destination carrier | Local arrival, sortation, delivery attempt | After delivery, or after a failed attempt |
The layers do not hand over in a tidy sequence. Linehaul updates arrive in clusters, often three to five events posted within the same hour after a five day gap. A delivery attempt can post before the arrival scan, because the local carrier writes its own record first and the shared record catches up later.
Two consequences follow. First, a blank day is not a signal. Second, the last event you can see may belong to a layer that has already finished its job. When the destination carrier takes over, the earlier layers freeze at their last state forever.
Read the gap from the evidence side and the number stops lying
Treat every scan line as one uploaded record, then ask how much of the journey the uploaded records now cover. In a normal parcel the visible records cover four checkpoints: intake, export, destination arrival, and delivery. A line showing intake plus export has covered 50 percent of the journey and is waiting on a boundary, not on a human.
| Interval you can see | What it usually means | What to do with it |
|---|---|---|
| Intake to export | Packing and export paperwork still running | Nothing, unless it passes the trace day |
| Export to destination arrival | Linehaul leg or a scan gap at a boundary | Ask for a last-scan note only |
| Destination arrival to sortation | Local carrier has not written its record yet | Wait one more posting cycle |
| Sortation to delivery attempt | Out for delivery, or a failed attempt exists | Check the parcel record for an attempt note |
When two layers disagree about the last event, trust the layer with the later timestamp and stop comparing calendars. A parcel that looks two days stale at one layer may have been updated three times at another, because each system writes to its own clock and its own timezone.
If the destination carrier cannot deliver, the route changes shape
A failed delivery attempt is the one event that legitimately changes the shape of the journey. After the export record closes, an undeliverable parcel is returned to the address that booked the freight rather than to the original seller, so the return leg runs under a new status line and a new clock. The original transit estimate no longer describes it.
- Check the parcel record for an attempt note before assuming the line is broken.
- A returned parcel usually re-enters storage, so the storage clock restarts there.
- Re-shipping after a return is a new freight booking with a new tracking number.
- Keep the failed-attempt note; it dates the moment the first route ended.
Two facts make this stage calmer. First, nothing you can do in the tracking app changes the return. Second, the return address is decided when the label is booked, so the destination cannot be edited afterwards at any layer.
Request the last-scan timestamp, the scan location, and the booking party name in one written reply. Those three lines are what any later claim is checked against.
Five ways a line freezes while the parcel is still moving
A frozen line has one of five causes, and they need different responses. Separating them takes about two minutes and saves a week of guessing.
- Scan gap: the parcel moved between two hubs and no intermediate scan was written. Typical display gap: four to eight days.
- Linehaul hold: a consolidation leg waits for its scheduled departure. Display gap: seven to ten days, nothing actually wrong.
- Customs review: the parcel is held for assessment. The line usually shows only the last transport event plus a status note.
- Batch reference: a single number covers several parcels moving together, so individual scans are thin.
- Reissued number: the label was replaced after repacking, and the old number is no longer fed data.
The difference between the first two and the last one matters. A scan gap resolves on its own, usually at the next country boundary. A reissued number never resolves, because nobody is writing to that reference any more. If a line has been frozen for more than ten days and no status note appeared, check the parcel detail for a second number before you contact anyone.
This page gives no carrier-specific transit times and no Kakobuy service-level figures. Any day range published by a carrier or a platform is theirs to publish, and we do not restate numbers we cannot check on the date of writing.
What to do on day 3, day 7 and day 10 of a silent line
Escalating early is as wasteful as escalating never. The sequence below assumes a normal international parcel with a live number and no customs note.
| Day | Action | What counts as progress |
|---|---|---|
| Day 3 | Confirm which number is live and compare it with the label on the parcel record | The two numbers match |
| Day 7 | Request a written status note from the agent | A dated last-scan time and location, in writing |
| Day 10 | Ask for a trace to be opened with the booking party | A trace reference you can quote later |
| Day 14 | Ask what the claim window is and when it closes | A stated deadline, not a reassurance |
A written note is the only useful output of a support contact. Ask for the tracking number, the exact timestamp and place of the last recorded event, and the name of the booking party. If the reply repeats what your own tracking page already shows, you have learned nothing and should ask again more narrowly.
The [customs clearance stage](/steps/customs-clear/) changes this ladder. A parcel held for assessment has no moving line by design, and chasing the carrier adds noise. Log the dates in [the transit log tool](/rig/transit-log/) so the gap is visible as a number rather than a feeling.
If the line never recovers, switch from tracking to evidence
Tracking tells you where a parcel should be according to the company that booked the freight. It stops being useful the moment you need to prove that something went wrong, because a screenshot proves nothing about who owns the shipment. Evidence does: the intake record, the freight invoice, the label, and the written last-scan note.
Order matters when the number changed. Repacking a parcel can create a second label, and the old number then freezes for good. Look at the parcel record first, because the new number is often already listed there while people keep refreshing a dead one for another fortnight.
- Step 1: check the parcel record for a second or replacement number.
- Step 2: if the number is unchanged, ask for the last-scan timestamp in writing.
- Step 3: if the last scan is older than the trace you requested, ask for the trace reference.
- Step 4: keep every reply in one folder; a claim is judged on dated documents, not on a story.
For a first-time buyer the practical routine is small: check every two days rather than every hour, keep one dated note per scan, and treat ten silent days as the trigger for the evidence step. The wider patterns behind these stalls are collected under [transit and tracking](/table/transit/).
Flow dependency: a domestic tracking number is a store-to-warehouse reference, so it stops reporting the moment warehouse intake closes and never resumes; buyers who keep refreshing it after the international label is booked are reading a dead reference, not a stalled parcel. (stated basis: Flow dependency)
This note explains the mechanics; the list is where the items are.