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.
Before the first paste, four windows worth having open
Preparation for a first order is small and specific. You need the row you intend to use, the seller listing itself, a place to keep numbers, and one question written out in advance. That is the whole kit, and the fourth item is the one people skip.
The written question matters because the first order always produces exactly one thing you do not understand, and the difference between a good and a bad first order is usually whether that thing was asked about before the parcel was built or after it arrived. Write the question down while you are calm.
The place to keep numbers should be plain text and should record four values per item: what the listing claims, what the warehouse measures, what the quote says, and what the parcel finally weighs. Four numbers, one line each, and you have a dispute file without ever deciding to build one.
- Condition: you have the row and the listing open side by side. Pass standard: the model name in the row and on the page agree word for word. Re-check: reload the page without a stored session.
- Condition: you have written your one question down. Pass standard: it can be answered with a number or a yes. Re-check: read it aloud and delete every adjective.
- Condition: you have a place to keep four numbers per item. Pass standard: claimed, measured, quoted, final. Re-check: after the parcel lands, fill in the fourth number.
- Condition: you know which stage you are in. Pass standard: seller, warehouse, line or border. Re-check: name the stage whenever you feel impatient.
Paste, row, and the first hour after both
The paste is the easy part: the link goes into the field, the platform resolves it into a line you can configure, and the line becomes an order with a status attached. What matters is that the resolution is a reading, not a purchase, and it should be checked before anything else happens.
In the first hour, two things are worth confirming. The variant the platform resolved should match the variant you intended, because stores list several items under one link and the default is not always the one you were reading about. The size or finish field should be the one you chose rather than the one the page defaulted to.
This is also the hour to send the question you wrote during preparation. Questions sent before the warehouse receives anything are cheap; the same question after the parcel is built costs a rebuild, and a rebuild costs weight.
| # | Window | What to confirm | Evidence that closes it |
|---|---|---|---|
| 01 | 0 to 10 | The link resolved to the item you were reading | Model name and variant match the row you started from |
| 02 | 10 to 20 | The variant and size fields hold your choice | The order line repeats the size you selected, not a default |
| 03 | 20 to 40 | Your prepared question reached the warehouse | A request reference, not a read receipt |
| 04 | 40 to 60 | The four numbers you will track are written down | One line per item with claimed and measured columns ready |
| ∑ | Nothing in this hour is urgent. Everything in this hour is cheaper than the same correction made after the parcel is built. |
Windows are guidance for a first order and assume the store has the item in hand; a store that has to restock pushes everything below it back.
Receipt day: what the warehouse line settles
A warehouse line settles two questions and leaves two open. It settles that the item arrived and that somebody weighed it. It leaves open whether the item is correct and whether the packing is right, and those two questions are answered by photographs and by a measurement, not by the arrival line itself.
Read the receipt for the number that is new to you rather than for the status word. The status tells you that a process moved; the weight tells you something about the parcel that no status can. If the weight is far from the listing claim, that is the moment to ask, not after the parcel is quoted.
The receipt is also where the packing request either appears or does not. If your note about the retail box is not reflected in the weight, the request may never have been passed on, and a second message now is still cheaper than a rebuild later.
Line choice: one parcel, three parcels, or a wait
Line choice is the first decision with a real cost attached, and it is usually framed wrongly. The question is not which line is cheapest but how many shipments your order needs, because shipment count is what multiplies handling and re-opens a border assessment on each parcel.
The ladder this desk publishes prices three shapes of the same order: one merged build that waits for the slowest seller, a split into two so nothing waits on a single store, and a per-store build on an express line. Each shape has a different lever, and knowing which lever you are pulling is most of the decision.
For a first order the honest advice is to keep the shipment count low and the expectations wide. A first order is a measurement exercise as much as a purchase, and a split order doubles the number of things you are learning from at the same time.
- Condition: every store in the order has dispatched. Pass standard: each line has a store tracking number. Re-check: count the lines against the stores you actually used.
- Condition: you know how many shipments the chosen shape produces. Pass standard: the number is written down before the quote arrives. Re-check: compare it against the handling lines on the quote sheet.
- Condition: the slowest seller is acceptable to you. Pass standard: you would still be relaxed if that store took its stated maximum. Re-check: look at the store dispatch estimate rather than the platform estimate.
Quote day: reading the per-kilo sheet from the bottom up
A per-kilo quote is easier to read backwards. Start at the bottom with the chargeable weight, then read the per-kilo rate that was applied, then the handling line, then the optional lines. Reading forwards invites you to agree with a total before you have seen the number that produced it.
The chargeable weight is the greater of what the parcel weighs and what its volume implies at the line divisor. That single sentence explains most surprises, and it is why a request to remove a box can change a quote while a request to compress soft goods usually cannot.
Once you have the bottom line in view, the rest of the sheet becomes a short list of things that can be changed. You can change the parcel count, the packed volume, the line, or the declared contents. You cannot change the divisor by wanting to, and the sheet should tell you which one was used.
| # | Line | What it is | What moves it |
|---|---|---|---|
| 01 | Chargeable weight | The greater of measured mass and volume at the line divisor | Packed volume, and the divisor the line applies |
| 02 | Linehaul | Chargeable weight multiplied by the per-kilo rate | The rung or line you picked, and the weight above it |
| 03 | Handling | A per-shipment fee, charged once per parcel built | Shipment count, which follows from parcel count and rung |
| 04 | Border lines | Duty and tax assessed on the landed value | Destination band and whether postage is inside the value |
| 05 | Optional lines | Requests such as added protection or a special build | Whether you asked, and whether the line offers it |
| ∑ | Read the sheet from the chargeable weight upward. The total is a consequence, never a starting point. |
Line names differ between desks and lines; the five jobs above do not.
Packing requests and the number they move
Packing requests divide cleanly into those that change a number and those that change a feeling. On this desk the split was measured: dropping the retail box on nine footwear parcels changed the chargeable figure on seven of them, while a vacuum bag on five soft-goods parcels changed it on none.
That result is not a rule about boxes and bags in general. It is a statement about what those two requests did to the chargeable figure on fourteen parcels, and the reason to publish it is to give you a prior. A request that shrinks rigid volume moves a quote. A request that squeezes compressible volume often moves nothing, because the volume was never the constraint.
So when you write a packing request, write the number you expect it to move. If you cannot name one, the request is a preference and should be sent as one, without the expectation attached.
The finishing check: six conditions before you call it done
An order is finished when six conditions hold, and none of them is a feeling. The first is that every line you paid for has been received or refunded. The second is that the final weight of the parcel matches the weight the quote was built on, within the tolerance you wrote down. The third is that the declared contents match what the parcel actually held.
The fourth is that the border treatment was what you planned for, or that you know why it differed. The fifth is that your four numbers per item are filled in, including the final weight. The sixth is that the one question you wrote before the order was answered in writing, not in a status word.
Anything that fails a condition is not a disaster; it is a row for your own table. The point of a first order is to finish with a file you can read next time, and a file is built from numbers rather than from impressions.
- Line condition: every item received or refunded, with a reference for each. Pass standard: no line is in an unexplained state. Re-check: walk the list against the order, one line at a time.
- Weight condition: final scale weight against quoted weight. Pass standard: inside the tolerance you set before the quote. Re-check: compare the two numbers on the same slip.
- Declaration condition: declared contents against contents. Pass standard: descriptions match in plain words. Re-check: read your own declaration as a border officer would.
- Border condition: planned treatment against actual treatment. Pass standard: you can explain any difference in one sentence. Re-check: keep the notice, not just the total.
- Record condition: four numbers per item, all filled. Pass standard: claimed, measured, quoted, final. Re-check: open your notes and count the blanks.
- Answer condition: your written question has a written answer. Pass standard: the answer contains a number or a yes. Re-check: if it does not, ask once more with the same wording.
Handover: what this walkthrough leaves in your hands
What you keep after a first order is not the parcel. It is a file with four numbers per item, one answered question, and a note about which stage produced the surprise. That file is the only thing that makes the second order cheaper, and it costs nothing to keep.
The second order then reads differently, because you are no longer learning what the stages are. You are comparing two sets of numbers, and comparisons are the point at which a table stops being somebody else document and becomes your own.
What this note comes down to
- 01Prepare four things before the first paste: the row, the listing, a place for four numbers per item, and one written question that can be answered with a number.
- 02Check the resolved variant and size in the first hour, and send your question while the parcel is still unbuilt, because rebuilds cost weight.
- 03Read a per-kilo quote from the chargeable weight upward rather than from the total downward.
- 04On this desk, dropping the retail box moved the chargeable figure on seven of nine footwear parcels, while a vacuum bag moved none of five soft-goods parcels.
- 05Finish with six conditions met and a file of numbers, not with a feeling that the order went well.
The data point behind this note
Own parcel test, KB-2026-04: fourteen parcels were re-weighed after a packing request. Removing the retail box changed the chargeable figure on 7 of 9 footwear parcels; a vacuum bag changed it on 0 of 5 soft-goods parcels.
KB-2026-04· 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 | 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. | 1635 |
Related entries and gauges
- How do you open a link from the table without losing your place?
- What happens in the first hour after you paste a link?
- Applicability protocol
Work out which entries apply to your order right now.