Dashboard showing per-SKU lost revenue from stockouts sorted by dollar impact on a dark background with red and amber indicators
Strategy

What Your Stockouts Actually Cost (Per-SKU)

ReplenishRadar Team
April 7, 2026Updated Nov 5, 20269 min read
Refreshed Nov 2026
ShareXLinkedIn
analyticsinventorykpisamazon-fbastrategy

Most sellers can rattle off their best-selling SKU: revenue per month, margin, maybe even the conversion rate. Ask which stockout cost the most money last quarter, and the answer is often a blank stare.

That is not a knowledge gap. It is a measurement gap. Your sales dashboard shows what happened. It does not show what should have happened.

You Track Revenue. You Do Not Track Missing Revenue.

Shopify and Amazon both report sales beautifully. Daily revenue, units sold, average order value. But neither platform tells you the other number: the revenue that vanished because a product was not available to buy.

Think about that for a second. You know the exact dollar amount of every transaction. You have zero visibility into the transactions that never happened because inventory hit zero.

Illustrative assumptions: a made-up catalog, not real data.

Say a mid-size Amazon catalog has 400 active SKUs. Pull the OOS data for one quarter: fourteen SKUs show stockout events ranging from 3 to 19 days. The aggregate lost revenue: over $74,000, from fourteen products across 90 days.

The seller running that catalog might have no idea. She would know she stocked out; she would remember restocking. But she might never go back and quantify the damage per SKU. The restocking feels like the fix. The money is already gone.

The Formula Is Simple. The Visibility Is Not.

Lost sales math is not complicated:

OOS Days x Daily Velocity x Revenue Per Unit = Lost Revenue

One SKU. One formula. Three inputs. Here is how we would run it on an example product:

Illustrative assumptions: a made-up product, not real data.

Variable Value
Product Stainless steel water bottle
Days out of stock 12
Daily velocity (pre-stockout) 4 units
Revenue per unit $50
Lost revenue $2,400

$2,400 from one product. Not your whole catalog. One SKU.

That number is easy to calculate in isolation. The problem is doing it across 200, 500, 2,000 SKUs on an ongoing basis. You need OOS tracking that counts the exact days out, not just a daily in-stock/out-of-stock flag, you need reliable velocity data from before the stockout started, and you need it all in one place where you can sort by impact.

Table showing five SKUs with their out-of-stock days, daily velocity, and calculated lost revenue sorted by dollar impact

That is where most sellers hit a wall. The data exists. It lives in three different places. And nobody has the patience to stitch it together in a spreadsheet every month.

The Pareto Problem

Run this analysis and one thing tends to jump out: stockout losses are often heavily concentrated.

Look again at that 400-SKU catalog. The top 5 stockouts by lost revenue accounted for more than half the total damage. Five products out of fourteen that stocked out. Out of 400 total.

Illustrative assumptions: the same made-up catalog, not real data.

Rank SKU OOS Days Daily Velocity Unit Revenue Lost Revenue % of Total
1 Bottle 32oz Black 19 14 $50 $13,300 18.0%
2 Resistance Band Set 17 12 $34 $6,936 9.4%
3 Yoga Mat 6mm Gray 16 9 $45 $6,480 8.8%
4 Meal Prep Containers 10pk 14 16 $28 $6,272 8.5%
5 Blender Bottle 28oz 12 11 $32 $4,224 5.7%
Top 5 Total $37,212 50.3%
Other 9 stockouts $36,788 49.7%

This is Pareto at work, and it means something practical. You do not need to fix all your stockouts at once. In this catalog, fixing the five most expensive stockouts recovers half the damage (an afternoon of work: adjust five reorder points, maybe expedite one PO) and $37,000 in lost sales prevented next quarter.

But you cannot do this without the per-SKU view. An aggregate "you lost $74,000 to stockouts" number tells you the problem is real. It does not tell you where to start.

Bar chart showing stockout cost by SKU ranked from highest to lowest with the top 5 highlighted

Why Velocity Matters More Than You Think

There is a subtlety in the formula that most people miss. Velocity is not the same for every product, and it is not static.

Say one product sells 2 units a day and stocks out for a week: that costs 14 units. Say another sells 20 units a day and stocks out for 3 days: that costs 60 units. The second stockout was shorter but four times as expensive in lost units.

Picture a seller spending a week chasing a restock for a slow-moving product that stocked out, while ignoring a fast mover that went OOS for just two days. The slow mover feels more urgent because it has been out longer. The fast mover can easily cost several times as much.

This is why sorting by lost revenue, not by OOS days, not by "how long has it been out", changes how you prioritize. A 3-day stockout on a high-velocity SKU is more expensive than a 10-day stockout on a slow mover. You need to see the dollars, not just the days.

From Lost Sales to Profit Drag

Lost sales are half the story. The other half is the inventory you are holding too much of.

Every SKU in your catalog sits somewhere on this spectrum:

State What Is Happening Cost
Stocked out Lost sales, ranking damage Revenue you did not earn
Understocked Days of supply running low Stockout risk building
Right-sized Demand matches supply Minimal waste
Overstocked Excess sitting in warehouse Carrying cost bleeding cash
Dead stock Nothing moving at all Storage fees + write-off risk

The combined cost of lost sales (left side) and excess holding costs (right side) is what we call profit drag. It is the gap between your actual profit margin and what your margin would be if every SKU had exactly the right amount of inventory. ReplenishRadar states it per year: recent lost sales scaled up to a year, plus a year of holding cost.

Say profit drag runs 5-15% of revenue. On a $2M business, that is $100,000-$300,000 a year in preventable waste from both ends of the spectrum.

Illustrative range, not a measured average.

The problem is that most sellers only worry about one end. Amazon sellers obsess over stockouts because the ranking penalty is brutal. Shopify sellers tend to over-order because they do not face storage fee pressure until their warehouse lease comes up for renewal. Neither group looks at both sides of the equation together.

What to Do With This Data

If you have never done a per-SKU lost sales analysis, here is how to start. It takes about an hour with a spreadsheet.

Step 1: Pull your OOS events. Go back 90 days. For every SKU that stocked out, record the product, the start date, the end date, and the number of days at zero inventory. Amazon's inventory health report has this data. For Shopify, you need to reconstruct it from inventory snapshots or use an app that tracks it.

Step 2: Get velocity and price. For each stockout SKU, pull the average daily sales velocity from the 30 days before the stockout started. Not during, not after. Before. Multiply by the average selling price.

Step 3: Run the formula. OOS days times velocity times price per unit. That is your per-SKU lost revenue.

Step 4: Sort by lost revenue, descending. This is the list that matters. The top 10 are your highest-priority reorder fixes.

Step 5: Ask why each one stocked out. Was the reorder point too low? Did the supplier ship late? Did demand spike unexpectedly? The fix is different for each cause, and the lost revenue number tells you which causes to investigate first.

Vertical flow showing the five analysis steps from pulling OOS data to investigating root causes

Automating It

That spreadsheet exercise is useful once. Doing it monthly? Nobody does. The velocity data drifts, new stockout events pile up every week, and the spreadsheet goes stale within a few months unless someone keeps updating it by hand.

This is exactly the kind of analysis that breaks down as a manual process. The inputs change constantly: velocity shifts with the season, new stockout events happen every week, prices move. By the time you finish the spreadsheet, the numbers are already outdated.

We built the lost sales analysis into ReplenishRadar's Profit Intelligence dashboard because this is the most expensive problem in inventory that most sellers never measure. The system tracks OOS days per SKU automatically, pulls the velocity data from your actual sales history, and calculates lost revenue in real time. You open the dashboard, sort by lost revenue, and you are looking at a ranked list of exactly where your money went.

We make the per-SKU lost sales table available on Growth plans and above. Standard plans see the aggregate summary (total lost revenue across the catalog), which tells you the problem is real but does not show you the individual SKUs. If you manage more than a few dozen products, the per-SKU breakdown is where the money is.

See how Profit Intelligence surfaces your lost sales. To estimate the downstream damage, the stockout cost calculator takes your stockout counts and adds ranking recovery and rush freight from figures you enter. It does not include lost repeat buyers or ad spend.

The Number That Should Keep You Up

Run the analysis. Just once. Do the spreadsheet version if you want. The number you find may be larger than you expect, and it will tell you exactly which SKU to fix first.

Then look at the top 5. Those are the SKUs where a small change to your reorder point or safety stock saves thousands of dollars next quarter. Five fixes. Maybe ten minutes each. Against thousands in recovered revenue.

The math is not hard. The visibility is the bottleneck. Once you can see what each stockout costs at the SKU level, the prioritization takes care of itself.


Related Reading:

Frequently Asked Questions

Get notified when it matters

Amazon and Shopify change the rules constantly. We'll email you when something affects your business.

Notification preferences

No spam. Unsubscribe anytime.

See what your inventory is really doing

Connect your store and see what is about to run out. No credit card is required to start the 14-day trial. Cancel any time.
Start Your 14-Day Free Trial
No credit card required14-day free trialCancel anytime

Doing $5M+ in revenue? Talk to our team