The storage decision checklist: twelve checks before the clock runs out

Group 1 — what is already in the warehouse

Three of the twelve checks concern rows that have already landed, and they are the cheapest in the list because everything they need is printed on the item record. Run them in the order a warehouse works: the arrival date first, then what the camera recorded, then the one window that still allows the item to be sent back. A row that fails one of these three is not a waiting candidate, whatever the remaining nine checks say.

Check one asks for the arrival date rather than the payment date. It passes when the date in your note matches the log-in entry on the item record, because that entry is what starts the clock. It fails when the only date you hold is the payment confirmation, and the repair is to reconstruct the log-in date from the record and write it down beside the date you checked.

The second line on the same record is the photo set, and it passes only when the set covers the item rather than merely exists. Each of the four groups the QC checklist names — carton, cut, detail, markings — needs at least one frame you could measure. Where a group is missing, the repair is a request naming the angles, sent while the item is still in storage, because the set is final once the item moves to packing.

The return window is the third check, and the only one whose failure cannot be repaired. It passes when every row carries a date you read from the platform and that date still lies ahead. It fails when a row has already passed its window, and at that point the check is not a request but a reclassification: the row leaves the return column and joins the ship-or-dispose column, where a condition complaint has to argue against photographs that were already on record. That is why it sits third in the order and first in weight, since the other two failures cost a request and this one costs an option.

Group 2 — what is still in transit

The second group covers rows that have been paid for and have not arrived, and it exists because a wait is only defensible when the thing being waited for has a name and a date. These three checks convert an open order into either a schedule or a question mark. A question mark is allowed in your notes; it is not allowed inside a waiting decision.

The fourth check is a state on every open row, written with the date you last read it. It fails when the honest entry is unknown, which is a different problem from a row that has not moved and should be written as such rather than smoothed into on the way.

The variant is check five, and it asks whether what is in transit still matches the note you recorded when the link was handed over. It passes when the resolved name on the order carries the same bracket note and the same marketplace label. It fails before payment, where the repair is a correction to the order, and it fails after payment in a different way: the row has become a return candidate rather than a shipment.

The sixth check is a decision date. It passes when you can write the date on which you would ship without the missing item and that date falls inside the earliest expiry computed in Group 3. It fails when no such date can be defended, and the honest reading of that failure is that the missing item is not coming and the haul ships without it. The check is deliberately last in the group because it depends on numbers that have not been read yet, and running it first produces a date checked against nothing.

Group 3 — what the clock says

No number of free days appears in this article. The day count is a platform setting rather than a constant, and on 2026-10-06 we could not confirm one from any public page we were able to open, so this group checks something more useful than the figure itself: that the number in your note came from your own account, and that it carries the date you read it. Three checks, all of them bookkeeping.

The free-window figure comes seventh and it needs a source rather than a recollection. It passes when you can point at the place on your account where the platform states the number of free days for the parcel. It fails when the number in your head came from a forum, and the repair is to open the account and read it before any other check in this article runs, because every remaining date is measured against that figure.

Days remaining is the eighth check, and it has two halves: one per row, one for the haul. It passes when the row with the least time left is marked as the row that sets the pace. It fails when the newest row is the one being watched, since the newest row is almost never the one that expires first.

The ninth check asks which window closes first. It passes when you can say, for each row, whether the storage window, the return window or the photo window expires soonest. It fails when the storage figure is treated as the only deadline, because the other two are shorter and both are permanent. One mechanism belongs in the same note even though no check can repair it once it starts: past the free window, storage keeps accruing as a charge on the parcel and has to be settled before shipping, so the cost of waiting changes character at that point rather than simply growing.

Group 4 — what merging would change

Merging is where a checklist earns its keep, because the case for it looks obvious and is sometimes wrong. Combining items removes the repeated fixed part of a freight charge and produces one larger box whose volumetric weight is calculated from the outside. Those two effects pull in opposite directions, and only arithmetic can say which one wins for a particular haul.

Check ten asks for both sides computed with the same inputs. It passes when you hold three figures — each item shipped alone, the merged parcel, and the chargeable weight behind each — produced by one tool from one set of measurements. It fails when the merge goes ahead on intuition, and the repair is to compute the three figures before submission rather than to write a justification afterwards.

The item that sets the outer dimensions is check eleven. It passes when you can name that single item and say whether it can be repacked without risk. It fails when the repack question is left open, since repacking changes volume rather than mass and does nothing for a parcel that is already heavy for its size.

The last of the twelve asks whether the decisions that close at packing are already on the record. It passes when the composition, the repack request and any reinforcement are written down before the parcel is submitted for international shipping. It fails when anything is left for later, and the cost of that failure is structural: additions after submission form a second parcel with its own freight charge, and reinforcement asked for after packing cannot be added in transit, so a later damage claim rests on the packing as it was. The check closes last for the same reason it is hardest to reverse, because its window is on the warehouse side rather than on yours.

When the checklist says ship now

Twelve checks produce a decision rather than a score, and the rule that makes them usable fits in three lines. Ship now when a Group 1 or Group 3 check has failed in a way that cannot be repaired today, when the row with the least time left is inside the last third of its return window, or when the merge arithmetic shows the wait saving less than the storage it consumes. Any one of those is sufficient on its own; none of them needs the other eleven checks to agree first.

Two of the three conditions deserve a sentence of their own. A Group 1 failure that cannot be repaired means the row has lost an option, not that it is damaged: a photo window that has closed leaves a record rather than a remedy, and the shipment proceeds with the record attached. A merge that does not pay is not a reason to keep items apart indefinitely; it is a reason to ship the bulky item now and merge the rest, which the parcel builder still accepts while nothing has been submitted.

Write the reason beside the decision. Three words are enough — window, merge, defect — and the point is that the row gets a verdict carrying a date rather than a mood carrying a date. A haul assembled from twelve checks tends to be more uniform than one assembled from impression, and the notes are what make the second reading cheap.

When it says wait

The wait branch has stricter entry conditions than the ship branch, deliberately. Wait when three things hold at once: the missing parcel has a tracking state you read in the last few days, its arrival falls inside the earliest expiry computed in Group 3, and the merge arithmetic shows a saving that survives the rise in volumetric weight. Two out of three is not a wait. It is a decision that has been postponed, and the checklist exists to make that difference visible.

The condition people break is the third one. A merge that saves on the fixed part of a freight charge and loses more on volume gains nothing, which is why check ten asks for three figures rather than one. The second condition is the one people cannot break and try to anyway: an expiry date does not move because a parcel is late, and a row that waits past its return window has traded a repair option for a shipping decision it could have taken a week earlier.

Record the wait as a dated decision rather than as an absence of one. A line that reads waiting for the second parcel, decision on the date beside it, is checkable at the next reading; a line that reads waiting is not. When that date arrives, run the twelve checks again instead of resuming the old conclusion, because the only thing that changed in the interval is the clock, and the clock is the subject of Group 3.