Getting Inventory Out of FBA: Removals, Disposals, and Recalls

Two sellers get the same email from the same supplier: a production batch is bad, stop selling it. One files removal orders that afternoon, pays freight nobody wants to pay, and has the lot off Amazon property and taped off in a warehouse corner before the week ends. The other reads the email again, decides the supplier is covering itself, and waits to see whether a customer complains. A season later, one of them is selling that ASIN and arguing about a supplier credit. The other is writing a plan of action about units that were still in fulfillment centers when the first complaint landed.

What separates those two afternoons is the clock, and every trigger runs a different one. A stranded listing runs on a timer Amazon set for you. Aged stock runs on the next fee assessment date. A stop-sale runs on a window that was already closing while you read the notice. A supplier's bad batch runs on however long it takes the first customer to complain, which is why that one feels like no clock at all.

Reading the clock right is most of the job. The removal itself is a form.

What fired, and who is holding the clock

Unrelated problems end at the same button. Find yours in the first column.

What fired	What is actually broken	Who holds the clock	The move that closes it
Listing went dark, units still in the network	The listing, not the goods	Amazon, via the stranded required-removal setting	Rebuild the offer; remove only if the ASIN is unrecoverable
Stock aging past the surcharge line	Your buying, not the product	Amazon, via the monthly fee assessment	Discount it out, or submit the removal before the next assessment
Returns came back unsellable	Condition of individual units	Your automated settings, running even when nobody opens them	Choose the disposition on purpose, grade the units off site
Closing the account or leaving a marketplace	Nothing; you are exiting	Amazon, via the closure and claims sequence	Zero the FBA balance before touching the close button
Supplier says a batch is bad	Traceability	You, until the first customer complaint	Stop the flow, pull the lot, isolate it, decide its fate
Amazon posts a stop-sale or safety alert	Compliance	Amazon, with a hard window and your ASIN as collateral	Remove everything affected, document it, then ask for reinstatement

The exits, and the one that may have been switched on for you

Before the triggers, the menu. The wrong door costs more than the wrong fee tier.

• Return. Amazon ships the units to an address you control. You get the goods back and decide what they are worth.
• Disposal. Amazon destroys them. Nothing comes back, nothing gets reviewed, and it cannot be reversed once processing starts.
• Donations. Eligible units go to charitable partners, and in the US and Canada this door is no longer optional.

Liquidation and Grade and Resell sit on the same menu, neither ships you anything, and since Amazon began enrolling unconfigured accounts into liquidation one of them may already be running on yours. What either door gives back per unit sits with the rest of the returns math (sorting FBA returns).

The listing went dark and the units are stranded

Stranded means the goods are fine and the offer is not. Amazon still holds the units and still bills storage on them, and nobody can buy them because nothing connects the FBA record to a live listing. This is the trigger most often answered with the wrong tool. The usual causes are boring and fixable:

• The ASIN got suppressed for a missing compliance document or a policy flag
• The ASIN was merged, reclassified or pulled from the catalog
• The listing SKU stopped matching the FBA record, or the listing was deleted outright, usually after a bulk flat file upload
• A switch between merchant fulfilled and FBA left the offer half built
• Brand Registry gating misfired and locked out your own offer

The clock belongs to Amazon here. The stranded inventory page carries its own required-removal setting, with a recommended window and a maximum number of days you may leave the problem alone. Let it run out and the units get removed or disposed of for you.

Work the Fix Stranded Inventory tool first, then the flat file, then a support case if the block is a suppression. The removal button makes sense only once the ASIN is dead, and then you are choosing between selling the goods elsewhere and paying to destroy them.

The stock got old while you waited for it to sell

This one sends no notification. It shows up on the invoice.

In 2026 Amazon pulled the aged inventory surcharge threshold earlier than it used to sit and added steeper bands for the stock that has been sitting longest. Whether a given SKU is worth keeping, discounting or pulling gets settled with the storage bill open, in your monthly inventory review. What belongs here is what the removal itself does to the math.

• Surcharges are assessed on a schedule, and what counts is that the removal order exists before the next assessment, not that the units have left the building
• Disposal is not automatically the cheap exit. Amazon prices return and disposal off the same size and weight card, and once the per-unit rework rate on our price list sits next to what the unit still resells for, plenty of SKUs are worth getting back
• Removal and disposal fees are now charged per unit as each unit is processed rather than once at the end, so a large removal lands in Payments as a drip of small lines instead of one entry a bookkeeper can match
• Thresholds and disposition eligibility move around. The FBA fee schedule in Seller Central is the version that counts on the day you file, and the current threshold belongs on the SKU record rather than in your head

Unfulfillable units are piling up and a setting you never opened is deciding

Unfulfillable is a different word from stranded, and mixing them up gets expensive. These units are individually damaged, opened, expired or otherwise unsellable as new. They pile up quietly as returns get graded, and sit in the inventory report as a number nobody reads.

The part that catches people: with automated unfulfillable settings left unconfigured, Amazon's help text says the items will be disposed of at its discretion based on capacity. No confirmation email asks if you meant it. The other classic failure is a setting pointed at an address you moved out of, paired with a disposal fallback. That is how sellers destroy inventory they meant to keep.

Open these settings this week and read what they are set to:

• Automated unfulfillable removals. Set the disposition deliberately, and verify the return address is one that is actually staffed today
• Automated removals for aged stock. Useful with a real policy behind it, dangerous when it runs on a default someone set during onboarding
• Stranded inventory required removals. The timer from the stranded section lives here, and it quietly overrides your intentions

If unfulfillable volume is steady rather than occasional, the answer is not a better setting. It is a standing return address at a facility that opens the boxes and grades every unit, because much of what Amazon calls unfulfillable is repackable rather than dead, and no default can tell the difference.

You are winding the account down

Rarer, and unforgiving about order of operations. Amazon expects the FBA balance at zero before an account closes, and closure is permanent.

• Turn off inbound first, including any replenishment automation still firing
• Sell down what clears at a price you will accept, then remove the rest
• File removals while the account is fully functional, not after a downgrade limits what you can submit
• Let the claims window after your last sale run out before closing, since refunds still land
• If there is any chance you come back, downgrade instead

Sellers who close first and think about the pallets second end up asking support for access to their own goods.

Your supplier tells you a batch is bad

A recall is a removal event before it is anything else. Refunds are the visible part. Getting the physical units out of circulation decides whether this ends as an expense or an account problem.

1. Stop the flow. Offer inactive in every marketplace, any inbound shipment killed if it can still be killed, supplier told to stop shipping that lot.
2. Identify the lot. This is where most sellers learn they cannot tell which FBA units came from which production run, so the recall expands to every unit of the ASIN.
3. Pull it out. Removal orders on every affected FNSKU, in every marketplace holding the goods, pointed at a facility that can store them separately.
4. Isolate on arrival. Quarantined stock gets its own labeled area and never touches sellable stock. A recalled unit rebagged and sent back into FBA is a far worse day than the recall itself.
5. Decide the fate and keep the paper. Rework and recertify, return against a supplier credit, or destroy with a receipt. Every step gets a date and a document, because the credit claim and the Amazon case both run on that trail.

Destruction is not always a dumpster. Batteries, aerosols and anything else carrying a hazard class have their own disposal route, and the class comes off the safety data sheet your supplier is supposed to hand you. Know your catalog's classifications before the day a lot has to go.

Amazon posts a stop-sale or a safety alert

The physical work is the same as a supplier recall. The pressure is not, because the clock is not yours. Amazon's recall and product safety pages tell sellers to request removal of all affected inventory within a set window, and ASIN reinstatement is conditional on that inventory being gone plus a requested document, usually a compliance letter or test report. Amazon says plainly it may refuse reinstatement and may act against the account.

Federal consumer product safety rules are blunter still, and they rule out quietly moving the units into a merchant fulfilled listing or a wholesale lot.

Order of operations when the notice lands:

• Removal orders for every affected FNSKU in every marketplace, filed the same day, not after you finish arguing with the notice
• The same units in your warehouse, at your 3PL and in any open inbound shipment, pulled and quarantined
• A written record of what you removed, when, and where it went
• Only then the reinstatement case, with the requested document attached

What the order can and cannot reach

A removal order is filed against inventory in a particular state, not against a product you have in mind. Some units sit outside its reach on the day you file, and sellers usually find out by counting a short shipment weeks later.

• Removals are filed per marketplace. Units held in a marketplace you did not file in stay exactly where they are, which is how recalled stock survives a recall
• Units already reserved against an open customer order are not yours to pull yet. They release back, or they ship to a buyer
• Inventory in transfer between fulfillment centers is out of reach until it lands somewhere and gets counted in
• An inbound shipment that has not been received cannot be removed. Stop the shipment instead, and if it is too far along, plan to remove the units after they check in
• Quantities drift between filing and processing, in both directions, as returns land and reservations clear

File per FNSKU when more than one condition or label version is in the network, keep the removal order ID with your case notes, and expect one order to break into several shipments out of several buildings. The removal order detail and removal shipment detail reports tie those shipments back to what you filed. Pull them the day you file, not the day something turns up missing.

What actually lands on your dock

Whatever the trigger, the ending is one physical event, and it rarely matches what sellers picture:

• Mixed SKUs inside a single carton, in no order, from several fulfillment centers
• Packaging in every state: bags slit open, retail boxes crushed, seals broken, sticker residue and torn FNSKU labels on units that are otherwise perfect
• Several shipments over days or weeks, several tracking numbers, no delivery date to plan around
• Customer returns mixed in with units nobody ever opened
• A manifest that gives quantity by ASIN and says nothing about condition

That last gap is where value quietly disappears. Amazon tells you how many units it sent, not which are still sellable or which never arrived. Both answers exist only if somebody counts and grades on arrival. A good share of that grading turns out to be label work, and what a bad label does at the receiving dock is why that pass is worth doing carefully rather than quickly.

The first week after the pallet lands

1. Photograph cartons sealed, before anyone opens them, tracking label visible
2. Count against the manifest by ASIN, per shipment, and log the variance that week instead of waiting for the last carton
3. Split the arrival on the first pass: units that can go straight back into an inbound plan, and units whose condition has to be judged one at a time
4. Repackage before relabeling, so a new bag or box does not take the fresh label with it
5. Print new FNSKU labels from Seller Central, cover the old barcode fully, verify the scan; that is standard FNSKU labeling work
6. Build a new inbound plan and expect a different fulfillment center than the goods came from
7. Give the second pile a deadline, because units nobody has judged turn into a shelf that sits untouched for a year

The first pile is the easy half. Judging the second runs the same way as judging a customer return, and the difference is volume: a removal drops the whole pile on you in one week.

The counting deadline is real. Amazon's inventory reimbursement policy puts both a floor and a ceiling on when you may claim for removal units that never arrived, counted from the shipment date, and that window tightened in recent years. Miss the ceiling and the units are gone whether or not they were ever loaded. That is the argument for receiving removals somewhere that opens boxes on arrival, which is the point of our removal order handling.

The traceability you should have set up last quarter

Every recall answer above depends on being able to say which units came from which production batch. Nobody builds that during a recall. It has to exist at receiving, months earlier, where it costs almost nothing to capture.

• Record the lot or batch code at receiving, per carton, before anything gets labeled or bagged
• Tie that lot to the outbound FBA shipment ID, so a bad batch maps to specific shipments instead of the whole ASIN
• For dated goods, capture the expiration date in the same pass, printed the way the FBA packaging and prep requirements ask for it
• Keep the supplier and PO reference on the same record, because the credit conversation starts there

Without that chain, a supplier recall means pulling every unit of the ASIN out of the network, good ones included. With it, you pull one shipment and keep selling the rest.

Timing and paperwork

My listing is stranded. Should I just remove the units?

Not first. Stranded units are usually in perfect condition; the offer is what broke. Removing them means paying to extract good inventory and paying again to send it back. Fix the offer, and reach for removal only when the ASIN cannot be revived. Watch the required-removal timer while you work, because it keeps counting down while a support case sits open.

Can I send a removal order to a prep center instead of my home address?

Yes. The return address is just an address, and a facility with a dock beats a residential driveway when goods arrive as several shipments over weeks. It also puts the count against the manifest inside the claim window instead of after it.

Can I resell units that came back from a recall or stop-sale?

Not in the condition they came back. Federal consumer product safety rules prohibit selling, offering for sale or distributing a recalled product, and that covers merchant fulfilled listings, other marketplaces and wholesale lots. What is left is supplier return, rework and recertification where the defect can be corrected, or documented destruction.

How long does a removal take to reach me?

Longer than the estimate on screen, and unevenly. Disposals tend to clear faster than returns, and returns can stretch past the quoted window before the last carton shows up. Never schedule a relaunch on the assumption everything lands at once, and log each shipment as it arrives rather than waiting for the last one, since the reimbursement window runs from the shipment date and not from the day you finish counting.