What is Stranded inventory?

What causes inventory to become stranded on Amazon

Stranded inventory almost always traces back to a listing problem rather than a physical one. The units are fine; the offer connecting buyers to those units has broken. Catching the cause quickly is the difference between a one-day relist and months of dead storage fees.

The most frequent triggers are listing-level events that sellers don't always associate with their warehouse stock. A pricing error or pricing-policy violation can suppress the offer. A category or brand gating change can deactivate the listing. An ASIN can be merged, flagged for a compliance issue, or have its detail page removed. In each case the physical units stay in FBA, fully chargeable, while the path to sell them is severed.

There's a subtler cause worth naming: bulk edits. A flat-file upload with a mistyped SKU, a blank price column, or a stray delete instruction can close dozens of listings at once while the matching units sit untouched in the warehouse. Sellers running large catalogs through spreadsheet uploads generate more stranded inventory from their own tooling than from anything Amazon does to them.

• •Pricing errors or potential-pricing-error suppressions that deactivate the offer
• •Listing closed or deleted by mistake while units remain in the warehouse
• •Category or brand gating changes that revoke your right to sell the ASIN
• •ASIN compliance flags, safety holds, or detail-page removals
• •Lost listing eligibility after an account or policy change
• •Flat-file or bulk-edit errors that close or blank out an active offer
• •SKU mismatches after a catalog migration or a merge of duplicate ASINs

How to find and fix stranded inventory

Amazon surfaces the problem in the Stranded Inventory report under the inventory tools in Seller Central, which lists every affected SKU alongside the reason and a recommended action. The fastest fix is usually to address the underlying listing issue: correct the price, reactivate or recreate the listing, resolve the gating or compliance flag, and the units become sellable again without ever moving.

When a listing can't be salvaged, your remaining levers are to relist the units under a new or corrected SKU or to remove them from FBA via a removal order, returning them for sale on another channel or disposing of them. The key discipline is speed: stranded inventory should be reviewed on a regular cadence, because every week a unit sits stranded is a week of storage fees with no offsetting revenue, and aged stock eventually attracts surcharges on top.

A practical triage order helps. Sort the report by units times cost, not by SKU count, so you work the biggest frozen capital first. Fix anything with a price or listing-state cause immediately, since those usually resolve within a day. Queue gating and compliance cases separately, because they need documentation and take longer. Then set a hard decision date on whatever's left: if a SKU isn't sellable within thirty days, issue a removal order rather than paying rent on it indefinitely.

Stranded inventory and your IPI score

Amazon folds stranded inventory directly into your Inventory Performance Index (IPI), the score it uses to gauge how efficiently you manage FBA stock. Carrying a meaningful chunk of stranded units signals poor inventory hygiene and can pull your IPI down, which in turn can affect your storage limits and capacity. In other words, ignoring stranded inventory doesn't just cost you fees on those specific units, it can constrain how much of your good inventory you're allowed to store.

That feedback loop is why proactive sellers treat stranded inventory as an operational metric, not an afterthought. Keeping the stranded count near zero protects both your fee load and your warehouse capacity headroom.

The timing of that loop is what hurts. Capacity limits are set on a forward window, so a stranded problem in one quarter can restrict the inbound shipments you need for the next. Sellers who let stranded units accumulate through the autumn often discover the cost in November, when they can't send in enough stock for peak season.

A worked example: what one stranded SKU actually costs

Put numbers on it. Say you have 400 units of a mid-size product stranded, each with a landed cost of $6.80, so $2,720 of capital is frozen. Imagine monthly storage runs $0.09 per unit in the standard season, which is $36 a month, rising in the Q4 peak-rate months. These are illustrative figures, not Amazon's published rates, so check the current fee schedule for your size tier.

Three months of stranding costs you roughly $108 in storage, which sounds survivable. The real cost is elsewhere. That $2,720 didn't buy replacement inventory, so if your capital turns four times a year at a 22% contribution margin, the forgone contribution is closer to $598. Add the risk that the units cross into aged-inventory surcharge territory, and the risk that demand for the product softens while you wait, and a $108 storage problem is realistically a $700 to $900 problem.

Now scale it. A catalog with 40 stranded SKUs at similar values isn't losing $4,300 in storage; it's sitting on roughly $109,000 of frozen capital and a five-figure hole in annual contribution. That's the framing that gets stranded inventory onto the weekly checklist instead of the someday list.

The accounting cost of stranded inventory

On your books, stranded units are inventory assets that have effectively stopped functioning as assets. They still carry their full landed cost on your balance sheet, so they make your inventory value look healthier than your sellable position actually is. If a large share of your inventory asset is stranded, your reported inventory overstates the stock you can actually convert to cash, which is exactly the kind of distortion that bites during a financing conversation, a valuation, or a tax review.

Stranded inventory also ties up working capital with no path to revenue, while continuing to generate storage charges that hit your P&L. Surfacing stranded units, quantifying the carrying cost they represent, and reconciling the storage fees they keep racking up is the kind of inventory-accounting visibility BeanHawk is designed to give Amazon sellers, so frozen capital and avoidable fees don't hide inside an otherwise healthy-looking inventory number.

There's a valuation question behind this that your accountant will eventually ask. Inventory is carried at the lower of cost or net realizable value. A SKU stranded because of a temporary price suppression is still worth its cost. A SKU stranded because you permanently lost the right to sell the brand is not, and if the realistic recovery is a liquidation price below landed cost, the difference belongs in a write-down this period, not next year. Sellers who never make that adjustment carry a slowly inflating inventory figure that has to be corrected all at once during due diligence.

Which valuation method you use decides how visible the damage is. Under the weighted average cost of inventory, stranded units share a cost pool with everything else, so their cost quietly averages into each sale and the frozen capital never appears as its own number. FIFO keeps purchase layers separate, which makes it easier to see that the oldest and most expensive layer is the one stuck. Both are accepted inventory valuation methods in accounting, so this isn't a right-and-wrong question, just a question of how much digging it takes to answer what stranded stock is costing you. The bigger fork is periodic vs perpetual inventory accounting: a periodic system only revalues at a physical count, so stranded units can look fine for a whole quarter, while a perpetual system updates cost as units move and puts the same problem in front of you within weeks.

Storage fees on stranded units raise a second question: where do they go? Amazon FBA storage is a period cost, so it belongs in expense as incurred rather than capitalized into the value of stock that isn't moving. Keeping stranded storage identifiable, ideally on its own account or tag, gives you a monthly number that makes the problem impossible to ignore. Proper amazon fba accounting means that number shows up in the P&L review, not buried inside a lump fee line.

Common mistakes with stranded inventory

The most common one is checking the report only when something feels wrong. Stranded events are created by routine catalog activity, so they arrive continuously and need a scheduled review, weekly at minimum.

The second is fixing the symptom and skipping the cause. Relisting under a fresh SKU clears the report but leaves whatever broke the original offer intact, and it fragments your sales history and inventory records across two SKUs, which makes your cost and velocity data messier.

The third is holding on too long out of sunk-cost reflex. Once a SKU has no realistic route back to being sellable, the money spent on it is gone and every extra month adds storage cost to a loss you've already taken. A removal order or a disposal is usually the cheaper answer.

The fourth is purely a records problem: removing units from FBA and never recording where they went. The stranded report clears, so the issue looks solved, but now you have inventory in a garage or a 3PL that your books still show at Amazon. Multichannel sellers with several storage locations run into this constantly, which is one reason ecommerce inventory management software that tracks quantity by location earns its cost quickly.

Building a routine that catches it early

The operational fix is unglamorous. Pull the stranded report on a fixed day each week, triage by frozen capital, resolve or remove, and log the cause so you can see patterns. Sellers who do this find that most of their stranded events come from two or three repeatable sources, usually a specific bulk-upload process or one supplier's gated brand, and fixing the source is worth more than fixing individual SKUs.

Tooling helps when catalog size makes manual review impractical. What matters in amazon inventory management software is whether it reconciles Amazon's reported on-hand quantities against your own records, values every unit at landed cost, and flags units that stopped being sellable rather than just units that stopped selling. Those are different signals, and most dashboards only show the second one. Be careful with general-purpose tools here: most inventory management software for small business is built around a warehouse you control, so it counts units on your own shelf and has no concept of stock split across FBA, a 3PL, and your own storage. Multichannel sellers should check that quantities sync both directions before judging a tool on price, because a Shopify inventory management app that never sees your FBA stock will cheerfully oversell you.

On the accounting side, look for a tool that ties storage and long-term storage fees back to specific SKUs so stranded carrying cost is visible per product, and that keeps SKU-level detail out of your general ledger while still feeding summarized journals into QuickBooks or Xero. A2X and Link My Books handle the settlement-to-ledger half well; BeanHawk covers that plus the inventory valuation side. Test any candidate on one real month of your own data before committing.

A spreadsheet still works below a certain scale. Under a few dozen SKUs on a single channel, a weekly export and a formula column showing units times landed cost will tell you everything in this article. The case for amazon accounting software gets strong once you're reconciling multiple channels or storage locations, because that's when the stranded units start hiding in the gaps between systems.

Budget is a fair filter, as long as you know what the cheap end gives up. Free accounting software with inventory management will usually track quantity on hand and stop there, with no landed cost and no fee attribution, which leaves you doing the expensive part by hand. Cheap inventory management software in the $20 to $50 range typically adds landed cost and multi-location counts. Inventory software with QuickBooks integration ranges from a small monthly add-on to a five-figure ERP, and the price difference is mostly about how much of your process it wants to own. The best inventory management software for small businesses is the cheapest one that puts landed cost, multi-location quantity, and marketplace fees in the same place. QuickBooks Online inventory management on its own is fine for a simple catalog bought and sold from one location; it wasn't designed for FBA quantities, commingled stock, or fee-heavy settlements, which is why most Amazon sellers end up attaching something to it.

Frequently asked questions

What is stranded inventory on Amazon?

Stranded inventory is FBA stock that's physically in Amazon's warehouses but has no active, sellable listing, so no customer can buy it. The units keep accruing storage fees while generating no revenue. Amazon reports it in the Stranded Inventory report in Seller Central, where you can see the cause and recommended fix for each affected SKU.

Why did my inventory become stranded?

Almost always because of a listing problem, not a warehouse problem. Common causes include pricing-error suppressions, a listing being closed or deleted, category or brand gating changes, and ASIN compliance flags. The physical units stay in FBA and remain chargeable; only the offer connecting buyers to them has broken.

How do I fix stranded inventory?

Start with the Stranded Inventory report and resolve the listing issue it identifies: correct the price, reactivate or recreate the listing, or clear the gating or compliance flag. If the listing can't be saved, relist the units under a corrected SKU or remove them from FBA with a removal order to sell elsewhere or dispose of them.

Does stranded inventory affect my IPI score?

Yes. Stranded inventory is one of the inputs to Amazon's Inventory Performance Index, and carrying a lot of it can pull your IPI down. A lower IPI can in turn affect your FBA storage limits, so unresolved stranded units can constrain how much of your healthy inventory you're allowed to store.

How does stranded inventory distort my financials?

Stranded units still carry their full landed cost on your balance sheet, so they inflate your reported inventory asset above the stock you can actually sell. They also tie up working capital and keep generating storage fees on your P&L. Tracking the carrying cost and ongoing fees of stranded stock keeps your inventory valuation honest.

How often should I check the stranded inventory report?

Weekly is a sensible floor, and daily is better if you push frequent catalog or price changes. Stranded events are generated by ordinary listing activity, so they appear continuously. The cost of checking is a few minutes; the cost of missing one for a quarter is months of storage fees on capital that could have been working.

Should I write down stranded inventory?

It depends on why it's stranded. A temporary price suppression doesn't change what the units are worth, so no adjustment is needed. If you've permanently lost the ability to sell the ASIN and the realistic recovery is a liquidation price below landed cost, the shortfall should be written down in the period you learn it, not carried forward. Ask your accountant to confirm the treatment for your entity.

What software helps track stranded inventory and its cost?

Look for something that reconciles Amazon's on-hand quantities against your own records, values units at landed cost, and attributes storage fees back to specific SKUs. That combination turns the stranded report from a task list into a dollar figure. Compare BeanHawk, A2X, and Link My Books on how they handle inventory valuation and settlement journals, and check whether the tool covers every channel you sell on before you subscribe.

Related terms

Go deeper

• Amazon Storage Fees: How FBA Charges Work and How to Cut Them
• Ecommerce Inventory Management: Quantity, Value, Reorder Points