Seller guide
How do I recover FBA stranded inventory before auto-removal?
Turn a current Stranded Inventory export into a deadline-first review queue, separate listing and inventory symptoms, and verify each proposed action in Seller Central before units reach a supplied auto-removal date.
Export the current rows and preserve Amazon's wording
Start with a fresh seller-normalized Stranded Inventory export. Keep the seller reference, SKU, ASIN or FNSKU, stranded reason, error message, Amazon-supplied primary action, stranded date, auto-removal date, unit counts, and current listing price together. Do not rewrite a reason into your own category before triage: two rows that sound similar may point to different live listing or inventory states. The export is a work queue, not proof that a proposed action is still available.
Sort by the supplied deadline before estimated value
Rank passed auto-removal dates first, then dates inside seven days, thirty days, later dates, and rows with no date. Within each band, sort by total stranded units and use listed value only as a secondary planning signal. Price multiplied by units is not recoverable value, profit, or a promised reimbursement. A low-priced row near a deadline can deserve attention before a higher-value row with time remaining.
Separate listing fixes from inventory disposition
Review the supplied reason and primary action beside the live record. A closed or incomplete listing, missing offer, policy issue, or stranded variation may require catalog work; unfulfillable units or an expiring disposition window may require a different inventory decision. Never create a listing, change a price, relist an offer, or request removal from the spreadsheet alone. Confirm the current state and available action in Seller Central for every affected identifier.
Work one verified action ledger
Record the current status, chosen action, owner, verification time, and result beside each seller reference. After a human completes an action, refresh the report rather than assuming the row cleared. Keep unresolved errors, unavailable actions, and conflicting identifiers visible for support review. This prevents the same units from being worked twice and makes a missing result obvious before the next deadline review.
Use recurrence as a process signal
Group the queue by supplied reason and primary action after urgent rows are handled. Repeated listing-closure, offer, identifier, or inventory-state patterns can reveal where a launch or catalog checklist needs a new review step. The group is evidence of recurrence in the supplied batch, not a root-cause diagnosis; verify the underlying records before changing a standard operating procedure.
Tools that help with this
- FBA Stranded Inventory Recovery Queue ($0.50) — Rank supplied stranded rows by auto-removal urgency, units, reason, and action
- Four-Marketplace Catalog Readiness Check ($0.05) — Review required catalog fields when the live issue points to listing data
- FBA Reimbursement Deadline + Evidence Tracker ($1.00) — Track a separate evidence and deadline ledger for eligible inventory events
Every paid output is a draft for your review before you publish, appeal, or activate anything. Friday does not access your seller account.