What is Amazon FBA stranded inventory?

Stranded inventory is FBA stock that Amazon cannot fulfill from for a non-quantity reason — the listing is suppressed, the offer is removed, the unit is FEFO-blocked, or a pricing rule has gone wrong. The unit is physically in the warehouse but unavailable for sale until the seller fixes the underlying issue or files a Removal Order. Amazon surfaces the report in Seller Central under FBA Reports → Fix Stranded Inventory.

How does expiration-dated inventory show up as stranded?

Two paths. First, units past the Unsellable by Date FEFO-block — they appear on the stranded report because Amazon cannot fulfill them. Second, listings can be auto-suppressed when buyer complaints about freshness or expiration trigger Amazon's listing review. The first is mechanical (the date passed); the second is a policy reaction. Both surface in the same stranded queue.

How does a seller fix expiration-stranded inventory?

For FEFO-blocked units, "fixing" the strand usually means filing a Disposal Request. The units are not coming back to a sellable state — the date has passed. For listing-suppression strands tied to a freshness complaint, the seller responds to the suppression notice in Account Health and resolves the underlying issue (commonly an expiration-date discrepancy that caused a buyer to receive a unit closer to expiration than they expected).

Do stranded expiration-dated units cost the seller storage?

Yes. Stranded does not mean removed from the warehouse — the units are still in FBA accruing monthly storage and long-term storage fees. Every day a stranded unit sits, the carrying cost grows. The fastest way to stop the bleed for expired units is a Disposal Request; the fastest way for a suppression-stranded ASIN is to resolve the suppression cause.

Can a seller prevent expiration-related stranding?

Mostly yes. Sequencing MSKUs by FEFO, applying FEFO pricing on the soonest-expiring batch, and filing scheduled Disposal Requests on the Unsellable by Date together prevent the most common path — units passing the Unsellable by Date in FBA with no plan. The harder path to prevent is listing suppression from a single buyer complaint, which can fire even on a well-managed ASIN.

Does Amazon's "Auto-fix stranded inventory" setting handle expiration-stranded units?

Amazon's auto-fix relists units where Amazon judges the strand is recoverable (e.g. a temporarily out-of-policy listing). It does not relist units that are FEFO-blocked or units past Unsellable by Date — those cannot be relisted by any setting because the underlying reason is the date. For expiration-stranded units the only paths are sell-through (impossible past Unsellable by Date) or removal.

Amazon FBA Stranded Inventory + Expiration

Short version

Stranded FBA inventory is stock Amazon cannot fulfill from for a non-quantity reason — usually a suppressed listing, a removed offer, or a unit past the Unsellable by Date. Expiration-dated units appear in the stranded report in two ways: as FEFO-blocked units that have aged past Unsellable by Date, and as units stranded by a listing suppression tied to a buyer complaint about freshness. Both consume storage fees until cleared; the response for FEFO-blocked units is a Disposal Request, and the response for suppression-stranded units is fixing the underlying suppression cause.

What stranded inventory is

Amazon's stranded inventory report — FBA Reports → Fix Stranded Inventory — flags every unit in FBA that cannot be fulfilled for a non-quantity reason. The most common categories:

Listing suppressed. Amazon removed the offer for compliance, policy, or freshness reasons.
Offer removed. The seller intentionally removed the listing but did not file a Removal Order on the existing FBA inventory.
FEFO-blocked. Units past the Unsellable by Date.
Pricing rule conflict. A pricing automation rule rejected the offer.
Missing image or detail. The listing is incomplete.

Where stranded inventory overlaps expiration-dated inventory

For expiration-dated categories two of those buckets matter most:

FEFO-blocked units. Mechanical — the Unsellable by Date passed. Amazon cannot ship the unit. The only paths off the stranded list are Disposal Request or Return Order.
Listing-suppression strands triggered by freshness or expiration complaints. Policy-driven — a buyer received a unit closer to expiration than they expected and complained. Amazon flagged the listing. The whole ASIN may strand until the seller resolves the suppression.

The two overlap when a unit FEFO-blocks AND a suppression is open on the same ASIN — usually the result of a missed Unsellable by Date that produced a complaint before the seller could file a Disposal Request.

Why expiration-dated units strand

No scheduled Disposal Request on the Unsellable by Date. Units age past Unsellable by Date in FBA with no removal plan.
Date discrepancy at receiving. Amazon recorded an earlier expiration than the actual batch warranted. Units strand at a date the seller did not expect. See the discrepancy section of Amazon FBA expiration date management.
Listing suppression after a buyer complaint. One buyer receives a near-expiration unit and complains. Amazon may suppress the ASIN.
Subscribe & Save mis-rotation. The active Subscribe & Save MSKU ran out and the predecessor strand was triggered while a successor migration was in progress. See Subscribe and Save expiration risk.

A working example

A baby-food seller has MSKU BAB-B0BAB1-2026-02in FBA — 240 units remaining, Unsellable by Date January 19 2026. The seller does not file a scheduled Disposal Request. On January 19 the units FEFO-block. The stranded report shows 240 units with reason “Unsellable”. The seller pays storage on the case-pack volume for the next 22 days before noticing the strand entry. Eventually the seller files an ad-hoc Disposal Request; Amazon processes it in ~10 business days. Total carrying cost from FEFO-block to physical disposal: roughly 32 days of storage.

With a scheduled Disposal Request, the same 240 units would have submitted on January 19. The Disposal Request would have processed in the same ~10 business days, but starting from FEFO-block day rather than 22 days later. Net carrying-cost difference: ~22 days of storage on 240 units. For a category with $0.0145/cubic-inch-month storage and a case-pack volume of ~3.4 cubic feet, the saved storage is ~$50. The avoided downside compounds across an account with hundreds of MSKUs.

The seller response per stranded category

Stranded reason	Operator response
FEFO-blocked (past Unsellable by Date)	File a Disposal Request immediately. Sell-through is no longer an option.
Listing suppressed for freshness complaint	Respond to the Account Health notice. Address the underlying cause (often a date discrepancy). Once the suppression clears, the still-sellable units relist.
Offer removed (seller intent)	Either relist the offer or file a Removal Order on the existing inventory.
Missing image or detail	Fix the listing detail page; the strand clears once Amazon re-validates.
Pricing rule conflict	Audit the pricing automation. Common cause: a min-price rule that rejects the current offer.

How Shelfdoc helps prevent and clear expiration strands

Scheduled Disposal Requests fire on the Unsellable by Date the seller picked. The most common path to a FEFO-block strand — units passing their cutoff with no plan — is prevented at the schedule layer.
Daily reconciliation against Amazon's inbound record surfaces date discrepancies before they trigger a FEFO block. The Discrepancies tab is where the seller resolves them.
When a strand happens anyway, the FEFO-blocked MSKU appears on the Removal Orders queue with a one-click Disposal Request action. The submission still goes through SP-API; Amazon decides processing.
The audit trail records the strand event, the Disposal Request submission, and Amazon's status transitions — the evidence chain a Seller Support reimbursement case usually needs.

What Shelfdoc does not do

Shelfdoc does not respond to listing-suppression notices or write Account Health appeals. Those are the seller's words, written in Seller Central.
Shelfdoc does not relist a suppressed ASIN or restore an offer Amazon removed.
Shelfdoc does not touch Amazon's “Auto-fix stranded inventory” setting. That toggle lives in Seller Central and the seller controls it directly.

Amazon FBA expired inventory — the upstream cause for most expiration strands.
Amazon FBA Removal Order expiration — the action that resolves FEFO-blocked strands.
Amazon FBA Unsellable by Date — the date that determines when units FEFO-block.
Amazon FBA expiration date management — the full lifecycle.
Resources hub — every guide, glossary entry, calculator, and decision framework, organized by topic.

Frequently asked questions

What is Amazon FBA stranded inventory?: Stranded inventory is FBA stock that Amazon cannot fulfill from for a non-quantity reason — the listing is suppressed, the offer is removed, the unit is FEFO-blocked, or a pricing rule has gone wrong. The unit is physically in the warehouse but unavailable for sale until the seller fixes the underlying issue or files a Removal Order. Amazon surfaces the report in Seller Central under FBA Reports → Fix Stranded Inventory.
How does expiration-dated inventory show up as stranded?: Two paths. First, units past the Unsellable by Date FEFO-block — they appear on the stranded report because Amazon cannot fulfill them. Second, listings can be auto-suppressed when buyer complaints about freshness or expiration trigger Amazon's listing review. The first is mechanical (the date passed); the second is a policy reaction. Both surface in the same stranded queue.
How does a seller fix expiration-stranded inventory?: For FEFO-blocked units, "fixing" the strand usually means filing a Disposal Request. The units are not coming back to a sellable state — the date has passed. For listing-suppression strands tied to a freshness complaint, the seller responds to the suppression notice in Account Health and resolves the underlying issue (commonly an expiration-date discrepancy that caused a buyer to receive a unit closer to expiration than they expected).
Do stranded expiration-dated units cost the seller storage?: Yes. Stranded does not mean removed from the warehouse — the units are still in FBA accruing monthly storage and long-term storage fees. Every day a stranded unit sits, the carrying cost grows. The fastest way to stop the bleed for expired units is a Disposal Request; the fastest way for a suppression-stranded ASIN is to resolve the suppression cause.
Can a seller prevent expiration-related stranding?: Mostly yes. Sequencing MSKUs by FEFO, applying FEFO pricing on the soonest-expiring batch, and filing scheduled Disposal Requests on the Unsellable by Date together prevent the most common path — units passing the Unsellable by Date in FBA with no plan. The harder path to prevent is listing suppression from a single buyer complaint, which can fire even on a well-managed ASIN.
Does Amazon's "Auto-fix stranded inventory" setting handle expiration-stranded units?: Amazon's auto-fix relists units where Amazon judges the strand is recoverable (e.g. a temporarily out-of-policy listing). It does not relist units that are FEFO-blocked or units past Unsellable by Date — those cannot be relisted by any setting because the underlying reason is the date. For expiration-stranded units the only paths are sell-through (impossible past Unsellable by Date) or removal.

Stop letting expiration-dated stock strand in FBA

Scheduled Disposal Requests on the Unsellable by Date, daily reconciliation against Amazon's inbound record, and a timestamped audit trail for every action.

Create account