Every status code, explained without jargon
Status words differ from desk to desk, but the seven phases behind them do not, and learning the phases is what makes any status line readable.
Phase codes: the seven states an order passes through
Every order sits in exactly one of seven phases, whatever vocabulary the desk in front of you prefers. The phases are: resolved, placed, purchased, dispatched, received, built, and handed over. Naming the phase is the skill. Memorising somebody labels is not, because labels change when a desk redesigns a page and phases do not change at all.
Two rules make the seven worth learning. A phase describes where an order is, not how it is going, so a reassuring word in a late phase is still a late order. And a phase has to be entered by an event somebody could point at, which means every phase you claim should come with a thing you could photograph, print or forward.
The phase you are in decides which question is worth asking. Asking about packing while an order is still in the resolved phase wastes a message, and asking about dispatch after the parcel is built wastes a rebuild. Most of the frustration in a first order is a phase question asked at the wrong phase.
- Resolved: the link has been turned into a configurable line and nothing is committed. Evidence: the line exists with a variant selected. It does not mean the seller has the item.
- Placed: your instruction and payment are recorded. Evidence: an order reference with a timestamp. It does not mean the seller has accepted anything.
- Purchased: the seller has taken the order. Evidence: a store-side order number. It does not mean the item is in stock today.
- Dispatched: the store has sent something. Evidence: a domestic tracking number beginning at the store. It does not mean the warehouse has it yet.
- Received: the warehouse has the item in hand. Evidence: a receipt line with a weight. It does not mean the item is correct.
- Built: the parcel has been assembled and weighed. Evidence: a packed weight and a packing list. It does not mean it has left the building.
- Handed over: the line has the parcel. Evidence: a handover scan. It does not mean the parcel will clear a border without a question.
Warehouse codes: received, checked, stored and the words between them
Warehouse vocabulary is where most confusion starts, because one word covers two different acts. Receiving means a parcel was opened, counted and weighed. Checking means somebody looked at the item against a request. An item can be received for days before anybody checks it, and a status that says only received is silent about quality.
The stored state is equally quiet. It means the item is on a shelf with an identifier, and it says nothing about how long the shelf will hold it. Storage language often carries a clock in the fine print rather than in the status, so the number you need is a window rather than a word.
When a warehouse status appears to move backwards, the usual cause is a correction rather than a reversal: a weight re-taken, an identifier re-scanned, a line split because two items arrived in one parcel. A backwards step with a new number attached is almost always better news than a forwards step with none.
- Received but not checked: send the request you were going to send anyway, and reference the receipt line so the reply has something to hang on.
- Checked and rejected: ask for the reason in one sentence plus one photograph, because a rejection without a stated reason cannot be appealed.
- Stored past the stated window: ask what happens at the end of the window in writing, and keep the answer rather than the memory of it.
- Corrected weight: compare the new figure against the listing claim before anything else, since a re-weigh is often the first honest number you get.
Money codes: paid, pending, refunded and the state that means neither
Paid is the least interesting and the most reliable of the money words: it records that a payment was taken. Pending is the one that gets misread, because it covers two unrelated situations. A pending line can mean the instruction has not yet been matched to a payment, or it can mean a payment was taken and is waiting on the seller.
The way to separate them is to look for a timestamp and a reference. Pending with a timestamp means something is in flight. Pending without one usually means the screen has not caught up, and the cure is a reload rather than a message.
Refunded is the last of the three and the most hopeful-sounding. It records that a refund was issued on the desk side. Whether the money is back with you depends on the payment route, which is a different system with a different clock, and it is worth asking for the reference that proves the issue rather than assuming a date.
Parcel codes: built, handed over, in transit, released
Parcel vocabulary describes a physical object rather than an administrative one, which makes it easier to check and harder to hurry. Built is a measurement event, handed over is a scan, in transit is a direction, and released is a border outcome. Only one of those four can be verified by you at home, which is the built step.
The in-transit word deserves special handling because it covers the longest stretch of the journey and the least information. A parcel can be in transit for three weeks with two scans, and neither scan is late in any sense a desk can act on. What you can act on is the window the line publishes with a sample behind it.
Released is the most over-read word in the set. It means a border process finished and the parcel moved on. It does not mean nothing was charged; a notice can follow the parcel and arrive after it does, which is a separate line on a separate clock.
| # | Word | What it asserts | How you re-check it | What it does not say |
|---|---|---|---|---|
| 01 | Built | A parcel exists with a weight and a packing list | Read the packed weight against the listing claim | Whether the contents match the request |
| 02 | Handed over | The line has taken possession | Find the first scan under the line reference | When the parcel will be built into a load |
| 03 | In transit | The parcel is moving somewhere | Compare elapsed days against the published window | Where it is today, in any useful sense |
| 04 | Released | A border process closed | Keep the notice if one arrives later | That nothing was assessed against you |
| ∑ | Parcel words describe movement. They never describe contents, condition or cost. |
Desks rename these freely; the four jobs they perform stay the same.
Codes people misuse most, and the cost of each misuse
The most common misuse is reading a phase word as a promise about time. In transit is not an estimate, received is not a schedule, and stored is not a countdown unless a window is printed beside it. The cost is a message sent too late to change anything, and a rebuild request that arrives after the parcel has been sealed.
The second misuse is assuming two words with the same name mean the same thing across desks. Order numbers, receipts and even packing lists are generated by different systems and carry different guarantees. Reading a familiar word as though it came from the familiar system is how people end up comparing a timestamp to a date and concluding something has gone wrong.
The third misuse is treating a correction as a problem. A weight that changes after a re-weigh is the system working. The problem would be a weight that never changes while the contents do.
- Promise misuse: a direction word read as a date. Cost: a late request, which is a request that cannot be acted on.
- Vocabulary misuse: a familiar word assumed to carry its familiar guarantee. Cost: a false alarm and a wasted message.
- Correction misuse: a revised number read as instability. Cost: a rebuild requested for no reason, which is weight you pay for.
- Silence misuse: a quiet status read as consent. Cost: a packing decision made by default rather than by you.
A one-line index from code to action
An index turns reading into doing, and it can be short. For each word, decide the single action it licenses. If a word licenses no action, it belongs in a watch list rather than in your inbox.
Keep the index beside your order notes rather than in your head. The value of writing it down is that it settles, in advance, which statuses deserve a message and which deserve patience, and it removes the daily re-decision that makes waiting feel longer than it is.
- Resolved: choose the variant and the size, then stop reading and start checking the listing.
- Placed: nothing to do; the next real event is a store order number.
- Purchased: nothing to do; the next real event is a store tracking number.
- Dispatched: watch the arrival at the warehouse, not the flight.
- Received: read the weight, then send requests while the parcel is still open.
- Built: read the chargeable weight against the quote before the parcel leaves.
- Handed over: switch from day counting to window comparison, and stop checking twice a day.
Reading two codes at once: the combinations that carry meaning
Single words mislead; pairs inform. Received without a weight means somebody has the item but has not measured it. Built without a packing note means the parcel was assembled before your request was read. Handed over without a scan means the parcel left on a promise rather than a record.
The most expensive pair is released with a later notice, because it means a border cost was assessed after the parcel moved. That combination is the one worth planning for rather than arguing about, since the assessment is not a mistake by the line.
A third pattern is a pair that never appears: in transit with no subsequent word for longer than the window you wrote down. That is the point at which a trace request is worth sending, and the useful version of that request contains three things: the line reference, the last scan, and the window you were given with its sample count.
- Received plus no weight: ask for a scale photograph rather than a status.
- Built plus no packing note: ask which requests were applied before the seal.
- Handed over plus no scan: ask for the load reference, not for reassurance.
- Released plus a later notice: keep the notice and read it as a separate line item.
What this note comes down to
- 01Seven phases cover every order: resolved, placed, purchased, dispatched, received, built, handed over. Labels change between desks, phases do not.
- 02A phase has to be entered by an event you could point at, so every status you rely on should come with a reference, a weight or a scan.
- 03Money words split into paid, pending and refunded, and pending without a timestamp is usually a stale screen rather than a stalled order.
- 04On this desk, any window published without an arrival count is treated the same way as a status word with nothing behind it: marked as indicative.
The data point behind this note
Own window count, KB-2026-06: each of the thirteen published lanes carries a re-read date and an arrival-report count, running from 29 to 214 reports; the four lanes below 45 reports are labelled indicative rather than dependable. A status without a count gets the same label here.
KB-2026-11· 2026-09-30 Batch ledger · Challenge a figure
Notes in the same cluster
| # | Note | What it argues | Words |
|---|---|---|---|
| 01 | What the table actually is, and what it was never meant to do | A CNFans spreadsheet is a hand-kept list of store links with working notes attached, and the useful question is never what it is but what it can be asked to prove. | 1670 |
| 02 | Reading a row in ninety seconds | Ninety seconds is enough to read one table row properly, provided you spend them on four fields in a fixed order instead of on the whole line at once. | 1425 |
| 03 | A first order, walked through step by step | A first order moves through six checkpoints, and each checkpoint has one question, one piece of evidence and one thing you should write down before moving on. | 1695 |
Related entries and gauges
- What does each order status mean in plain words?
- What does a warehouse receipt tell you that the seller page does not?
- What happens in the first hour after you paste a link?
- Transit window bench
Reported arrival windows with the sample count attached.