You've got sales coming in, buy boxes are holding, and the dashboard looks healthy enough. Then Seller Central starts flashing the ugly stuff, excess units, aging stock, a few stranded ASINs, and that sinking feeling that your “good month” is hiding cash tied up in the wrong places.
That's the trap with Amazon inventory management. Revenue can look fine while margin leaks out through storage drag, stockouts, and poor placement decisions that never show up in a top-line report. The work is less about guessing reorder quantities and more about running a tight operating system, the kind that turns inventory from a passive asset into a measurable profit lever. If your current process feels reactive, start by mapping the flow end to end with a supply-chain lens like the one outlined in this Amazon supply chain resource.
Why Most Amazon Sellers Lose Money on Inventory
A brand can be “growing” and still be making less money every month. That usually happens when the inventory stack is out of sync with demand, so the business pays to store product that isn't moving, then pays again when the fast movers run out and sales stall.
The most common pattern is simple. A seller over-orders after a good run, the product ages in FBA, and the next replenishment lands too late or in the wrong place. By the time the team notices, cash is tied up in slow stock, the top ASIN is losing traction, and the warehouse is carrying more risk than revenue.
Practical rule: if you can't explain where every unit is in the fulfillment network, you're not managing inventory, you're hoping it behaves.
The hidden cost isn't just fees. It's the way weak inventory discipline distorts decisions everywhere else, from ad spend to pricing to supplier commitments. A catalog with messy replenishment can make profitable SKUs look weak, and weak SKUs look worth saving. That's why the best operators treat inventory as part of commercial strategy, not a back-office task.
A useful mindset shift is this, Amazon doesn't reward “having stock,” it rewards having the right stock in the right place at the right time. When that discipline breaks down, sellers usually feel it first in sell-through, then in storage pressure, then in customer experience. Strong revenue can mask the problem for a while, but it doesn't fix it.
The operational fix starts with clarity. Know what's moving, what's aging, what's stranded, and what's likely to sell before you buy again. That's the difference between scaling cleanly and funding your own inefficiency.
Understanding the Inventory Performance Index Scorecard
Amazon's Inventory Performance Index, or IPI, is the scorecard sitting underneath most FBA inventory decisions. Amazon describes it as a weekly-updated score for FBA sellers, driven by four factors, excess inventory, sell-through rate, stranded inventory, and in-stock rate on popular ASINs. That design matters because it turns inventory into a live operating system rather than a static stock count. Amazon's IPI guidance makes the logic explicit.
The four drivers that actually matter
Excess inventory tells you when stock is drifting into storage waste. Amazon's own guidance says inventory becomes excess when it has been in storage for more than 90 days without selling, which is a blunt but useful signal that demand didn't meet your buy plan. Stranded inventory is the opposite problem, product that exists in the network but can't be sold because the listing or fulfillment setup is broken.
Sell-through is the cleanest operational measure in the group. Amazon defines it as units sold and delivered over the past 90 days divided by the average number of sellable units in fulfillment centers during the same period, and it also frames it in more straightforward terms as units sold divided by units received. Either way, the signal is the same, inbound supply has to turn into outbound demand quickly enough to justify the slot it occupies.
In-stock rate on popular ASINs is where many sellers lose momentum. You can have inventory in the account and still miss demand if your strongest items go out of stock or sit underfed in the network. Amazon's scorecard is built to punish that mismatch.
Practical rule: a strong IPI isn't built by ordering more. It's built by removing drag faster than you add it.
What the dashboard is really telling you
Amazon's FBA inventory dashboard surfaces FBA percentage in stock over the last 30 days, weighted on sales from the past 60 days, the number of out-of-stock SKUs in the last 30 days, estimated excess units, days in inventory, and turns. Those are not vanity metrics. They show whether you're feeding the network well enough to protect revenue while avoiding excess buildup. Amazon also recommends setting measurable goals, such as reducing stockouts by 20% or lowering lead times, which reinforces that this is a quantified management problem, not a loose planning exercise. Amazon's inventory optimization guidance is very clear on that point.
For practical management, use the IPI as a weekly control loop. If sell-through weakens, check aging stock first. If in-stock rate slips, check replenishment cadence and placement. If stranded inventory shows up, fix listing issues before you buy another unit. The scorecard only works when every replenishment decision is tied back to one of those four drivers.
Amazon sales data guide can help teams structure the reporting discipline around that weekly review.
Choosing Between FBA and FBM Workflows
The FBA versus FBM choice is usually framed as a fee debate. That's too shallow. The decision is about how much control you need over inventory placement, how much margin your product can absorb, and how fast the item really moves.
When FBA wins
FBA usually wins for high-velocity, compact products that benefit from Prime eligibility and distributed fulfillment. If the item sells consistently, the network can absorb the operational complexity, and the customer-facing upside is easy to justify. The trade-off is that you give up some control, and storage pressure becomes part of the cost structure.
That trade-off gets expensive fast for oversized or slow-moving items. Thin-margin products can look fine in a P&L until storage and aging inventory start compressing the economics. If a SKU doesn't move cleanly, FBA can become a holding pattern for capital.
When FBM wins
FBM is usually stronger when the product is bulky, unpredictable, or tied to a supplier that can fulfill reliably without sitting on too much finished stock. It gives you more control and can reduce exposure to long-term storage pressure. It also fits better when you want to test demand before committing deeper inventory to Amazon's network.
There's also a useful hybrid move. Keep core volume in FBA, then use FBM as a backup on slower or riskier SKUs so a stockout doesn't take the listing offline. That approach protects availability without forcing every unit through the same cost structure. If you're still figuring out how prep, labeling, and handoff affect this choice, the guide on what is Amazon prep service is a solid operational reference.
Some teams over-index on the badge and under-index on the economics. Prime traffic doesn't matter if fulfillment friction is eating the spread.
For setup and margin thinking, the important question is simple, which workflow gives you the most reliable order-to-cash path for this SKU, not for Amazon as a whole? That answer changes by product family, season, and supplier performance. For broader marketplace structure, the internal reference on merchant on Amazon fits well alongside this decision.
Forecasting Demand and Calculating Safety Stock
Good forecasting is less about getting the future exactly right and more about building a replenishment system that doesn't fall apart when demand gets noisy. On Amazon, that means using the dashboard data you already have, then layering in seasonality, promo spikes, and supplier variability with enough discipline to avoid panic buys.
Build the forecast from actual selling behavior
Start with the last clean stretch of demand, not the busiest week you can find. Use Amazon's inventory reporting to watch FBA percentage in stock, estimated excess units, days in inventory, and turns, because those metrics reveal whether the forecast is too aggressive or too cautious. If inventory stays high while turns slow, the buy plan is too loose. If in-stock rate slips and the best ASINs go dry, the plan is too tight.
Then adjust for lifecycle stage. Launch SKUs need tighter review cycles because demand is unstable. Mature SKUs can be forecast with more confidence, but only if reorder timing and supplier lead time stay steady. Discontinuing products need a different rule set altogether, because the goal shifts from growth to controlled sell-down.
Use a buffer that matches risk, not habit
Safety stock should reflect the risk profile of the SKU. A stable supplier and consistent demand need less buffer than a product with volatile lead times or promotional swings. The point is to protect service levels without creating dead stock that later shows up as excess inventory in Seller Central.
A simple operating habit helps. Recalculate reorder timing every week for fast movers, every cycle for slower ones, and more often around seasonal peaks. Q4 and major promotional events deserve separate planning because demand can distort quickly when traffic concentrates.
If you need a broader planning lens, the Logivo piece on practical predictive analytics for SMEs is useful context for how to structure data inputs without overcomplicating the model.
You don't need a perfect model to improve results. You need a repeatable process that updates often enough to catch changes before they turn into stockouts or overflow. Preventing stock outs starts with that discipline.
Cleaning Up Stranded Inventory and Returns
Stranded inventory is one of the easiest ways to damage both cash flow and IPI health. The unit exists, the demand exists, and yet sales don't happen because the listing is broken, suppressed, or detached from the correct fulfillment setup. That's pure operational waste.
Treat stranded inventory as a revenue leak
The first move is diagnosis. Find the stranded ASINs, identify whether the problem is listing, pricing, variation structure, or fulfillment configuration, then fix the root cause before creating more inbound stock. Buying more product while stranded inventory is unresolved only increases the pile of inventory that can't convert.
Returns need the same level of discipline. A weak returns workflow turns recoverable inventory into write-offs, while a tighter process can route items back into sellable stock, refurbishment, or removal before they decay further. That matters especially for products that come back in usable condition but lose value when they sit.
Sync matters more than most sellers think
Multi-channel inventory sync is where many brands create their own oversell risk. If Amazon, eBay, Walmart, and DTC all pull from the same pool without a reliable buffer or real-time sync, one channel can sell the last unit while the others still think stock is available. The result is canceled orders, customer service noise, and replenishment confusion.
A clean setup uses one source of truth for available stock and reserves a buffer for latency between channels. That buffer doesn't have to be huge, but it does need to be intentional. Without it, inventory accuracy starts drifting the moment orders arrive from more than one marketplace.
Practical rule: if a SKU is sold on multiple channels, inventory should be managed by process, not by whoever updates the spreadsheet last.
For reverse logistics and recovery planning, the article on handling returned freight efficiently gives a useful operational angle. For a more general process lens, the internal guide on inventory management best practices fits this cleanup work well.
The best teams connect these three problems, stranded stock, returns, and sync, into one workflow. That way, a return can become sellable inventory, a channel oversell can be prevented before it happens, and the IPI stops absorbing avoidable damage from operational sloppiness.
Tracking the KPIs That Actually Matter
The right KPIs change with the stage of the product, but the dashboard has to stay connected to profit. Revenue alone doesn't tell you whether inventory is healthy. It only tells you that something sold.
Compare the metrics by growth stage
| KPI | New Seller Target | Scaling Seller Target | Established Brand Target |
|---|---|---|---|
| Sell-through rate | Watch weekly | Track by SKU family | Manage as a portfolio |
| Days on hand | Keep tight | Balance with launch risk | Use for replenishment discipline |
| Fill rate | Protect availability | Reduce stockout gaps | Maintain service consistency |
| Stockout rate | Minimize early misses | Watch top ASINs closely | Keep strategic SKUs in stock |
| Landed-cost variance | Flag surprises early | Compare suppliers regularly | Use for sourcing decisions |
The table works because it forces the team to ask a different question at each stage. A new seller needs signal, a scaling seller needs consistency, and an established brand needs control. The same metric can matter in all three stages, but the action behind it changes.
Pick tools based on the problem you're solving
Amazon's native dashboards are enough for many smaller catalogs. They show the operational basics, and if the SKU count is manageable, that may be all you need. Once the catalog expands or channels multiply, third-party inventory systems start to earn their keep because they centralize replenishment logic, sync across channels, and make exceptions visible faster.
The right tool stack should answer a few practical questions. Which SKUs are at risk? Which supplier is driving variability? Which channel is overselling? Which items are aging into excess? If a platform can't surface those answers quickly, it's probably adding complexity instead of control.
Next Point Digital is one option for brands that want inventory and fulfillment guidance tied to marketplace growth, especially when Amazon, eBay, and Walmart are all in play. The value is in combining reporting, listing work, and operational decisions so inventory planning doesn't live in a separate silo.
Building Your Inventory Management Action Plan
Treat inventory like a profit lever and the business gets easier to manage. Treat it like a warehouse problem and you keep paying for mistakes that show up later as storage drag, missed sales, and weak replenishment signals.
Days 1 to 30
Audit stranded ASINs, aging units, and out-of-stock risk on your top sellers. Tighten the reorder points on the most important SKUs and remove any inventory that's clearly not moving. If the data is messy, fix the reporting first, because every other decision depends on it.
Days 31 to 60
Install a weekly inventory review cadence. Build a simple forecast that reflects seasonality, supplier reliability, and channel mix. Then decide which SKUs belong in FBA, which belong in FBM, and which need a hybrid backup.
Days 61 to 90
Automate the sync points that still rely on manual updates. Refine placement so product sits closer to demand, not just closer to a warehouse. By then, you should be measuring fewer stockouts, less excess, and more consistent sell-through.
The brands that win on Amazon usually aren't the ones buying the most inventory. They're the ones controlling inventory with enough discipline to keep cash moving and demand covered.
If your Amazon operation is growing faster than your inventory process, Next Point Digital can help you turn that chaos into a system. Visit Next Point Digital to see how inventory and fulfillment support can fit into a broader marketplace growth plan built around measurable outcomes.