The storage clock: when free days turn into a fee

Day 1: the row that starts the clock

Day one is the arrival date, and it is the only date in this sequence that can be verified from two directions at once. The warehouse registers the parcel against your row, and the seller side shows a dispatch that has already happened, so the two records should agree on the day even when they disagree about the hour. Everything the storage clock later charges for is counted from this date, which is why it belongs in your own notes rather than only in the interface. Mark it on the day it appears, because reconstructing it afterwards means matching two logs by eye.

Arrival itself creates three facts you will use at every later stop, and none of them is visible until you go and look. The first is the row id, which is how the warehouse refers to the parcel in every message after that. The second is the measured weight, which may not match what the seller declared on the listing. The third is the arrival date, which is the start of the clock. Record all three on one line and the rest of this sequence turns into arithmetic.

Two things about day one are counterintuitive enough to state plainly. Storage is counted on the space a parcel takes, so a light but bulky parcel can consume more of the free period than a heavy compact one, and our sample suggests how often that happens: outerwear at 20 rows and shoes at 10 rows make up 30 of the 192 rows, 15.6 percent, and those are the two groups where a parcel is large without being dense. Storage is also counted whether or not you are still deciding, so an idle row is never neutral. The exception is a row you merge and ship within the same week, where the clock exists but never bites.

Day 3: the decision that belongs inside the free window

By day three every question that needs an answer from the warehouse has an answer available, and the free window is still wide open. Weight and dimensions have been measured, the QC set either exists or has been requested, and the row can be merged with anything else that has arrived beside it. This is the last point at which a wrong decision costs only time, because nothing has been packed and no carrier has been booked. Use the window for the decision rather than for more research.

The decision itself has three branches, and picking one early is better than improving the pick. Ship the row alone if it is the only one coming, merge it if the rest of the haul is close behind, or leave it if a missing item would change the shape of the parcel. The merge branch carries a cost at the packing bench and a saving at the freight line, which is the trade the merge planner exists to compute. The exception is a row that cannot legally travel on its own, where the branch is chosen for you.

Day three is also when a return still looks like a cancellation to most people, and it is worth separating the two before using either. Cancelling at this point is a disposal or a send-back, and it is slower and less certain than the cancel that closes with the item payment. Returning is a claim about what arrived, and it stands or falls on the photographs taken at the warehouse. The exception is a row that arrived damaged, where the claim and the cancel are the same request.

Day 14: the first reminder

A reminder at the two-week mark is a notification rather than a deadline, and its job is to move a row that has stopped moving. Nothing about the parcel changes on that day and no fee is charged on it, so the correct response is a decision rather than a payment. Treat the reminder as the point where a row that was waiting for the rest of a haul should stop waiting. If the answer is still not to ship, write down what you are waiting for, because the next reminder will ask the same question with less time behind it.

Two weeks is also long enough for the usual reasons people leave rows behind to become visible, and most of them are about information rather than money. The QC frames may show a defect that changes the whole haul, or the listing may have been re-cut so the size you wanted no longer exists in it. Either discovery is cheaper now, while the row can still be returned or replaced, than it is at packing. The exception is a row genuinely waiting for a second parcel that is already in transit, where the reminder needs no action at all.

Day 45: past the halfway point

Halfway through the free period the arithmetic changes, because any decision that needs a new parcel to arrive no longer fits comfortably inside what is left. Merging two rows requires both of them to be present, and a return requires a round trip through the seller. Neither is impossible at this point, but both now compete with the remaining days instead of sitting comfortably inside them. The useful action is to stop adding rows to a haul you have already decided about.

The halfway mark is also where a merged parcel usually becomes the better answer than a set of small ones, because the freight line is computed on chargeable weight and one box measures less than the boxes it replaces. That is the calculation the merge planner performs, and it is worth running before the remaining days make the choice for you. Two rows that are heavy and compact will merge well, and two that are bulky will merge even better. The exception is a row that has to travel alone for legal reasons, where the arithmetic is irrelevant.

One practical habit makes the second half of the free period much easier, and it costs nothing to keep. Store the free-period end date in the same note as the arrival date, so the two numbers sit next to each other instead of in two different screens. Our own sampled list shows how far a haul can spread across categories, with 44 shirts and tees, 36 hoodies and sweaters and 27 pants and shorts among the 192 rows, and a spread like that almost always means the rows arrived on different days. The exception is a single-row haul, where there is nothing to compare and the arrival date is enough.

Day 90: the day billing starts

Ninety days is the marker this runbook uses for the end of the free period, and after it the same parcel starts producing a charge instead of waiting quietly. We publish no rate for that charge and no daily figure, because we have not measured one and a number invented here would be worse than none at all. What is checkable is the mechanism: the days are counted from the arrival date, the parcel is measured on the space it takes, and the charge is calculated per day on that measurement. The figure that binds you is the one printed against your own row, which is why the arrival date matters more than any published marker.

The billing start is usually discovered late, because nothing about the parcel changes at the moment it begins. A row that has been sitting since the spring looks identical to a row that landed last week, and the only difference is a number the interface may or may not show prominently. Two habits prevent the surprise: check the age of every open row whenever you open the account, and treat any row older than the halfway marker as a decision you have already postponed once. The exception is a row you are deliberately storing, where the charge is the price of the decision rather than a mistake.

If a charge has already started, the useful question is not how to reverse it but how to stop it growing, and the answer is the same as it was on day three. Ship the row, merge it with another, or dispose of it, and each of those three ends the accrual at a different moment. Merging ends it for two rows at once, which is why the planner is the tool to open first. The exception is a row that cannot be shipped at all, where disposal is the only action that stops the clock.

After the due date: what the warehouse actually does

After a due date passes the parcel does not disappear, and the sequence from there is administrative rather than dramatic. The warehouse continues to hold the row, the charge continues to accrue, and the messages become firmer about the fact that the row is unresolved. Every one of those messages is an invitation to choose one of three actions rather than a statement that a choice has been made for you. The exception is a row the warehouse cannot legally keep, where the disposal question arrives earlier than the storage question.

Three outcomes are available to a row that has run past its date, and they are the same three as before with less room around them. You can ship it, which ends the accrual and the storage question together. You can merge it, which does the same for two rows and usually reduces the freight line as well. Or you can abandon it, which ends the accrual without producing a parcel, and which is the right answer for a row whose freight would cost more than the row is worth. The exception is a row with an open claim, where abandoning it would destroy the evidence.

The practical way to avoid this section entirely is to treat the free period as a deadline for a decision rather than for a shipment, which is a difference of a few weeks in practice. A decision taken on day three can be executed on day eighty with no penalty, while a decision deferred to day ninety has to be executed immediately and cannot be improved. Our own sample is a reminder of how much there is to decide, with 192 rows across nine category groups and 26 of them multi-variant, so a haul is rarely uniform enough for one rule to fit every row. The exception is a single compact row, where the whole sequence takes one line to plan.