Stranded inventory: definition, causes and removal deadlines

Stranded inventory is stock you paid to make, ship and check in, sitting on an Amazon shelf where no customer can buy it. Amazon defines it narrowly: FBA units in a fulfillment center with no active offer. The cause is usually a listing problem, not a warehouse one.

The deadlines, fees and page names below come from Amazon's US Seller Central help. Other Amazon stores can differ, so check the help pages for each store you sell in.

How is stranded inventory percentage calculated?

Amazon describes stranded inventory percentage as the share of your FBA units that shoppers cannot currently buy. It does not publish the exact unit basis, so treat this as a working version:

Stranded inventory % ≈ stranded FBA units ÷ total FBA units × 100

If 300 of your 6,000 FBA units have no active offer, that works out to about 5%. Amazon shows the percentage on the Inventory Performance dashboard next to a stranded units count. It is one of the four categories Amazon says influence your IPI score, alongside excess inventory, sell-through and in-stock rate, although Amazon's IPI FAQ notes that in-stock rate is not a direct input.

What causes inventory to become stranded?

Amazon tags each stranded SKU with a reason on the Fix stranded inventory page. The common ones map to a few fixes:

Stranded reason	What happened	Usual fix
Listing closed	The offer was closed or its end date passed	Relist the SKU
Missing price	The offer has no price	Add a price
Seller-fulfilled	The listing switched to merchant fulfilled	Change it back to FBA
Missing SKU	FBA units match no SKU in Manage Inventory	Create the listing at quantity 0, then change it to FBA
Deleted listing	The listing was deleted	Create a new listing
Qualification required	Brand, category or item approval is missing	Request approval, or remove the units
Blocked listing or restricted ASIN	IP, quality or safety restriction	Appeal, or create a removal order

Many are self-inflicted. Amazon's help pages point to repeat causes: closing a listing right after selling out, so returns and found units strand; inventory loader files with the quantity column filled, which flip listings from FBA to merchant fulfilled; offers whose ASIN, SKU or condition do not match the units in stock; and poor labeling at inbound, which lands units under Amazon.Found or "Missing" SKUs.

Why does stranded inventory matter for operations and growth?

• It pays storage and earns nothing. Stranded units keep accruing storage fees and keep aging. In the US store, Amazon adds an aged inventory surcharge from 181 days.
• It can lower IPI, and IPI feeds capacity. Amazon lists IPI as one input to your FBA capacity limits.
• It blocks replenishment. Amazon will not process a shipment that contains an ASIN with stranded units. Because the block works per ASIN, a few units of a best seller stranded under an Amazon.Found SKU can hold up its next shipment.
• It runs on a deadline. Amazon removes stranded units on the auto-removal date your settings produce. If you set nothing, it disposes of them once the maximum days pass: 30 for deleted listings and severe policy issues, 60 for policy violations and account issues, and 180 for closed or merchant-fulfilled units. Future sell dates and hazmat reviews are exempt. You can delay removal by 30 days once per stranded event.

What mistakes keep inventory stranded?

• Trusting Manage Inventory. A listing can show Active there while it is stranded. Amazon says the Fix stranded inventory page is the accurate view.
• Ignoring automatic actions. Automatic relist brings closed listings back after seven days, or as few as two. Automatic change to FBA switches merchant-fulfilled listings back after five days, or within a day at zero. Opt out any listing you strand on purpose.
• Leaving auto-removal on defaults. With no settings, the outcome is disposal. The return address for stranded removals is also set separately from other removal settings.
• Reading only the percentage. A 5% share can hide your highest-value SKU. Rank stranded units by landed cost and removal date.
• Fixing symptoms, not feeds. If a bulk upload or API feed keeps sending quantity for FBA SKUs, the same listings will keep stranding. Amazon suggests a 0 or 1 day automatic change to FBA as a backstop, but the feed is the real fix.

How do Growth OS and custom modules handle stranded units?

Amazon's automatic actions cover the simple cases. The rest, units that need a decision and the feeds that keep creating them, is where Ecomsellertool Growth OS and the custom layer come in.

In the base, listing fixes such as a missing price or a missing listing go out through the listings and pricing sync. Count variances between your 3PL, FBA and catalog, such as units received under an Amazon.Found SKU instead of your own, are flagged by 3PL reconciliation.

A stranded-inventory module, scoped on top of the base, can request the SP-API stranded inventory report (GET_STRANDED_INVENTORY_UI_DATA) on a timetable we set, since Amazon lets you request that report but not schedule it. The report carries the stranded reason, recommended action and auto-removal date for each SKU, so the module can group units by reason and list approval, appeal and removal cases by the date Amazon will remove them, nearest deadline first. Other checks, such as flagging stranded ASINs before a shipment plan is drafted or stopping a feed from sending quantity to FBA SKUs, are scoped the same way. Listing work builds on the audit-and-publish agents we built for Grow8. Everything we build for you is yours; the Growth OS base is licensed to you, terms on request.

Where should you start?

If nobody checks the Fix stranded inventory page every week, or idle units are adding to your storage costs, start with the free Quick Scan in our Ops Gap Diagnostic. It puts a yearly dollar figure on your top three operations gaps, and aging stock and storage fees are among the gaps it checks.