What inventory aging analysis measures
Inventory aging analysis is a backward-looking metric. For every unit of stock on hand, it asks one question: how long has this been sitting? The answer gets categorized into buckets, each representing an escalating level of concern and a different required response.
The distinction between aging and days on hand is important. Days on hand is forward-looking: given current stock and current demand, how many days of coverage do we have? Aging is backward-looking: given current stock, how long has it been sitting without being consumed? An item with healthy DOH that experiences a sudden demand drop will look fine in a DOH report for a while, because DOH is calculated on current consumption rates. But its aging clock starts ticking the moment demand stops. Aging catches the early signal that DOH can miss.
The purpose of aging analysis is not just classification. It is to quantify how much capital is tied up in inventory that is not contributing to revenue, calculate the carrying cost of holding it, and generate a ranked action list before the situation becomes a write-down problem. The earlier the intervention, the more options are available: return to supplier, inter-company transfer, customer order search, or liquidation at partial value. At 365+ days, most of those options are gone.
Three ways to define item age: which one to use
Age means different things depending on what you are trying to measure, and choosing the wrong definition produces a report that looks actionable but is not.
Age since last receipt
Counts days since the most recent purchase receipt or production completion for the item. This is the simplest to extract from ERP data and the most common default. The limitation: an item can receive a new receipt that resets the aging clock even though existing stock has been sitting untouched. A SKU with 500 units that aged for 200 days, received 50 more units, and now shows as "5 days old" has buried its exposure in the receipt date logic.
Age since last warehouse movement
Counts days since any transaction touched the on-hand balance, including issues to production, customer shipments, adjustments, and transfers. Better than receipt date because actual consumption resets the clock appropriately. The limitation: a small partial issue can reset the aging clock on a large inventory balance that is effectively stagnant. An item with 2,000 units that issued 5 units to a test order last month shows as "30 days old" despite 1,995 units that have not moved in a year.
Age since last demand
Counts days since any consumption-driven event: production order issue, sales order fulfillment, transfer out. Ignores internal adjustments and receipt transactions entirely. This is the most meaningful definition for most manufacturers because it asks the core question directly: when was this item last needed? An item with non-zero demand within 90 days is still being consumed. An item with no demand event in 180 days has a problem regardless of recent receipt dates or adjustments.
For finished goods, age since last sales order shipment is the appropriate analog. For components and raw materials, age since last production order issue or warehouse issue to production is the right measure. Most robust implementations track both receipt date and last demand date at the unit or lot level, allowing the aging report to surface items where the stock is old even when recent receipts have masked the exposure.
The five aging buckets and what lives in each
Standard aging analysis uses five buckets. The boundaries below represent a reasonable starting framework for discrete manufacturers. Items with very long supplier lead times (aerospace, specialty materials) may warrant pushing the watch threshold to 60 or 90 days. High-velocity consumer goods may compress everything.
Root causes by aging category
The aging bucket tells you the urgency. The root cause tells you what to fix. The same item can land in the same bucket for very different reasons, and the right disposition path depends on understanding which one applies.
| Aging Bucket | Most Common Root Causes |
|---|---|
| Watch (31-90d) | Seasonal demand gap; recent engineering change with demand expected to resume; forecast error on a specific batch; short-term customer order pause |
| Slow Mover (91-180d) | Customer loss or order cancellation not reflected in MRP; product substitution that made this component obsolete; delayed project start where the end-customer pushed timelines; minimum order quantity that forced over-purchasing |
| Dead Stock (181-365d) | Discontinued product line; failed new product launch leaving WIP and purchased materials stranded; post-acquisition inventory from predecessor entity's line that does not fit combined company's product portfolio; safety stock policy never revised after demand dropped |
| Write-Down (365+d) | Confirmed obsolescence deferred by operations or finance; cumulative slow-mover exposure that was not acted on in prior periods; post-acquisition items that were never written down at time of acquisition and are now beyond recovery |
Post-acquisition environments typically show a compression of all four problem categories simultaneously. Acquired entities often carry undisclosed aging inventory that appears on the balance sheet at full book value. A systematic aging analysis in the first 60 days after close is one of the highest-value data exercises a new owner can run, because the discovery of aging exposure is much more manageable before the first financial close under new ownership than after.
How aging connects to inventory turns
Aging and inventory turns are inverse metrics measuring the same underlying phenomenon. An item turning less than once per year is, by definition, accumulating aging exposure. If you run turns at the SKU level, aging items appear automatically in the bottom quartile. The two analyses complement each other: turns quantifies velocity, aging quantifies stagnation. Running both gives you a complete picture.
The relationship holds in reverse as well. An aggregate turns figure that looks adequate may contain a significant aging tail that is depressing turns without surfacing in the aggregate number. A portfolio of 1,000 SKUs with 850 turning well and 150 turning below 0.5x will produce an aggregate turns figure that looks acceptable. The aging report surfaces those 150 SKUs as a discrete group with a specific dollar exposure and a specific action path.
The working capital math: Inventory in the Slow Mover and Dead Stock buckets at an 8 percent annual carrying rate costs approximately $2 for every $25 of book value per year. On a $2M aging inventory exposure, that is $160,000 per year in pure carrying cost before any write-down. The write-down, when it comes, is incremental. Acting at the 91-day mark rather than the 365-day mark preserves both the carrying cost savings and the liquidation optionality.
The action framework: what to do at each bucket
An aging report without an action protocol is just a list. The value is in routing each bucket to the right team with the right mandate and the right deadline. The framework below assumes a manufacturer with operations, procurement, finance, and sales functions, each with visibility into different pieces of the disposition path.
- Review and suspend any open POs for this item
- Check if demand gap is seasonal or structural
- Confirm with sales if any open opportunities exist for the item
- No new purchase orders until cleared
- Check sister plants for transfer need
- Explore supplier return or credit option
- Identify any alternate use cases within the product line
- Assign a disposition owner with a deadline
- Escalate to ops and sales leadership for final disposition decision
- Notify finance for potential reserve consideration
- Obtain liquidation bids if recovery is still possible
- Document disposition decision and timeline
- Initiate formal write-down review with CFO sign-off
- Execute scrap, disposal, or liquidation
- Record write-down with root cause documentation
- Review purchasing and safety stock policies to prevent recurrence
How IQ Insights flags aging inventory continuously
The problem with a periodic aging review is that items cross bucket boundaries between review cycles without anyone noticing. An item that crossed into the Slow Mover bucket three weeks ago is now seven weeks closer to Dead Stock before the next monthly review finds it. Continuous monitoring with threshold-based alerts closes that gap.
Bucket crossing alerts: IQ Insights monitors every SKU's aging status daily and alerts the responsible buyer or planner the day an item crosses a bucket threshold. The alert includes the item, the aging bucket it entered, the on-hand value at risk, and the last known demand date, so the recipient has everything needed to act without running a separate report.
Post-acquisition aging sweep: For PE-backed manufacturers adding a new entity, IQ Insights runs an initial aging sweep across the acquired entity's full item master within the first data load, classifying all on-hand inventory against the same framework. This surfaces undisclosed aging exposure before the first close rather than discovering it incrementally over the following quarters.
Cross-plant aging transfer matching: Items in the Slow Mover or Dead Stock buckets at one plant are automatically cross-referenced against the item master at all other plants to identify transfer opportunities. A component aging at Plant A that is in the Stockout Risk zone at Plant B is flagged as a transfer candidate, not a write-down candidate.
How Inventory IQ surfaces aging exposure from your ERP
Inventory IQ connects to your ERP, calculates aging for every on-hand unit using last demand date rather than receipt date, classifies each item against the five-bucket framework, and routes alerts to the right team the day a threshold is crossed. For multi-plant environments, cross-plant transfer matching runs automatically once the item master is unified.
Inventory IQ calculates aging from last demand date for every active SKU, assigns each to the appropriate bucket, quantifies the carrying cost and write-down exposure, and alerts the responsible owner when items cross thresholds. In multi-plant environments, it identifies inter-company transfer opportunities before items reach Dead Stock status. Post-acquisition, it runs a full aging sweep in the first data load.