Amazon FBA Stranded Inventory: Causes, Costs, and the Fix for Every Reason Code

Most guides on Amazon FBA stranded inventory tell you to open the Fix Stranded Inventory queue and click relist. That advice is correct but incomplete. By the time a unit appears in that queue, the mistake that created it was made days or weeks earlier - at the prep table, in the shipment plan, or in a compliance document folder nobody checked before shipping. This guide starts at those upstream causes, traces the full financial cost from the first day stranded through the automatic removal trigger, catalogs every major reason code, and ends with a workflow that catches problems before the clock has run for a week.

What Makes Inventory Stranded - and Why It Is Worse Than Just Unsellable

Stranded inventory is FBA stock that is physically present at a fulfillment center but has no active listing attached to it. Amazon cannot match the units against any offer, so customers cannot purchase them. The units occupy warehouse space, generate storage fees, and produce zero revenue simultaneously.

This is different from unfulfillable inventory, which typically describes units that are damaged or have failed an inspection. Unfulfillable units are ineligible for sale because of their condition - that status is clear and the resolution path is limited. Stranded units are often in perfect condition. The disconnect is administrative: a closed listing, a flagged price, an expired certificate. That kind of problem is fixable, but only if you act before the removal trigger fires.

The financial problem is the overlap of ongoing costs against zero revenue. Storage fees accrue every month whether the unit is sellable or not. Those fees run lower through most of the year and rise sharply during Q4 - the months when a stranded unit sitting idle is paying peak-season rates while generating nothing. On top of base storage, the aged inventory surcharge begins after a unit has been in FBA past a multi-month threshold, and it escalates steeply for units approaching a year in storage. That surcharge applies to stranded and sellable inventory alike. A unit that strands in September and is not resolved before the new year can end up paying both peak storage rates and an aged surcharge simultaneously.

The Full Cost Stack: Storage Fees, Aged Inventory Surcharge, Removal Fees, and the IPI Multiplier

The Direct Costs

Consider a standard-size unit that enters stranded status in late September. It pays peak-season storage rates through December, then shifts to lower off-peak rates in January - by which point it may be approaching the aged inventory threshold. Cross that threshold and a surcharge begins layering on top of base storage. For units approaching a full year in FBA, that surcharge can reach multiples of the base monthly rate. Check Amazon's current fee schedule for specific figures, as rates are updated periodically - what matters structurally is that each of these costs runs independently and accumulates whether the unit is selling or not.

When the automatic removal trigger fires, the seller also pays a removal or disposal fee. These fees scale by unit weight, so heavier products carry higher exposure. On a low-margin or heavy product, the combined cost of peak storage, an aged surcharge, and a removal fee can exceed the unit's landed cost entirely.

The IPI Multiplier

The less visible cost is the Inventory Performance Index impact. Amazon evaluates IPI quarterly to determine whether a seller faces storage limits at fulfillment centers. The formula weights four factors: excess inventory percentage carries the largest weight, followed by sell-through rate, then stranded inventory rate, then in-stock rate. The stranded inventory rate - what share of your total FBA inventory is currently stranded - carries a meaningful portion of the overall score. Sellers whose IPI drops below Amazon's current threshold face storage limits that restrict how much they can send in. During peak season, that restriction can cost more in lost sales than any individual removal fee. Check Seller Central for the current IPI threshold and your live score, since Amazon adjusts these values over time.

Reason Code	Amazon Auto-Relists?	Resolution Path	Urgency Level
Listing closed	Yes	Automatic or one-click relist	Low - monitor for recurrence
Pricing violation (too high or too low)	No	Adjust price within bounds, relist manually	High - clock running
Missing or expired compliance document	No	Upload current document in Seller Central	High - can affect full ASIN position
FNSKU mismatch or wrong barcode received	No	Seller Support case, possible reprocessing	High - queue cannot fix it
Category or product restriction	No	Ungating or category approval process	Medium - may require documentation
Shipment plan unit-count mismatch	No	Seller Support case to reconcile discrepancy	Medium - often hidden in receiving

Listing-Side Reason Codes: The Six Causes You Will See Most Often

• Closed listing: The listing was deactivated - manually or after a period of inactivity. This is the least dangerous stranding event because Amazon will often auto-relist it, and the manual fix is straightforward.
• Pricing violation: Amazon flagged the offer price as too far above or below comparable catalog offers. The listing suppresses immediately and any FBA units behind it strand. Correcting the price and relisting resolves it, but the trigger can fire again if pricing automation pushes outside bounds without a floor or ceiling guard.
• Compliance documentation: Listings that require safety data sheets, product certificates, or test reports are suppressed if the document is missing, expired, or in the wrong format. Amazon requires specific formats - a 12-section safety data sheet submitted instead of the required GHS 16-section SDS will not satisfy the requirement even though it covers similar information. The entire FBA position on that ASIN strands until the correct document is accepted.
• Category or product restriction: Products in restricted categories, or products Amazon has reclassified into a restricted category after listing, require an approval that may not be in place. The listing suppresses and units strand.
• ASIN catalog merge: Amazon periodically consolidates duplicate ASINs. If your offer sat on one version and it gets merged into a different parent structure, units can land in a stranded state while the catalog update completes.
• Product reclassification: When Amazon changes the product type or hazmat classification of an item, listings that were compliant can become non-compliant without any seller action. This is difficult to detect unless you monitor listing health reports on a set schedule.

Prep-Side and Inbound Causes: How Units Strand Before They Ever Go Live

This category is nearly absent from competing guides but accounts for a significant portion of stranded inventory - particularly the cases that are hardest to resolve quickly, because they do not always surface in the Fix Stranded Inventory queue.

FNSKU Errors and the End of Amazon Prep Services

Starting in January 2026, Amazon ended all FBA prep and labeling services in the United States. Units arriving at a fulfillment center without correct prep or with mislabeled barcodes are returned to the seller at the seller's expense rather than corrected on-site. Prep accuracy is now a hard requirement at the point of origin.

The specific risk is a unit carrying the wrong FNSKU - even a single-digit error - being received under a different ASIN. It may be received under another seller's listing on the same catalog or under a wrong variation of your own product. In either case, the unit shows up stranded under an incorrect listing with no automatic fix. Recovery requires a Seller Support case and can take weeks while storage fees accumulate.

The March 2026 Commingling Change

Effective March 2026, Amazon eliminated commingling for all non-Brand Registry resellers. Any seller not enrolled in Brand Registry must now apply FNSKU barcodes to every unit. Units arriving with only a manufacturer UPC after that date can be received under the wrong ASIN and strand immediately. Resellers who previously relied on commingling and have not updated their prep workflow are generating stranded inventory with every shipment until the process is corrected.

Shipment Plan Mismatches

When the physical unit count in a carton differs from what was declared in the shipment plan, Amazon's receiving system flags the discrepancy. Those units often land in an unfulfillable status rather than appearing in the Fix Stranded Inventory queue at all. Resolution requires a Seller Support case to force a receiving reconciliation - a process that can take days to weeks. During that time the storage clock runs, and the IPI impact begins immediately.

How to Work the Fix Stranded Inventory Queue in Seller Central

The Fix Stranded Inventory tool is located in Seller Central under Inventory, then Manage FBA Inventory, then Stranded Inventory. Each row shows the ASIN, reason code, recommended action, and the date the clock started. Work through the queue in this order:

1. Open the Fix Stranded Inventory page and sort by earliest removal deadline. Units closest to the deadline go first.
2. Read the reason code before clicking anything. Relisting an ASIN with an unresolved compliance problem will strand again immediately after relist.
3. For reason codes where a one-click relist is offered and the root cause is genuinely resolved, use it. Amazon reactivates the listing without additional input.
4. For reason codes requiring manual relist - pricing violations, compliance issues, restrictions - resolve the upstream problem first, then relist from the queue.
5. For large catalogs with many stranded ASINs, download the flat-file stranded inventory report, update the status column in bulk, and re-upload. This is the only practical approach when dozens of listings are affected at once.
6. For FNSKU or shipment plan mismatch cases, open a Seller Support case from the same session, reference the shipment ID, and document the discrepancy. These do not resolve through the queue.

The Four Scenarios Where Amazon Auto-Relists - and the Many Where It Does Not

Amazon will automatically relist a stranded unit in exactly four cases: listing closed, item discontinued, listing completed, and an FBA listing changed back from Merchant Fulfilled to FBA. Every other reason code requires seller action.Amazon Seller Central - Fix Stranded Inventory documentation

That list covers simple administrative resets. It does not cover pricing violations, compliance problems, category restrictions, FNSKU errors, or any prep-side cause. For every other stranding event, the unit stays stranded until you act or until the automatic removal trigger fires.

The Edit Automatic Action Settings button in the Fix Stranded Inventory dashboard is one of the least-used features in Seller Central. It lets you specify what Amazon should do at the end of the removal window for future stranding events - automatically relist or automatically remove. Leaving this unset means Amazon decides. For most sellers, automatic relist is the safer default for products with strong sell-through rates, because the unit returns to active status and may sell before any further action is needed. Set a preference that reflects your inventory economics; without one, you have no control over outcomes when you miss the monitoring window.

The 30-Day Removal Clock and What Happens When It Runs Out

The Fix Stranded Inventory queue shows the date each unit entered stranded status. Amazon sets a fixed deadline from that date - visible in the queue - after which it fires an automatic action. Amazon does not grant extensions and does not send an advance warning email. The deadline shown is the actual deadline.

If the automatic action is removal, units are pulled from inventory and prepared for return shipment. Starting in early 2026, Amazon changed removal and disposal billing from a single lump sum at order completion to a per-unit-as-processed model. Charges now appear in the account progressively as units are processed rather than as one line item when the order closes. The total cost is the same - check Amazon's current removal fee schedule for rates by weight class - but the timing of when charges hit the account changed.

Units returned via removal can be sent back to FBA as a new shipment, but they must be re-prepped and re-labeled. If the original stranding was caused by an FNSKU error, the returned units carry the wrong label. Sending them back without correcting the label will strand them again on receipt. Disposal is permanent: Amazon destroys the units, the inventory record closes, and there is no recovery option.

Preventing Stranded Inventory at the Prep Stage: A Shipment Readiness Checklist

Each item on this checklist stops a specific stranding cause before units leave the prep table.

• FNSKU scan verification: Scan every FNSKU label and confirm it matches the ASIN in the current shipment plan. Do not assume the label roll in the printer matches the SKU being worked. Verify the scan result, not just the print job.
• Manufacturer barcode coverage: Confirm every manufacturer barcode on the product and its packaging is fully covered by the FNSKU label. If the product has a barcode on both the front panel and the bottom, cover both. A partially covered barcode is a stranding risk at receiving.
• Shipment plan unit count reconciliation: Count units per carton before sealing. The count in Seller Central for each carton must match the physical count exactly. Flag any carton with a discrepancy and correct the plan before shipping.
• Compliance document expiration check: For any ASIN requiring documentation - safety data sheets, children's product certificates, GMP certificates - verify the document on file is current and in the correct format. An expired or incorrectly formatted document can trigger a listing suppression the day it is detected, stranding the full FBA position regardless of how well the units were prepped.
• Pricing bounds review: Before shipping a restocking order, confirm the current offer price falls within a range Amazon considers reasonable relative to the catalog. If a repricing tool has recently moved the price, verify it has not crossed into a range that will trigger suppression when new inventory arrives.
• FNSKU requirement check for non-Brand Registry resellers: Any seller not enrolled in Brand Registry shipping after spring 2026 must confirm every unit carries an FNSKU, not a manufacturer barcode. Units prepped under an old commingling workflow that still carry only a UPC must be relabeled before the shipment goes out.

Weekly Monitoring Routine That Catches Stranded Units Before the Clock Advances Past 7 Days

A weekly review on the same day each week is the minimum cadence to keep stranded units from quietly running down the clock while attention is elsewhere.

What to Check Each Week

• Open Fix Stranded Inventory and sort by earliest removal deadline. Any unit with a deadline inside the coming week needs same-day attention.
• Pull the downloadable Stranded Inventory Report from Seller Central's inventory reports section. The flat file includes ASINs, reason codes, quantities, and dates in a format you can sort in a spreadsheet - essential for operations teams managing large catalogs where the on-screen queue becomes unwieldy.
• Cross-reference new stranded ASINs against recent inbound shipments. If a stranding event appeared within days of a shipment being received, review that shipment's prep records for FNSKU or unit count errors before taking action in the queue.
• Check the Inventory Health dashboard for your current IPI score and stranded inventory rate. A rising stranded rate shows up here before it triggers a storage limit warning, giving lead time to clear units before the next quarterly IPI evaluation.
• Review any compliance documents with expiration dates in the coming 90 days. Listing suppression from an expired document happens without advance notice; renewing before expiration keeps the listing active and the FBA position sellable.

The prep-stage checklist and the weekly queue review address stranded inventory at both ends - prevention before units ship and rapid response after they arrive. A thorough prep process without monitoring leaves compliance-triggered strandings undetected for weeks. A rigorous monitoring routine without prep discipline means new stranded units arrive with every shipment.

Frequently Asked Questions

What is the difference between stranded inventory and unfulfillable inventory in FBA?

Stranded inventory has no active listing attached to it - the units are in the warehouse but Amazon has no offer to sell them against, usually because of a closed listing, pricing flag, or compliance problem. Unfulfillable inventory refers to units that are damaged, defective, or have failed a condition inspection. Both types incur storage fees; only stranded inventory has a realistic chance of quick recovery by fixing the underlying issue.

Can I recover units Amazon already removed automatically?

Yes - removed units can be sent back to FBA as a new shipment, but they must be re-prepped and re-labeled first. If the original stranding was caused by an FNSKU error, correcting the label before reshipping is critical; units sent back with the wrong label will strand again on receipt. Units that went to disposal cannot be recovered.

Why do some stranded units not appear in the Fix Stranded Inventory queue?

Units created by shipment plan unit-count mismatches often land in a receiving discrepancy or unfulfillable status that does not surface in the Fix Stranded Inventory queue at all. If your inventory reports show units in that status that are not appearing in the stranded queue, open a Seller Support case immediately and reference the shipment ID to start a receiving reconciliation.

How does stranded inventory affect my IPI score specifically?

The stranded inventory rate is one of four inputs Amazon uses to calculate IPI. It carries less weight than excess inventory percentage and sell-through rate, but a high stranded rate pulls down a score that may already be under pressure from slow-moving stock. IPI is evaluated quarterly, and sellers below Amazon's current threshold face storage limits that restrict how much inventory they can send in - a constraint that can hurt sales far more than any individual removal fee. Check Seller Central for the current threshold and your live score.

What happens if I never configure the Edit Automatic Action Settings in the stranded inventory dashboard?

Leaving that setting unconfigured means Amazon applies its own default when the removal window closes for any stranded unit you do not manually resolve. In practice that default leans toward disposal rather than relist. Setting an explicit preference - either automatic relist or automatic removal - overrides that default for all future stranding events and gives you predictable outcomes on units you miss during your monitoring window.

Does the 2026 commingling change affect sellers who are enrolled in Brand Registry?

Brand Registry members who already label every unit with an FNSKU saw no operational change from the March 2026 commingling policy update. The change specifically targets non-Brand Registry resellers who previously relied on manufacturer barcodes under commingling. If you are not enrolled in Brand Registry, verify your current prep workflow against Amazon's updated commingling policy for your account type before shipping your next inbound.