How to Spot Aged Inventory Before It Becomes a Write-Off

Aged inventory rarely arrives as a surprise. It builds from small decisions: a purchase order placed on last year's demand, a return that never got restocked, a part that sold well at one site and sat untouched at another. By the time it shows up as a write-off in the month-end close, most of the options that could have saved its value are gone.

The usual defence is the inventory ageing report: exported from the ERP once a month and reviewed in a meeting. That report records what has already happened. If it tells you on the 3rd that stock crossed 180 days on the 12th of the previous month, it helps accounting but does little for operations.

This guide covers how to reduce aged inventory by working from live stock data. It explains how to set ageing buckets, which early-warning triggers matter, how to move stock between sites before you discount it, and what breaks when your systems don't share data. The final sections explain how The Ninjaz Group approaches the problem.

Why aged inventory goes unnoticed

Most aged stock has an ordinary cause. Knowing which causes apply to you tells you where to look first.

• Purchasing runs on a stale forecast. Reorder points set a year ago keep triggering orders after demand has shifted.
• Demand differs by site, but replenishment doesn't. Central buying treats the network as one market, or each site buys in isolation and duplicates what another site already holds.
• Stock stalls in the gaps between processes. Special orders go uncollected, returns wait in receiving, and transfers sit in transit with no one chasing them.
• Products change. A part is superseded, a model is updated, or a season ends, and the old stock keeps its place on the shelf.
• Nobody owns the item. Purchasing owns it until it arrives, and sales owns it only when a customer asks. Between those two points, ageing stock belongs to no one.
• The reporting rhythm is too slow. A monthly report can only trigger monthly action, and by then the cheap fixes have expired.

Notice that none of these is a data problem on its own. They become one when the information needed to act on them sits in different systems, reviewed at different times, by different people.

Build ageing buckets that mean something

A single set of buckets applied to every item is the most common mistake. A consumable with a limited shelf life and a durable spare part have very different risk profiles. Ninety days is an emergency for one and routine for the other.

Start by setting buckets per category, based on how long that category normally takes to sell and when it begins to lose value. A workable pattern is four bands: healthy, watch, act and critical. The "critical" band should begin well before the date you would write the stock down, so there is still time to do something about it.

Then measure two different ages, because they answer different questions:

• Age since receipt shows how long your money has been tied up in the item.
• Days since last movement shows whether anyone wants it. An item received 200 days ago but sold last week is in a different position from one received 90 days ago that has never moved.

Add a third measure, days of cover: quantity on hand divided by recent daily demand at that site. An item with 400 days of cover is a future write-off even if it is only 60 days old.

Combining age, velocity and cover is the basis of sound slow-moving inventory management. It separates stock that is merely old from stock that is old and not selling, and only the second group needs urgent action.

One configuration point deserves a check. Depending on how your ERP or warehouse system is set up, an inter-site transfer may create a new receipt and reset the item's age. If so, your ageing report will show a bucket that looks healthy for stock that has been on your books for most of a year. Confirm that age is carried from the original receipt date.

Set early-warning triggers, not just reports

A report waits for someone to open it. A trigger finds the owner. Effective stock ageing alerts fire on conditions that predict a write-off, not on the write-off itself. Useful triggers include:

• An item reaching a set share of its category's "act" threshold, for example when it enters the watch band.
• Days of cover exceeding the expected life of the product at that site.
• Quantity on hand far above trailing demand at one site while another site is low or out of stock on the same item.
• No sales movement for a set period on an item stocked at several locations.
• A supplier supersession or end-of-life notice against an item you still hold.
• Customer-reserved or special-order stock uncollected after an agreed number of days.
• Returned goods sitting unprocessed in receiving beyond a set limit.
• An open purchase order for an item that already exceeds its days of cover.

The last trigger is the cheapest to act on, because you can stop the inventory before it arrives.

Every alert needs a named owner and a short list of options attached to it: transfer, promote, return to supplier, or hold with a reason. An alert that says "item X is ageing" produces a shrug. One that says "40 units at site 4 are 20 days from the act threshold, and site 9 has three open quotes for them" produces a decision.

How fragmented systems create the problem

Consider a group with twelve locations. Financial valuation and original receipt dates live in the ERP. Each site's warehouse management system tracks bins, picks and local counts. Open quotes and customer requests live in the CRM. A BI tool refreshes overnight, but only from the ERP.

Now follow one item. Site 4 holds 40 units that arrived 150 days ago. The ERP knows the age, but the report is monthly. Site 9 sold its last unit three weeks ago, and its sales team has logged three open quotes in the CRM that depend on the item. The site 9 purchasing lead, who cannot see site 4's stock, has just raised a new order with a supplier. Nobody in the chain is careless. Each person has accurate information about their own system and none about the others.

The outcome is predictable. Site 4 crosses the write-down threshold, site 9 loses at least one of its deals to a delay, and the group ends up holding both the old stock and the new order.

The same pattern appears in other forms: a transfer recorded in the warehouse system but not reflected in the ERP, a returned item counted as available before it has been inspected, or a dashboard that shows stock by site but not by age. The cause is the same each time. The systems work on their own, but the decision needs all of them at once.

The real cost of waiting for month-end

The write-off itself is the smallest visible part of the cost. Before it lands, aged inventory takes a toll in several ways:

• Inventory. Capital is tied up in stock that isn't moving. It also takes up shelf space, can be damaged or lost, and may lose value with every month of delay.
• Time. Planners and site managers rebuild the same picture in spreadsheets each month, reconciling exports from three systems that disagree slightly.
• Lost deals. Customers at one location wait or walk away for an item the group already owns at another.
• Mistakes. Duplicate purchase orders, stock counted twice, and transfers raised for items that are not where the system says they are.
• Burnout. Site managers are pulled into end-of-quarter clearance exercises that could have been routine decisions months earlier.
• Customer frustration. Backorders and long lead times at one site, alongside idle stock elsewhere, are hard to explain to a customer.

None of these costs appears on the ageing report. They surface in service levels, staff turnover and margin, and they are rarely traced back to stock that was left to age.

Redistribute before you discount

Moving stock to where it will sell is usually cheaper than marking it down. It only works if you act early, while the item still has value and the receiving site still has demand. A practical sequence:

1. Set thresholds and owners. Define ageing buckets per category, and agree who decides what happens in each bucket and by when.
2. Get one live view of stock by site. It should show age from the original receipt date, days since last movement and days of cover, refreshed throughout the day, not monthly.
3. Match aged stock against demand. Check open quotes and orders in the CRM, backorders, and sell-through at other locations. Demand that is already documented is the strongest case for a transfer.
4. Transfer where demand exists, and cost it. Include freight and handling in the comparison. A transfer that costs more than the discount you would otherwise give is not a rescue.
5. Decide the remainder before the deadline. For stock with no internal demand, work through the options in order: promotion or bundling, supplier return, sale through another channel, discounting, and finally disposal. Make the call while each option is still open.
6. Fix the cause. Review the reorder rules, forecast assumptions or ownership gap that produced the stock, so the same item doesn't return next quarter.

Step 3 is where most groups stall, because the quote data and the stock data are held by different teams in different systems.

How The Ninjaz Group approaches it

The Ninjaz Group is a managed-services partner for multi-location enterprises. Aged inventory is a good example of the kind of problem it works on, because the cause is rarely one broken system. It is usually several working systems that don't talk to each other.

An engagement begins with a Blueprint. We map the operation and look for the places where work is done twice, data goes stale or money leaks. For inventory, that often means tracing a single item from purchase order through receipt, transfer, quote and sale, and noting where its age or location stops being visible. The client keeps the map either way.

The next stage is Build & Link. There is no rip-and-replace: the ERP, warehouse system and CRM you have already paid for stay in place. Under our Managed Link layer, Ninjaz builds, owns and maintains the integration between them. In practice, the Ninjaz Operating Platform connects to those systems and brings stock, asset and order records into a unified data layer, with one record per item and order instead of a separate version in each tool.

On top of that layer sit the pieces relevant to ageing stock: inventory and asset views across sites, a Command Center with live KPIs and alerts across locations, workflow automations that route an alert to an owner, and reports built on current data. Roles and an audit trail record who decided what.

Some limits are worth stating. The platform does not decide your thresholds, and it cannot correct source data that is wrong at the point of entry. Your category knowledge and commercial judgement still drive the decisions. What changes is that the right person sees the right stock, with demand data beside it, while there is still time to act. After go-live, Managed Business Operations can handle the day-to-day running so the connections and alerts stay healthy.

Where to start

You don't need a full programme to begin. Pick one high-value category and define its ageing buckets. Check whether your systems carry age through transfers. List the five triggers from this article that you could build soonest, and assign an owner to each. Then look at how long it takes your team to answer one question: where else in the network could this aged stock sell?

If the answer takes days or involves three spreadsheets, that gap is where your write-offs are forming. To talk through your own setup, book a consultation with The Ninjaz Group. If you'd rather see how live stock views, alerts and cross-site data fit together first, take a look at the platform demo.