A warehouse can look full and still be short of the inventory that matters. The issue is often not total units on hand. It is that too much cash is tied up in products that have sat too long while faster-moving SKUs approach a stockout. So, what is inventory aging? It is the process of measuring how long inventory has been held and using that age to decide what needs attention before it becomes obsolete, discounted, damaged, or simply expensive to carry.
For an operations leader at a growing product business, inventory aging is not a finance-only report. It is an operating signal. It tells you where past purchasing decisions are still consuming warehouse space and working capital, and where future reorder decisions need a different approach.
What Is Inventory Aging in Practice?
Inventory aging categorizes on-hand units by the time since they were received, produced, or last moved, depending on the policy your business uses. A typical report might separate stock into 0-30 days, 31-60 days, 61-90 days, 91-180 days, and more than 180 days.
The goal is not to declare that every unit older than 90 days is bad. A replacement part, a seasonal item purchased before its selling window, or a product with a six-month supplier lead time may reasonably sit longer. Aging only becomes useful when you compare the inventory's age with expected demand, shelf life, carrying cost, and replenishment constraints.
For example, imagine a SKU with 800 units on hand. If its per-SKU forecast calls for 40 units per month, it has roughly 20 months of supply before considering incoming inventory. If 500 of those units were received nine months ago, the aging report is confirming a commercial problem: the business has much more stock than it can sell at the current rate. The right next step may be to pause replenishment, revise the forecast assumptions, transfer stock, bundle the item, or work with the commercial team on a sell-through plan.
Aging is therefore different from a simple stock count. Counts tell you what is there. Aging helps explain whether that inventory is becoming a cash and operational risk.
Why Inventory Aging Matters Before a Write-Off
Old inventory has a cost even before anyone writes it down. It occupies bin locations, complicates cycle counts, raises handling effort, and consumes attention during every purchasing review. For businesses selling across Shopify, Amazon, wholesale, marketplaces, and retail locations, slow-moving stock can also be hidden by fragmented reporting. One channel may appear short while another warehouse holds units that have been aging for months.
The financial consequence is working capital. Cash used to buy excess inventory cannot be used for products with healthy demand, supplier deposits, freight, new assortment, or day-to-day operations. That does not mean the answer is always to buy less. Cutting purchases too aggressively can create stockouts and lost sales. The practical objective is to hold the right inventory for the forecast and supplier lead time, not the lowest possible amount of inventory.
Aging also exposes a common planning mistake: treating historical sales as a reorder instruction. A SKU may have sold well last year but slowed after a price change, a channel shift, or a competitor entering the market. Reordering based on its former run rate keeps extending the aging problem. A current demand forecast and a clear view of incoming inventory are needed before the next purchase order is drafted.
How to Measure Inventory Age
The cleanest method is receipt-level aging. Each receipt is tracked as its own inventory layer, and units are assigned an age based on when that layer arrived. If a business follows first in, first out for fulfillment, the oldest receipt is assumed to sell first. This approach gives the clearest answer to how much stock is genuinely old.
Not every system has receipt-level detail that is reliable enough to support this. In that case, teams often use the date of the last receipt, the date the SKU was created, or the date of the last movement as a proxy. These methods are less precise, but they can still reveal where review is needed. The key is to document the definition and use it consistently. A report based on item creation date can make a mature, fast-moving SKU look old even when its actual units turn quickly.
Days of supply should sit alongside age buckets. Days of supply estimates how long current on-hand and incoming inventory will last at the expected demand rate. A basic version is:
Days of supply = available inventory / expected daily demand
If an item has 300 available units and expected demand of 10 units per day, it has 30 days of supply. If its supplier lead time is 45 days and the business wants a 15-day safety buffer, that position is a stock risk even if the inventory is newly received. Conversely, a product with 300 days of supply may be an excess risk even if all units arrived last week.
That distinction matters. Inventory aging looks backward at time held. Days of supply looks forward at time remaining. Strong inventory decisions use both.
Set Aging Buckets Around Your Operating Reality
Standard 30-day buckets are a reasonable starting point, but they should match your purchasing cycle and product characteristics. A business with weekly replenishment and 20-day supplier lead times needs tighter attention than one placing quarterly orders from a supplier with a 120-day lead time.
For most operators, the useful question is not, “Is this inventory 90 days old?” It is, “Is this inventory older than it should be given its forecast, reorder policy, and lead time?” A 90-day-old item can be healthy if it is a planned buffer for a long-lead-time bestseller. A 30-day-old item can be a concern if demand collapsed and there are several more shipments inbound.
Turn an Aging Report Into Decisions
An aging report that only highlights red cells creates more work. Each aging exception should lead to a specific operating decision.
First, separate aging caused by too much inventory from aging caused by a data or allocation issue. A SKU may look excess at one warehouse while another location has a stockout because transfers are not reflected in the same view. Check on-hand inventory, committed units, incoming purchase orders, warehouse context, and channel allocation before changing demand or canceling a reorder.
Next, review demand. Compare recent sales with the forecast, but avoid overreacting to a brief dip or spike. Seasonality matters. A swim product held in February may be intentional; the same stock held after the summer selling window requires a different conversation. Demand ESP, Spark's forecasting engine, forecasts every SKU across sales channels and accounts for seasonality, which gives operators a stronger basis for distinguishing planned inventory from emerging excess.
Then review replenishment. For a slow-moving, aged SKU, the default should be to pause or reduce the next order until projected inventory returns to an acceptable days-of-supply range. That decision depends on supplier minimums, lead time, future promotions, and whether the SKU supports a broader assortment. If a supplier minimum forces a larger order, you may need to combine items, negotiate timing, or accept a deliberate inventory position rather than quietly creating more excess.
Finally, assign an owner and a date. Inventory aging often spans purchasing, merchandising, warehouse operations, and finance. A useful exception record says what is happening, what action is proposed, who owns it, and when the decision will be revisited. Without that follow-through, the same aged stock appears on every month-end report.
Common Mistakes That Make Aging Less Useful
The biggest mistake is using a single aging threshold for every SKU. Fast sellers, long-lead-time items, seasonal goods, and end-of-life products need different policies. A universal 90-day rule is easy to administer, but it can create bad decisions.
Another mistake is ignoring incoming inventory. An item may not look old yet, but a large purchase order due next week can turn a manageable position into excess inventory. Reorder recommendations should account for what is already on the way, not only what is on the shelf.
Teams also lose time when aging data lives separately from purchasing action. A static monthly report can identify old stock, but it cannot tell a buyer what to reorder today, how much to reduce, or which draft purchase order should be held. The operational value comes from connecting the report to the next decision.
Use Aging to Improve the Next Reorder
The best time to address inventory aging is before approving another order. Each reorder review should ask whether existing on-hand and incoming inventory already covers demand through the supplier lead time plus the intended safety stock. If it does, a new order may be unnecessary even if an old reorder point says otherwise.
Spark brings sales history, on-hand and incoming inventory, supplier lead times, purchasing data, warehouse context, and inventory policies into one operating view. It identifies stock risk and excess-inventory risk, plans every reorder, and prepares draft purchase orders for operator review. The operator can adjust quantities, timing, or suppliers and must approve before anything is sent or committed.
This is also where modern access matters. Through Spark MCP, operators can use Claude, ChatGPT, and other supported MCP clients to map and validate inventory data from their own AI assistant, with nothing imported until they approve. That is a more practical path than treating legacy inventory software as a closed reporting system.
Text with Sparki keeps the aging conversation moving when you are away from the desk. Sparki can text a stock-risk alert or answer a question about a slow-moving SKU from your phone, and you can reply YES to create a draft purchase order when the revised reorder is ready for review.
Aging inventory will never be eliminated entirely. Some stock is intentionally held for seasonality, long supplier lead times, or service-level protection. The discipline is knowing which inventory is planned, which is drifting, and what to do before another purchase turns a manageable issue into trapped cash. Spark and Text with Sparki turn that discipline into a repeatable workflow: identify the risk, review the forecast and incoming supply, adjust the reorder, and approve the draft purchase order only when it makes operational sense.