Requesting an Amazon FBA removal order: when to pull stock back or have it destroyed

Every unit you do not sell within a few months costs you money you will never see again, and most sellers I talk to wait too long with their removal order.

Short answer. You request a removal order through Manage Inventory in Seller Central: select the SKUs, choose Actions and then Create Removal Order, with return or disposal as the option. The real question is not how, but when: a removal or disposal pays off as soon as the storage costs plus the aged-inventory surcharge exceed the residual value of the unit. That is a calculation per SKU.

What a removal order is and how you request it

A removal order is the instruction to Amazon to pull inventory out of the fulfillment center. You have two flavors: a return (back to an address in the same country) or a disposal (Amazon destroys the inventory). You find it through Manage Inventory, you select the listings, and under Actions you choose Create Removal Order. Note that you cannot have inventory returned cross-border: inventory in a German center only goes to a German address.

The steps are trivial. The decision is not. See also the official explanation in Seller Central.

The three situations in which you pull stock out

There are roughly three triggers, and each one calls for a different answer.

Stranded inventory. A listing gets blocked (suppressed, a compliance issue, an ASIN merge that went wrong) and the inventory sits there but is unsellable. Amazon gives you a limited window to fix it before the inventory has to come out. Here the first reflex is not removal but fixing the listing. Only when that fails is removal the way out.

Aged inventory just before a higher tier. This is the most painful one, because it is predictable and yet people miss it. Since the tightening, the aged-inventory surcharge already starts at 181 days, no longer at 271. Units of 181 to 270 days get the first tier, and it climbs as the inventory gets older. Anyone who has a SKU on their radar on day 175 can still deploy a removal or an aggressive markdown before the next tier kicks in.

Slow-movers that keep costing storage. No acute trigger, just dead weight. Monthly storage plus the climbing surcharge eats into your margin until the unit costs more than it brings in.

The calculation: storage costs versus residual value

This is the core, and it is a decision per SKU. On one side is what the unit keeps costing you if it stays in FBA: monthly storage, the aged-inventory surcharge that climbs per tier, and the capital that is tied up. On the other side is the residual value: what can you still get for the unit through outlet, through your own channel, or if you repurpose it? From that you subtract the removal or disposal costs.

The fees themselves shifted as of March 1, 2026 to a per-unit charge at the moment of removal or disposal, and for the lightest standard sizes they have actually been lowered to encourage faster turnover. Exact amounts differ per marketplace and size, so you pull those from your own rate card; I deliberately name no fixed figures here.

The rule of thumb I follow: keep in FBA what you realistically sell in the coming one to two months, and pull everything above that out before the next tier hits. Disposal is cheaper than return, so if the residual value of the unit is lower than the return plus inbound costs to sell it again, you destroy it.

Automated removals: do not let Amazon surprise you

Amazon can start removals itself through automated unfulfillable removal settings and the aged-inventory settings. That is handy, but it also means Amazon decides on its moment and its terms, not on yours. I set those settings deliberately and check per SKU category whether automatic or manual is smarter. For a long-tail with low residual value, automatic is fine; for your A-SKUs you want to keep control.

What you do with returned inventory

A return only makes sense if there is a second life. Three routes that work: Amazon Outlet or a liquidation route to clear it within the platform, your own webshop or bol as a more margin-friendly channel, and reuse (rebundling, as part of a set, or as a sample). What you do not want is to pull inventory back to your warehouse where it gathers dust again at your own storage costs.

Why this calls for a system, not a quarterly spreadsheet session

The problem is not that the calculation is hard. It is that it holds per SKU, shifts every day, and plays out across your whole catalog at once. A seller with hundreds of SKUs who reviews this manually in an export simply does not see the day-175 moments coming.

I have sold on Amazon myself and I know the feeling of a surcharge line that surprises you on your settlement. First I look at whether the process can be simpler: which triggers do you really want to monitor, and which SKU segments deserve manual attention. After that I build the solution where the standard tools fall short: an integration on the SP-API that brings together, per SKU, the inventory age, the storage costs, the next surcharge tier, and your COGS, and gives you a worklist of what has to come out before the tier flips. Removal versus disposal versus markdown, calculated, not by feel. That is the moat: not a dashboard that shows data, but a workflow that calculates the decision on your own figures.