In the system, not on the shelf: how to find and fix phantom inventory
Phantom inventory is stock that exists in your system but not on the shelf. The ERP says a store has eight units; the customer and the store team find none. Because the record looks fine, automatic replenishment sends nothing, and the item can stay missing for weeks while the report shows it as in stock.
This is one of the hardest leaks to see, because every standard report agrees with the system. Stock value looks correct, the item is not flagged as out of stock, and nobody complains about a product that simply stops selling. Negative stock gets attention; positive stock that is not really there does not. The loss shows up only indirectly: lower sales, a larger write-off at the annual count, and replenishment decisions built on numbers nobody has checked.
Where phantom inventory comes from in retail and distribution
Inventory records drift away from reality through many small, ordinary errors. None of them is dramatic on its own, which is exactly why they accumulate:
- Wrong-variant scanning: a size M is sold but the cashier scans the L barcode. The system now has one phantom M and one missing L, often visible as negative stock on the sibling variant.
- Receiving errors: a delivery is booked from the dispatch note instead of being counted, or cases and pieces are confused.
- Unrecorded shrinkage: theft, damage and expired goods leave the shelf without leaving the system.
- Returns and transfers in limbo: a return is booked but the item never goes back to the floor, or a transfer is shipped out but not received at the other end.
- Wrong location: the goods are in the back room, a second warehouse bay or a promotional display the team does not check.
How to estimate what phantom inventory costs you
Phantom inventory costs you twice: the sales lost while the item is missing, and the capital and decisions tied to stock that does not exist. A simple way to size the first part: phantom cost = number of phantom store–SKU pairs × normal daily sales × days until detected × average price × gross margin.
To find the share of phantom pairs, you do not need a full count. Count a random sample of a few hundred store–SKU pairs that the system says are in stock, and note how many are actually empty.
Illustrative example (hypothetical, round numbers): 30 stores with 3,000 active SKUs make 90,000 store–SKU pairs. Suppose a sample count suggests 2% show stock in the system but nothing on the shelf: 1,800 pairs. If each normally sells 0.3 units a day at an average price of 200 TL and stays unnoticed for 20 days, that is 1,800 × 0.3 × 20 × 200 = 2,160,000 TL of sales not made. At a 35% gross margin, about 756,000 TL of gross profit per cycle, before counting the write-off at year end.
Why annual counts, ERP reports and spreadsheets miss phantom stock
- Replenishment trusts the record: if the system shows stock, no order is triggered. The error protects itself.
- Annual counts come too late: a year-end count finds the difference but not when it started, and the lost sales are already history.
- Variances are written off in aggregate: the count difference is booked as one number per store, without a root cause per item.
- Reports look at stock or sales, rarely both: an item with stock and zero sales is not flagged by a stock report or a sales report.
- Blanket cycle counts spend effort evenly: counting every item on a rota uses staff time on items that are almost always correct.
How AI agents detect phantom inventory: detect, diagnose, assign, measure
The strongest signal of phantom stock is already in your data: an item with positive stock that stops selling when it normally sells steadily. For an item that usually sells two units a day, seven days without a sale is not bad luck. An AI agent runs this check every day, using anomaly detection that weighs how unlikely each silence is given the item's usual pace. It also watches negative stock on sibling variants and receiving quantities that differ from order quantities. To diagnose, it looks at the item's last movements: a recent receipt, a transfer still in transit, a return, or a sibling size with negative stock that points to a barcode mix-up. It then assigns a targeted count: a short list of items, with likely locations, sent to the store team. Stock adjustments go through human approval at region or head office, because adjustments affect valuation. Finally it measures: how many alerts were confirmed, and how the item sold once the record was corrected.
The inputs are the same data you already hold: daily sales, stock by location, receipts, transfers, returns and adjustment history. Zzeti runs these agents on your own servers or private cloud, reading Nebim V3, Logo or SAP data through MCP connectors, so inventory and sales data stay inside the company. Count tasks and adjustment approvals flow through the Actions Inbox, and each alert shows the query behind it, so the store team sees why an item was chosen rather than receiving an unexplained count list.
A 4-week pilot plan to improve inventory accuracy
- Week 1: pick 5–10 stores and connect sales, stock, receipts, transfers and returns. Agree what tolerance counts as accurate (for example, exact match for high-value items).
- Week 2: run a random sample count to set a baseline for inventory record accuracy and phantom rate.
- Week 3: switch to targeted counts: each store gets a short daily list of suspected phantom items. Corrections go through approval.
- Week 4: compare the hit rate of targeted counts with the random baseline, track sales of corrected items, and group root causes to fix processes such as receiving or scanning.
Inventory accuracy KPIs to track
- Inventory record accuracy: share of counted store–SKU pairs within tolerance.
- Alert precision: share of phantom alerts confirmed by a count.
- Days from alert to correction.
- Sales of corrected items in the 14 days after correction.
- Negative stock lines, by store.
- Adjustments by root cause (scanning, receiving, shrinkage, returns, transfers).
Your replenishment is only as good as your stock records. Let the data tell you which few items to count each day, fix the record quickly, and remove the process errors behind it.
Frequently asked questions
What is phantom inventory?
Phantom inventory is stock that your system shows as available but that cannot be found or sold. Because the record looks healthy, replenishment does not trigger and the item can stay missing for a long time.
How can I detect phantom inventory without a full stock count?
Look for items with positive stock that have stopped selling although they normally sell regularly, and for negative stock on sibling variants. Count only those items. This focuses staff time where errors are likely.
How often should we do cycle counts?
Rather than a fixed rota for every item, count fast movers and high-value items more often and let data signals trigger extra counts. Keep a small random sample each month so you can still measure overall accuracy.
Does RFID solve phantom inventory?
Item-level tagging can improve accuracy for tagged goods, but it requires investment and disciplined processes. Many companies can make measurable progress first with the sales and stock data they already have.
In the system, not on the shelf
Zzeti flags products whose sales flat-line while stock is still on record, assigns a count task to the store and gets the item back on sale once the record is corrected.