
E-commerce returns: when does a returned item count as stock?
Between a return being received and the item going back on the shelf, books and shelves can disagree for days. A few clear return statuses close most of that gap.
A parcel comes back. The customer has been refunded or sent a replacement, and the courier has handed the box to your storekeeper. The question that decides whether your numbers stay clean is simple: from which moment does that item count as stock again? In many e-commerce businesses the honest answer is "whenever somebody gets round to it", and the result is a few days in which the books and the shelves disagree about every returned item.
Three clocks that do not run together
A return has three clocks, and they rarely tick at the same time:
- The money clock: when the refund is paid.
- The parcel clock: when the box physically arrives.
- The shelf clock: when the item has been checked, packed if needed, and put into a bin where it can be picked.
Only the third one creates sellable stock. If the system adds the item back on the parcel clock, the listing shows it as available before anyone has opened the box. That is how a damaged phone case gets sold a second time. The misalignment is not anyone's mistake. The process was never defined, so the fix is a definition, not more reminders.
Give returns a small set of statuses
Define five or six statuses and make everybody use them:
- Received: the box is at the dock and has not been opened. Not stock.
- Inspected: opened and checked, with a note of the result.
- Restockable: as good as new. It goes to its normal bin, and only now does the sellable quantity rise.
- Repack: needs new packaging or a new label. It goes to a repacking area and becomes stock when the work is done.
- Damaged: cannot be sold as new. It is written off, or sold at a discount under a separate SKU.
- Return to supplier: goods that qualify for a claim.
The rule is short: only "restockable" raises sellable stock. Everything else is counted, but kept apart.
A returns bin with a code of its own
Make the returns area a proper location with its own label, for example R-01. A scan puts the item into that location, so it appears in the count as returns and not as part of the normal stock. Never let returned items drift back onto ordinary shelves before inspection, because from that moment nobody can tell them from good stock.
What happens to the numbers
Suppose 30 pieces of SKU B-0360 come back in one week. After inspection 18 are restockable, 7 need new packaging and 5 are damaged.
If all 30 are booked back as stock on arrival, the sellable quantity is 12 too high (7 plus 5). The marketplace listing may accept 12 orders that cannot be filled, and they end in cancellations. Each cancellation also costs a customer message and goodwill, far more than one extra day for inspection. With statuses, the 18 become stock on the day they reach the shelf, the 7 follow after repacking, and the 5 never enter sellable stock.
Who does what
Keep the roles apart. The storekeeper receives the parcel and sets the status to received. A second person inspects and decides the status. Operations or finance books refunds and write-offs. When the person who inspects is not the one who approves a write-off, every loss has a second pair of eyes on it, and the numbers are easier to trust.
Put a time limit on it
Set your own target, such as inspection within two working days of arrival, and report the aged returns every week. A returns bin that holds a month of unchecked parcels is a hidden stock problem, and at count time it will show up as an unexplained surplus.
Some returns go to the marketplace's warehouse, where you cannot inspect them. For those, record the quantity and the status as the platform report gives it, and mark the line "at marketplace".
InventoryHub's e-commerce SKU reconciliation looks specifically for returns that have not yet been shelved when it compares back-office stock, your ERP records and the physical count, and lists them by SKU so that you can see how many are waiting.