Amazon Stranded Inventory - The Fix Workflow 2026

Stranded inventory is FBA stock that cannot be sold because the listing is broken, deleted, blocked, or suppressed. The units keep accruing storage fees the whole time. On a mid-sized catalog, the aggregate cost typically shows up as a slow bleed inside the P&L that nobody attributes to a specific event. This guide covers what causes strands in 2026, how to fix them in priority order, and how to catch new ones before the next storage cycle.

What stranded actually means

Amazon marks inventory as "stranded" when units are physically in an FBA fulfillment center but no active listing points at them. The units keep accruing monthly storage fees, they are exposed to long-term storage surcharges once they cross 271 days, and they cannot generate revenue. Amazon documents the state and its causes in the Fix stranded inventory help article.

Fee math for US standard-size units: $0.87 per cubic foot per month January through September, $2.40 per cubic foot per month October through December. On a small-standard SKU (roughly 0.15 cubic feet packed) with 500 stranded units, that is $65/month in peak season plus long-term storage exposure after nine months. On a large-catalog brand, unaddressed strands run into thousands of dollars per month.

The four triggers that cause almost every strand in 2026

1. Unresolved suppression. A listing was suppressed for content or image compliance, the seller never republished, and the FBA units are now behind a dead listing. This is the single most common cause, covered in the suppression playbook.
2. Deleted or merged parent variation. A catalog cleanup deleted the child SKU or merged variations; the units at FBA still reference the old SKU that no longer resolves.
3. Compliance block. GPSR data missing for EU marketplaces, HAZMAT information missing, or a category-specific compliance flag that took the listing offline.
4. Accidental SKU closure. A bulk operations file with an unintended "Delete" or "Close" instruction. Common enough that Amazon's own Avoid stranded inventory article opens with it.

The fix workflow, in priority order

1. Export the Stranded Inventory report from Manage FBA Inventory.
2. Join it against unit cost to compute exposure per line: units × unit cost = capital tied up. Add a second column for units × monthly storage per unit = fee bleed per month.
3. Sort descending by exposure. Work the top 10 percent of lines first; the Pareto is extreme on stranded reports.
4. For each top-exposure line, choose one action: relist (fix the listing status and republish), file a removal order (dispose or return-to-vendor), or match the units to an existing live ASIN if the strand was caused by SKU deletion.
5. Set a 30-day re-check. Strands recur when the underlying trigger is not fixed at the source (catalog QA, GPSR data pipeline, ops process).

How Nova detects strands before the storage cycle

The design intent of Listing Health is to surface the state change on the day it happens, joined against the trailing P&L exposure so the operator sorts the queue by dollars, not by SKU. On a fresh catalog upload that accidentally strands 40 SKUs, the alert lands the same day and the decision (relist vs. remove) happens before the next monthly storage invoice.

Prevention: what actually reduces strand rate

• Catalog QA before every bulk upload. Reject files that close or delete SKUs with active FBA inventory unless flagged intentionally.
• Same-day suppression alerting. Unresolved suppressions are the number-one strand cause; catching them fast prevents the downstream strand.
• GPSR data pipeline that maintains manufacturer contact info per EU marketplace, so a compliance sweep does not strand units in DE, FR, IT, ES.
• Quarterly SKU-lifecycle review. SKUs at end-of-life should be planned into removal, not orphaned.