FBA Removal Fees: What They Cost and How to Decide If Removal Is Even the Right Call

What a removal order actually does

A removal order is a request you submit in Seller Central telling Amazon to take specific units out of FBA. You pick the SKU, the quantity, and what happens to it next: shipped back to an address you control, or disposed of. Amazon charges a per-unit fee for doing this work, separate from and on top of whatever storage or aged-inventory surcharges that SKU has already accrued.

People use the phrase FBA removal order fees and FBA removal fees to mean the same thing. It's one charge, billed per unit removed, and it shows up as its own line in your Amazon transaction detail.

What a removal order does not do is fix the reason the inventory is stuck. It moves stock out of the fulfillment network. Whether that's the right move depends on why the stock isn't selling in the first place — a question the removal order doesn't answer for you.

How the fee is calculated

Amazon's removal fee schedule is structured by size tier and weight band, and it's charged per unit, not per shipment. Two things drive the number: how big and heavy the unit is, and whether you chose return or disposal. Disposal is almost always the cheaper option per unit because Amazon doesn't have to pack and ship it anywhere — it just needs to be scrapped or donated.

Amazon updates this fee schedule periodically, and it varies by marketplace, so treat any specific dollar figure you see on a listicle with suspicion. Pull the current per-unit rate for your weight tier directly from the Removal Order fee page in Seller Central before you commit — don't plan around a number you read somewhere else.

The structural point that matters more than the exact rate: the fee is proportional to weight and size, not to what the item is worth. A $60 kitchen tool and a $6 phone case in the same weight band cost the same to remove. That asymmetry is why removal decisions should be made SKU by SKU on unit economics, not as a blanket policy.

A worked example

Say you've got 500 units of a slow SKU sitting in FBA, small and under a pound, so it's in a low weight tier. For the sake of showing the math — and you should swap in your own current rate from Seller Central, since Amazon revises this schedule — assume a disposal fee of $0.50/unit and a return fee of $0.80/unit.

Disposal: 500 × $0.50 = $250. Return: 500 × $0.80 = $400, and now you own 500 units of dead stock plus whatever it costs you to warehouse or resell them yourself. Meanwhile, that SKU may have been accruing an aged-inventory surcharge for months already — if that's added up to $400 over two quarters, that money is gone regardless of what you do next.

This is the pattern we see across the accounts we manage: the removal fee itself is almost never the expensive part of the decision. The sunk storage and surcharge cost that already happened is the part sellers miss when they're staring at the removal fee line and deciding it looks too high to act on.

Removal, disposal, or liquidation — how to pick

Removal isn't the only exit. Amazon also offers liquidation, where it buys the inventory from you at a wholesale rate instead of you paying to remove it. Liquidation usually recovers less per unit than selling it yourself, but it recovers something, and it doesn't cost you a per-unit fee to execute.

The decision usually comes down to three questions: will this SKU sell again at a normal velocity, is the aged-storage surcharge about to jump to the next tier, and is the unit worth more sitting in your own warehouse than it costs to remove and re-store it. If the answer to the first question is yes, removal-and-hold is often right. If no, disposal or liquidation, whichever nets more after fees, usually wins.

The mistake that costs more than the fee

The honest version of the common mistake: an auto-removal setting gets turned on during a cleanup — maybe to clear excess of a discontinued SKU — and then gets left on. Months later it fires on a SKU that's seasonal and about to come back into demand, and units get disposed of before anyone notices. We've seen this happen inside client accounts we run, including our own oversight lapses. The fix isn't a smarter automation rule. It's a human checking what automated settings are live before assuming last quarter's cleanup logic still applies.

The second common mistake is removing stock and then reordering it a few weeks later, eating an inbound placement and shipping cost that would have been cheaper than the removal fee plus the aged-inventory charge you were trying to avoid. Across the more than $500M in managed revenue we've managed across 100+ brands, this removal-versus-hold call is one of the most frequently mishandled decisions in an account — not because the fee is complicated, but because it gets made in isolation from the reorder plan.

When the fee looks wrong, or the removal didn't fix anything

If the removal fee itself looks off, check the weight and dimension classification Amazon has on file for that ASIN first. A dimensional-weight misclassification inflates removal fees, storage fees, and the standard fulfillment fee all at once — it's worth disputing at the classification level, not the removal-order level, because fixing it there fixes every downstream charge.

If you removed the inventory and the underlying problem is still there — the SKU keeps overstocking, or it keeps aging out before it sells — the removal order was never going to fix that. That's a reorder-timing and demand-forecasting problem, and no amount of removing stock changes the reorder point that put you there. If the real leak is that ad spend stopped moving the SKU rather than the warehouse holding too much of it, that's a question for the ad account, not inventory — that's Dr. PPC's territory, not this one.

Dr. Stock, the managed product from Fable 5 at Full Circle, works the inventory side of exactly this decision: when removal beats liquidation, whether a fee was billed correctly, and whether the reorder point that created the overstock has actually been fixed. It doesn't store or ship anything itself — that's a 3PL's job — and it doesn't replace an ERP or run your whole operation. It flags the leak, and a human still approves the purchasing decision either way. There's no published price; it's a call and a 30-day trial. Whether or not that's the right fit, the removal fee was never the part of this worth losing sleep over — the surcharge that already accrued before you noticed is.