Six tracking states, and the two that mean movement
Three things this piece settles
- Only two of the six states we track correspond to a physical scan; the rest are record updates.
- QC posted looks like the biggest update and is the one where nothing has moved at all.
- Warehouse arrival reads as good news and is the moment the storage clock starts.
Which stop this touches
8 stops · open a stop to read its windows · “n open” = actions still available
- Stop 1: Pick the channel — 3 actions still open. A channel is a filtered view of one agent, not a shop. Learn what its row count proves and what it cannot.
- Stop 2: Hand the link over — 3 actions still open. A link carries an identity, not a product. Keep the identity intact and the order stays traceable.
- Stop 3: Pay for the item — 2 actions still open. Item payment and freight payment are two separate moments. Most closed doors close at the first one.
- Stop 4: The warehouse clock — 3 actions still open. Arrival starts a clock. Verify the window on your own account before you plan around it.
- Stop 5: QC photos — 3 actions still open. A photo set is evidence of coverage, not a verdict on quality. Ask for angles, not for opinions.
- Stop 6: Merge and pack — 3 actions still open. Merging trades a second freight charge for a bigger volumetric weight. Run both sides.
- Stop 7: Freight and customs — 2 actions still open. Freight is charged on chargeable weight. Customs is decided on declaration fields you fill in.
- Stop 8: Checking the parcel — 2 actions still open. Delivery starts the claim clock. Photograph the unopened parcel before you open it.
Six order states, side by side
Six states cover an order from the moment the item payment clears to the moment a carrier has the box, and only two of them are evidence that something physically moved. The table below is ours: it was assembled from the eight stops in this runbook rather than copied from any channel interface, so the wording on your own screen may differ while the underlying events do not. Each state carries four fields, which are what it means, whether it counts as movement, and what you should do while it is showing. Read the movement field first, because that is the one that decides whether waiting is reasonable.
Paid with the seller means the item payment has cleared and the order exists, and it is not movement in any sense, since nothing has been dispatched and nothing is on the road. What to do here is narrow, because this is the last state in which a cancel is still a withdrawal rather than a request, so any change of mind belongs at this point. Domestic leg means the seller has handed the parcel to a courier inside China, and this is the first of the two states that do represent movement. What to do is to stop watching the order and start watching the warehouse clock, since arrival is the event that closes the clean cancel.
Logged in at the warehouse means the parcel has been received and registered against your row, and this is the second movement state, which is also why it starts the storage clock. What to do is to fix the row in your own record, because the id, the measured weight and the arrival date are the three facts every later calculation uses. QC posted means a photo set now exists for the row, and despite being the loudest update on the screen it represents no movement at all, since the parcel is exactly where it was. What to do is to read the frames against the listing before the window closes, because approving them is what makes the photographs final.
Packed for export means the rows you merged have become one labelled parcel, and that state change is internal work rather than a journey. What to do is to check the declaration and the address now, because those are the fields that lock at this point and they cannot be corrected in transit. In transit and customs covers the whole international leg, and it counts as movement in the sense that a carrier holds the parcel, even though the label can sit unchanged for the longest stretch of the order. What to do is to keep the carrier reference next to the parcel total, because a query about a stalled shipment moves faster with both in hand.
How the six states were defined
The six states were defined by ownership rather than by label, which means a state belongs to whoever can still change the outcome at that moment. Paid with the seller and QC posted belong to the agent and the warehouse, domestic leg and in transit belong to carriers, and packed for export belongs to the packing bench. That definition is why the list has six entries rather than twelve, and why a channel that shows ten statuses is usually showing the same six with more words. The useful test for any status you meet is to ask who can still act, and if the answer is nobody then you are outside this table.
Our own logging fixed the shape of the sample these states are illustrated with, and it is worth being precise about what was logged. Eight pages of the source channel list were read row by row on 2026-10-06 and produced 192 rows ranked 1 to 192, with no gaps in the rank sequence and no repeated item id. That is a record of a listing page rather than of anybody’s order, so nothing in this article describes a real parcel or a real scan. The states themselves come from the stop sequence, which is the part of this site that is a procedure rather than a measurement.
Two fields in the table are ours and two are structural, and mixing them up is the main way this kind of table misleads. What a state means and whether it represents movement are structural, because they follow from who is holding the parcel at that moment. What to do is our judgement about which action still has an effect while the state is showing. A reader who disagrees with the action column can still use the movement column, since that one does not depend on our opinion.
The state list carries one deliberate omission, which is anything that only exists after delivery. Claims, disputes and returns all happen after the last movement state in this table and have their own sequence with their own windows. Putting them in the same column would suggest they can be reached from the six, when in fact the parcel has already left the system by then. The exception is a delivery scan that never arrives, where the missing state is itself the signal and the right move is to open a query rather than to keep waiting.
Notes that keep the table honest
A state label is a record maintained by a party with an interest in it, so the table describes who holds the parcel rather than what the parcel is doing at this second. Between two movement states there can be many days in which the record is accurate and the parcel is stationary, and nothing about the label tells you which of the two you are in. The practical consequence is that a state change is evidence of an event that already happened, not of progress that is continuing. The exception is a carrier scan, which is generated at a physical handover and is therefore the closest thing to a fact in the list.
We publish no normal duration for any state, because we have not measured one and a number invented here would be worse than no number at all. What can be said is which states are structurally short and which are structurally long: the two movement states are usually brief, and the internal states can be long because they wait for something other than a truck. If you need a duration to compare against, take it from your own previous orders and keep it in the same note as the ids. The absence of a published duration is a limit of this page and is recorded as one.
Order of appearance is not guaranteed, which surprises readers who treat the list as a pipeline. A multi-variant row can produce two domestic legs and two arrival records under a single id, and a merged parcel can skip the individual arrival line entirely if the rows went straight to packing. Our sample gives a sense of how often a row is really several: 26 of the 192 rows, 13.5 percent, declare between 2 and 40 styles in the title alone. The exception is a row that declares no styles at all, where the single-line reading is almost always correct.
Two of the six states can be edited by you and four cannot, and the table is arranged so the editable ones are obvious. Nothing you type changes whether a parcel has moved, but the declaration and the address are your fields and they lock while the parcel is still inside the warehouse. Trying to change a carrier state from your side is the most common wasted action in this sequence. The exception is a genuinely wrong record, where the correction comes from a message to the agent rather than from anything in the interface.
Two states that read backwards
QC posted is the first counterintuitive state, because it looks like the biggest update in the sequence and it is the one where nothing moves at all. The photographs are produced at the warehouse after arrival, so this state records work done inside a building rather than a parcel on its way anywhere. A reader who treats the photo set as a sign of progress then waits inside it, when the only thing the state actually changes is how much evidence is held. The correct reading is the opposite of the intuitive one: this is the state where a clock is running and the parcel is not.
Logged in at the warehouse is the second one, and it reads as good news while it is in fact the start of a deadline. Arrival feels like a milestone because the uncertain part of the order is over, and it is also the moment the storage clock in this runbook begins, running from day one through to day ninety. Nothing on the screen marks that shift, which is why the arrival date belongs in your own record rather than only in the interface. The exception is a row you merge and ship immediately, where the storage question never becomes real.
A third reading error is common enough to mention even though this heading promises two, and it concerns the in transit label being treated as a single state when it is at least three. The parcel leaves the warehouse, clears export, and is then handed between carriers and customs, and all of that shares one label. When the label stops changing, the useful question is which of the three a query should be aimed at. The exception is a query answered by the carrier reference alone, where the extra detail changes nothing.
Put the two backward states together and a rule falls out that is worth keeping: the states that look most informative are the ones where you have the most work to do, and the states that look quiet are the ones where something is actually happening. Acting on that rule means reading the photo set when it appears and writing the arrival date down when the row lands, rather than waiting for a notification that may never come. The exception is a state that never appears at all, which is a different problem with a different answer and a different page.
The data point behind this piece
The eight logged pages hold ranks 1 through 192 with no gaps and no repeated item id, so a state seen on one row can be traced back to a single page and position.
Basis: Runbook desk inventory of the 2026-10-06 Joyagoo channel snapshot: 8 pages at 24 rows each, rank sequence checked for continuity and ids checked for duplicates.
Only two of the six tracked states correspond to a physical scan, and the other four can change while nothing moves between two points.
Basis: Derived from the eight stop definitions on this site, which separate warehouse-side record updates from carrier events; no platform status list was copied.
This piece answers searches about “how to track joyagoo order”. It is part of the tracking and exceptions cluster.
Where to go next
Links to Kakox are tracked so the destination can attribute the visit. Nothing on this site is sold by us.
Reviewed 2026-10-06 · Weekly review · next review weekly review