Amazon stranded inventory is FBA stock sitting in a fulfillment center with no active offer attached to it — the units are physically there, but nothing on Amazon can sell them. Amazon’s own definition, posted by staff account Topher_Amazon on the public Seller Forums: “Stranded inventory is FBA inventory in fulfillment centers that does not have an associated active offer and thus is not available for sale on Amazon” (read 2026-08-06).
The fix is never generic. Amazon says so directly: “Resolving stranded inventory depends entirely on the reason the inventory was stranded in the first place” (Bryce_Amazon, Seller Forums, read 2026-08-06). Every stranded unit carries a reason, and the reason decides whether you are one click from relisting or three weeks from an ungating approval.
This guide maps each cause Amazon names to its fastest route back to sellable, and to the removal clock running behind it. It does not cover the mechanics and fees of removal orders themselves — those live in the FBA removal orders guide — nor the aged inventory surcharge that keeps billing while a unit sits stranded.
Fact Block: What Amazon Officially Says
One sourcing caveat first, and it matters for everything below. The canonical Seller Central help pages for stranded inventory — including the reason-code table Amazon staff repeatedly point sellers to — sit behind a login wall. We confirmed on 2026-08-06 that both G200452770 and the Fix stranded inventory reference page return a sign-in page to a logged-out reader.
So every figure and quote in this guide comes from pages readable without a seller account: Amazon staff and News_Amazon posts on the public Seller Forums. Where a detail exists only inside the logged-in help pages, this guide says so instead of guessing.
| Fact | Amazon’s wording | Source (public, read 2026-08-06) |
|---|---|---|
| Definition | “FBA inventory in fulfillment centers that does not have an associated active offer” | Topher_Amazon, Seller Forums |
| Only two exits | “it requires either reactivating the listing or removing inventory” | Topher_Amazon, Seller Forums |
| Trigger events | “When you delete or close a listing, or change it from Fulfilled by Amazon to Fulfilled by Merchant, it might strand your inventory” | Bryce_Amazon, Seller Forums |
| Other triggers | “Product listing issues, infringement concerns, or system errors can also result in stranded inventory” | Bryce_Amazon, Seller Forums |
| Barcode angle | Stranded inventory “does not match the SKU it is sent in on exactly… commonly related to the labels, usually a UPC/GTIN identification error” | Glenn_Amazon, Seller Forums |
| Where you are told | “On Fix Stranded Inventory” and “Under Fix stranded inventory in the Notification section of your Inventory Dashboard” | Bryce_Amazon, Seller Forums |
| Removal clock | “30 days after this notification, your inventory will be automatically removed” | Bryce_Amazon, Seller Forums |
| Two clocks | “Listing-level stranded inventory ranges from a maximum time before disposal of 30-180 days while account-level stranded inventory has a maximum of 60 days to schedule removal” | Topher_Amazon, Seller Forums |
| Exceptions | “units with a future listing sell date or units under hazmat review are not subject to required removal” | Topher_Amazon, Seller Forums |
Note the reason-code table itself is not reproduced anywhere public. Bryce_Amazon: “This page in Seller Central has a comprehensive table that includes the various stranded inventory reason codes, and the additional information you will need to resolve it.” You have to be logged in to read it.
The Causes Amazon Names
Amazon’s public statements collapse into six causes. They are worth separating because their fix times differ by an order of magnitude.
1. Listing closed or deleted. You closed the offer, deleted the SKU, or a bulk feed did it for you. The units keep sitting in the FC with nothing to attach to. This is the most common cause and the cheapest to fix.
2. Fulfillment channel switched to FBM. Named explicitly by Bryce_Amazon. Flipping a SKU from Fulfilled by Amazon to Fulfilled by Merchant strands whatever FBA units already exist, because the offer no longer points at FBA stock. Common after a repricing or channel experiment — see FBA vs FBM for when the switch is worth it at all.
3. Item discontinued. Amazon’s automation treats this as its own class: the automatic-relist feature covers inventory stranded due to “listing closed, listing closed and inventory error, or item discontinued” (News_Amazon, Seller Forums, read 2026-08-06).
4. Inventory error / SKU-to-barcode mismatch. Glenn_Amazon’s framing is the useful one: the units in the building do not match the SKU they were shipped in on, usually a UPC/GTIN labeling problem. This is a receiving-side defect, not a listing-side one, which is why relisting alone often fails to clear it. Prevention lives upstream in Amazon barcode requirements.
5. Listing issues and infringement. Amazon groups “product listing issues” and “infringement concerns” together. In practice this covers restricted or gated ASINs you no longer have approval to sell, category or brand gating applied after your stock arrived, and rights-owner complaints. These are the slow ones — the clock keeps running while you seek approval (ungating) or resolve a claim.
6. System errors on Amazon’s side. Not a euphemism sellers invented. Dominic_Amazon confirmed one such episode on the forums outright: “We are experiencing a technical issue which can prevent you from reinstating your stranded inventory” (read 2026-08-06). When relisting genuinely does not stick after repeated attempts, this class is real and the fix is a case, not more clicking.
The Fastest Fix for Each Cause
Two exits exist, per Amazon: reactivate, or remove. Everything below is a route to the first.
| Cause | Fastest route back to sellable | What decides the speed |
|---|---|---|
| Listing closed / deleted | Relist the offer — Amazon’s automatic relist covers this class without you touching it | Automation runs on its own schedule; manual relist is faster if you catch it same-day |
| Item discontinued | Same automatic relist class | Same as above |
| Switched to FBM | Switch the fulfillment channel back to FBA — Amazon’s “automatic change to FBA” action exists for exactly this | Instant once applied; verify the offer shows FBA stock afterwards |
| Inventory error / barcode mismatch | Fix the identifier, not the listing: confirm the FNSKU on the units matches the SKU they arrived under | Needs a case if the mismatch is physical on units already in the FC |
| Restricted / gated ASIN | Obtain approval for the category or brand, then reactivate | Approval turnaround, not Amazon’s stranding system — the slowest class |
| Infringement complaint | Resolve with the rights owner or appeal; the offer cannot return while the complaint stands | Entirely outside the stranded-inventory tool |
| Amazon-side system error | Open a case and cite the SKUs; repeated relisting does not clear it | Amazon’s queue |
Two mechanics are worth calling out, both from News_Amazon’s announcement of the automated fixes (Seller Forums, read 2026-08-06). First, the automation is not limited to flagging: it performs automatic relist and automatic change to FBA for the classes above. Second, on approval timing: “Now when listings are approved by Amazon, they become automatically available for customers within 24 hours.” Plan the day after the fix, not the hour.
What no public source confirms is the button-level detail — which one-click action Amazon offers next to which reason code. Third-party blogs list “Relist,” “Edit Listing,” and “Request Approval” as the typical options; treat that as third-party information until you can read the reason-code table in your own account.
The Removal Clock You Are Racing
Stranded inventory is not a stable state you can leave alone. Amazon removes it.
The headline number from Bryce_Amazon is blunt: “30 days after this notification, your inventory will be automatically removed.” But Topher_Amazon describes two different clocks, and knowing which one you are on changes how urgent the week is:
- Listing-level stranding — “a maximum time before disposal of 30-180 days.”
- Account-level stranding — “a maximum of 60 days to schedule removal.”
Account-level is the harsher case: every SKU strands at once, and 60 days is a ceiling on scheduling the removal, not on completing it. This is the scenario behind suspended and un-onboarded accounts, where nothing can be relisted at all until the account issue clears — see account health rating.
Two documented exceptions, in Amazon’s words: “units with a future listing sell date or units under hazmat review are not subject to required removal.” The second is the useful one — stock held up in a hazmat / dangerous goods review is not on the removal clock while the review runs.
Since 2020 the end state has been automatic. News_Amazon: “Beginning June 30, 2020, FBA aged stranded inventory will no longer be classified as unsellable. Instead, such inventory will be automatically removed from Amazon fulfillment centers based on seller-configured settings.” Which brings up the setting most sellers have never opened.
The Setting That Decides Return vs. Disposal
Automatic removal follows seller-configured settings, and the default disposition is not “ship it back to me.” Sellers on the same forum thread report the default is disposal rather than return — third-party observation, but it is the expensive assumption to get wrong, so verify yours rather than trusting either claim.
Per News_Amazon, the controls live on the Fix stranded inventory page under “Edit automatic-action settings”, where the stranding threshold defaults to 30 days. The same panel is where you set whether stranded stock comes back to you or is destroyed. Amazon also documents an opt-out for individual listings: “select Opt out of auto action in the drop-down arrows to the right.” Setting a future Start selling or Offer start date has the same effect of blocking automatic reactivation.
A dating caveat on that paragraph: the “Edit automatic-action settings” wording and the 30-day default come from Amazon announcements published years before this guide, and Amazon has not restated them on any page a logged-out reader can open. The panel’s current default disposition and its selectable day range are only visible inside a logged-in account, so confirm both in yours rather than treating the numbers above as today’s settings.
If a fix genuinely is not going to land before the clock expires, the decision stops being a listing decision and becomes a disposal decision — the routes, costs, and timing are in the FBA removal orders guide.
Four Mistakes That Keep Units Stranded
Relisting without reading the reason. A barcode mismatch does not care that you created a fresh offer; the units still do not match a SKU. Cause 4 needs the identifier fixed, not the listing recreated.
Creating a duplicate SKU instead of reactivating. A new SKU gives you a live offer with zero units attached and leaves the original stock stranded — now you have two problems and a split sales history.
Assuming the storage meter stopped. Stranded units still occupy cubic feet. Monthly storage and the aged inventory surcharge keep accruing on stock that cannot generate a sale, which is what makes a slow ungating case expensive rather than merely annoying.
Treating it as a one-time cleanup. Stranding is generated continuously by ordinary operations — feed errors, channel switches, gating changes. It belongs in a weekly cadence alongside restock limits and your IPI score, not in an annual purge.
Weekly Stranded Inventory Checklist
- Open Fix stranded inventory and sort by reason code, not by unit count.
- Clear the auto-fixable classes first — closed listings, discontinued items, FBM switches.
- Escalate gating and infringement cases immediately; they are the only ones whose turnaround you do not control.
- Check your automatic-action settings: threshold days, and return vs. dispose.
- For anything that will not clear inside the window, decide on a removal deliberately rather than letting the default fire.
- Re-check 24 hours after each fix — that is Amazon’s stated window for approved listings to go live.
Frequently Asked Questions
Why is my Amazon listing stranded when I have plenty of stock?
Because stranding is about the offer, not the stock. Amazon’s definition is inventory with “no associated active offer” — the units are fine, the sellable listing pointing at them is missing, closed, blocked, or mismatched.
How long do I have to fix stranded inventory before Amazon removes it?
Amazon staff state 30 days after notification for automatic removal, with listing-level stranding running “a maximum time before disposal of 30-180 days” and account-level stranding allowing “a maximum of 60 days to schedule removal” (Seller Forums, read 2026-08-06). Your own automatic-action threshold, which defaults to 30 days, can make it shorter.
Does stranded inventory still cost me storage fees?
The units remain in the fulfillment network, so they continue to occupy storage and age. That is why a long-running gating or infringement case is the expensive kind of stranding, not the merely irritating kind.
Can Amazon dispose of stranded inventory without asking me?
Automatic removal runs on seller-configured settings, and disposal is one of the configurable dispositions. If you have never opened the automatic-action settings, you have not confirmed which disposition your account uses — check before the clock matters.
Why does relisting not clear my “inventory error” stranding?
Two possibilities. Either the units genuinely do not match the SKU they arrived under — a labeling or UPC/GTIN problem that a new offer cannot fix — or you are in an Amazon-side technical fault, which staff have acknowledged happens. Both need a case rather than another relist attempt.
Conclusion
Stranded inventory has exactly two exits: reactivate the listing, or get the units out. What decides which one you take is the reason code, and what decides how much it costs you is how fast you read it. Sort by reason weekly, clear the automatable classes on sight, escalate gating and infringement the day they appear, and know what your automatic-action settings will do on your behalf if you do nothing. All figures here checked 2026-08-06 against publicly readable Amazon sources; the canonical reason-code table is login-gated and worth reading inside your own account.