Stock ageing buckets: measure age before it costs you

Two people look at the same warehouse and report two different numbers. Planning says the average age of stock is forty days. Finance says ninety. Both are honest. Both are using a different clock. So the meeting spends forty minutes arguing about the number and zero minutes on the decision.

That is the real failure. Ageing is not a reporting problem. It is a definition problem. Until the definition is agreed and written down, every markdown conversation restarts from scratch.

Age starts at goods receipt, not at last sale

The most common measure in Indian D2C is days since last sale. It is easy to pull and it is close to useless. A SKU that sold one unit last Tuesday shows an age of six days, while nine hundred units from a February receipt sit behind it. Days since last sale measures silence. It does not measure age.

Use the goods receipt date. That is the date the units physically landed and the date your cash converted into stock. It is verifiable, it ties to a purchase invoice, and no one can argue with it.

Two traps follow. First, transfers. When you move units from your warehouse to an Amazon fulfilment centre, a 3PL node, or a quick commerce distribution centre, the receiving system stamps a new date. The unit does not become young because it moved. Age travels with the unit. Your ageing table must carry the original receipt date through every transfer.

Second, missing receipts. Imported lots, opening stock from before the current system, and returns coming back into saleable inventory often have no clean receipt date. Backdate from the supplier invoice where you can. Where you cannot, mark the units as unknown and treat unknown as old. Never treat unknown as new.

Buckets must match the category, not the calendar

Zero to thirty, thirty one to sixty, sixty one to ninety, ninety plus. Everyone uses it. It fits almost nothing.

Buckets should count towards a commercial deadline, not away from a receipt. A skincare SKU with a twenty four month shelf life sounds comfortable until you remember the minimum life on receipt that quick commerce platforms and modern trade buyers demand. If a platform will not accept stock below a stated share of remaining life, your commercial deadline arrives long before expiry does. Build the bucket boundaries around that date.

Apparel works on seasons. Units bought for a festive drop are late by January whether they are ninety days old or thirty. Electronics and accessories age against the next model launch, not against the calendar. Staples with long life and steady offtake genuinely can use wide buckets, because a slow sixty days there means nothing.

The test for a good bucket is simple. Crossing a boundary should trigger an action that a named person owns. If nothing happens when stock moves from one bucket to the next, the boundary is decoration.

SKU level hides what batch level shows

SKU level ageing gives you an average. Averages are where old stock hides. A SKU showing an average age of fifty days can be a mix of a fresh receipt and a forgotten lot from three quarters ago.

Batch or lot level is the honest unit for anything with an expiry date, anything with a manufacturing code printed on pack, and anything bought in distinct purchase orders at different landed costs. If your warehouse system cannot hold batches, approximate it with first in first out layers built from receipt quantities. It is not perfect, but it separates the lot instead of blending it.

Batch tracking costs real effort at the receiving dock and the pick face. Decide category by category. Food, beauty and anything with a regulated shelf life earn it. A hardware accessory with a five year life usually does not.

One view across warehouse, marketplace and quick commerce

Your stock sits in at least five places. Your own warehouse, a 3PL, marketplace fulfilment centres, quick commerce distribution centres and dark stores, and units in transit. Each of those systems reports in its own format and none of them reports what you actually need.

Marketplace fulfilment reports usually show inventory age in their own bands, built to explain storage fees. That is useful for fee management. It is not your commercial ageing view, because it starts from the date they received the unit, not the date you did.

Quick commerce is harder. Where the platform buys outright, the units become theirs on receipt, so your ageing exposure formally ends at that sale. In practice it comes back through expiry driven debit notes, near expiry returns and pressure to fund clearance. Where the arrangement is consignment or marketplace style, the stock stays yours the whole time. The commercial and accounting treatment of these arrangements varies by contract, so confirm how your own agreements work with your finance team rather than assuming.

Whatever the model, build one table. Keyed by SKU, batch, location, quantity, original receipt date and landed cost. Everything else is a view on that table.

The weekly report that makes ageing visible

One page. Read before the buying meeting, not after.

• Stock value by bucket, this week against last week, at landed cost. Never at maximum retail price, which flatters everything.
• Value that moved into an older bucket this week. This is the leak, and it is the number most reports omit.
• Top twenty SKUs by value sitting in the oldest two buckets, with weeks of cover at the current rate of sale.
• New entries into the oldest bucket, named, with the owner against each one.
• Actions taken last week and their result.

Weeks of cover matters more than age alone. Sixty day old stock with three weeks of cover is fine. Sixty day old stock with sixty weeks of cover is already a write down waiting for a date.

Once the definition is settled, the argument moves from the number to the decision, which is where it belongs. The decisions are markdown while the stock still has value, provisioning so the books tell the truth, and only at the end, liquidation. Get the measurement right and the first two happen early enough that the third stays small.