Stockouts and Phantom Inventory (2026): Why the System Says In Stock When the Shelf Is Empty

TL;DR

A stockout leaves a product unavailable to customers. Phantom inventory is a stockout the system cannot see: the shelf is empty, but the inventory record still shows sellable units, so automatic replenishment never orders more. Shrink, receiving errors, misplacement and unrecorded damage create the gap, and staff often discuss the cause in chat or email without updating the record. This guide covers how it breaks replenishment, how to estimate the cost, and how to detect and fix it. It is published by Sentra, which understands how a company really runs, and acts on it before anyone asks. Sentra joins inventory data with staff conversations to flag discrepancies that neither source shows alone.

What a stockout is and what phantom inventory is

A stockout occurs when customers cannot buy an item because no sellable units are available. When the inventory record correctly shows zero, a replenishment rule can recognize the shortage and reorder. A shelf can also be empty while sellable units sit in the backroom.

Phantom inventory is an overstated inventory record: the system reports sellable units that a physical count cannot find. The units may be missing, damaged or misplaced. The positive balance prevents the system from flagging the shortage or placing a reorder.

The problem is common. In a study of nearly 370,000 inventory records across 37 stores of one retailer, DeHoratius and Raman found 65% of the records to be inaccurate, with the recorded quantity differing from what was physically in the store.

Check the backroom before correcting anything. If sellable units are there, you have a shelf-restocking problem. If a count finds fewer units than the system reports, you have a record error. The distinction tells you whether to move stock, correct the balance or both.

How phantom inventory breaks automatic replenishment

Automatic replenishment cannot respond to an empty shelf when the record shows stock above the reorder point. Suppose a store has no sellable units of a product, its record shows 12 and its reorder point is five. The replenishment system sees no reason to order. With nothing to sell, sales cannot draw the recorded balance down, so the false count persists until someone reports the gap or a count corrects it.

An understated record creates the opposite problem: it triggers unnecessary orders and leaves excess stock. An overstated record is worse for revenue because it keeps an empty shelf off the replenishment queue altogether. A reorder rule cannot question a count it has no reason to doubt.

Why inventory records drift from reality

• Shrink. Goods disappear through theft or loss without a matching adjustment, leaving fewer units than the record shows.
• Receiving errors. A store records a delivery of 20 units but receives 18, creating two units that never existed.
• Misplacement. The units exist in the backroom or another aisle while the shelf stays empty.
• Unrecorded damage. Staff remove unsellable goods but do not adjust the count.

A markdown changes the price, not the quantity, so it should not reduce stock unless staff also remove or transfer units. The first clue often appears outside the inventory record. An associate reports the empty shelf in chat, or a receiving clerk emails a supplier about a short delivery. If nobody posts the discrepancy as an inventory transaction, the ERP keeps showing stock that customers cannot buy.

How to estimate the cost of a stockout

Estimate stockout cost from the contribution margin you would have earned during the gap, minus the margin recovered when customers buy a substitute. Contribution margin is the selling price minus the variable cost of one unit. Keep lost revenue and lost margin separate so you do not count the same sale twice.

Stockout cost =
  expected units per day x days unavailable
  x (unit contribution margin - substitution rate x substitute unit margin)
  + estimated future lost margin
  + measurable recovery costs (for example, expedited freight)

Suppose a SKU normally sells 10 units a day at $25, with a $10 contribution margin, and the shelf is empty for four days. You estimate that 25% of customers buy a substitute that earns $6. The gap puts $1,000 of expected revenue at risk, but the immediate margin loss is 40 x $10 minus 10 x $6, or $340. If you separately estimate $40 of future margin lost from customers who do not return, the total is $380 before recovery costs. Count future loss only when you have a reasonable basis for it.

Estimate expected demand from comparable days, not from sales recorded while the shelf was empty. For phantom inventory, measure from when the item became unavailable until it was available again. If the start date is unknown, use the last confirmed available date and state the uncertainty. Because a false record suppresses reorders, the empty-shelf period usually runs longer than a stockout the system records promptly.

How to detect phantom inventory before it compounds

• Run targeted cycle counts. Count fast sellers and items with repeated shelf complaints more often than slow movers, and shorten the interval when errors appear between counts. Count shelf and backroom separately.
• Flag zero-sales anomalies. For a SKU that normally sells every day, three days with no sales and a positive on-hand balance warrant a check. Set the window from each SKU's usual sales rate, and rule out a paused promotion before assuming an inventory error.
• Compare alerts with what staff report. An associate may mention an empty shelf in chat before a zero-sales rule fires, and a planner may explain a paused order by email. Confirm the report with a targeted count so you know whether stock is missing, misplaced or waiting to reach the shelf.

The same blind spot affects delivery metrics. A supplier can post a strong OTIF score on completed deliveries while a product sits missing from the shelf, because nobody placed the order that would have refilled it.

How to fix phantom inventory once you find it

Start with a targeted count of the affected SKU, shelf and backroom, and check whether pending receipts, transfers or reserved units explain the difference. If the stock is in the backroom, move it to the shelf. If units are missing, document the count and correct the record through your normal approval process so replenishment uses the right balance.

Then trace the discrepancy to a process failure. Compare the count with receiving records, sales, transfers and damage logs. A delivery entered for more units than arrived points to receiving. Stock in the wrong location points to put-away. If the records do not explain missing units, investigate shrink rather than guessing. A short root cause analysis keeps the evidence in one place. Route the finding to the person who owns the failed process, have them change it, and repeat the count afterwards. A record correction restores today's balance, but the same gap returns if the process stays unchanged.

Lenskart: 95% reported, 12.8% on shelves

At Lenskart, a top product line was reported as about 95% in stock while Sentra measured 12.8% availability on the shelves. In Sentra's own measurements as of October 2026, about $860K of sales were lost in the two weeks before the fix. The record said the line was healthy. The shelves and the conversations about them said otherwise.

How Sentra catches the gap between the record and the shelf

Sentra understands how a company really runs, and acts on it before anyone asks. It reads email, chat, meetings and documents alongside ERP, CRM, HRIS and BI data, works out what is true now and why, and raises what is going wrong to the person who can act. When an in-stock record sits beside an empty-shelf report in a store channel, or a planner's email pauses an order the system still expects, Sentra flags the contradiction to the replenishment owner.

A named person approves each finding before it reaches anyone else. Every claim cites its source, and permissions follow the source. Sentra replaces none of the company's systems. The ERP and the replenishment engine stay in charge of the balance and the order.

FAQ