Appearance

FBA Removals Tracking: How to Stop Losing Money ​

Posted 2026-05-17

A refurbisher friend pulled his last 90 days of FBA Removal Orders on a Sunday night last spring. He'd never reconciled them. Thought removals were noise — pennies on the dollar.

He found $7,840 in unreimbursed warehouse-damaged units, $2,300 of resellable phones Amazon had marked unfulfillable that were fine on inspection, and $1,200 of long-term storage fees he could have avoided by removing slow movers two months earlier. Twelve thousand dollars he'd written off as "the cost of doing business on Amazon." It wasn't. It was the cost of not tracking removals.

If you're doing $200K+/year on Amazon FBA, you're probably leaving $3,000-$10,000 a year on the table in removals you never reconcile. This post walks through the fee math, the four types of FBA Removal Order, and what real tracking looks like.

The trap: removals look like noise, but they're a leak ​

FBA Removal Orders are what happens when inventory leaves Amazon's warehouse without selling. Customer returns Amazon couldn't restock. Units the receiving team damaged on intake. Listings you took down with stranded stock. Slow movers you pulled before the storage clock hit. None of it gets tracked the way a normal sale does.

Most sellers ignore removals because the per-unit value looks low. A $4.50 removal fee on a $15 product feels not worth chasing. The math compounds fast:

  • 100 removals/month × $15 average COGS = $1,500/month in inventory in motion
  • 30% gets damaged, lost, or never reconciled = $450/month leaking
  • Annualized: $5,400/year gone, on a single product line

Now run that across an operation with 50-200 SKUs and 300-1,500 removals/month. You're looking at five-figure annual leaks that don't show up in any P&L because they're spread across a dozen line items in Seller Central none of your tools were watching.

The leak isn't the removal. The leak is that nobody connects the removal to the unit, the unit to the original cost, and the cost to whether Amazon owes you a reimbursement or whether the unit is sitting in a corner waiting to be re-graded.

The four types of FBA Removal Order (and the money in each) ​

Customer returns ​

Most common type. Customer ordered, returned it, Amazon couldn't restock it so they send it back. Default disposition: returned to your address.

The opportunity is condition. Amazon's grading is "sellable / unfulfillable" — binary, fast, wrong half the time. A returned phone marked "unfulfillable" because the box was opened is usually a fine A-grade unit you can re-list. A unit marked "sellable" can be cracked. You don't know until you open the box.

Sellers who re-grade on arrival recapture 40-70% of removed inventory at full or near-full margin. Sellers who don't, write it off.

Warehouse-damaged inventory ​

Amazon's own staff damages your stock during inbound or outbound handling. Forklift hit, mishandled box, water damage in a fulfillment center. These are reimbursement-eligible — Amazon owes you the wholesale value of the unit.

The catch: you have to file the claim, within the eligibility window, with proof of cost. Most sellers never file because they don't connect the damaged removal back to the original FNSKU and shipment ID. Your inventory tool says 12 units. Amazon sent back 10. The variance? Two were warehouse-damaged. Amazon reimburses if you ask. Most operators don't.

Average reimbursement recovery for sellers doing 500+ orders/month: $400-$1,500/month. An entire ShipStation subscription's worth of margin, sitting in Amazon's pocket because nobody filed.

Unfulfillable inventory ​

Your listing got suppressed, the account had an issue, or the product became unfulfillable for compliance reasons (CPSC, lithium-ion handling, expired). The inventory is stuck in FBA and the long-term storage clock is ticking.

Long-term storage surcharges kick in at 181 days for most categories — $0.78/cubic foot/month at the low end, $6.90/cubic foot/month after 365 days. On a pallet of phone cases that's nothing. On a pallet of full-size kitchen appliances, the surcharge can exceed unit cost within a year.

The play: pull a removal before the surcharge compounds. Most sellers find out a listing was suppressed two months later, by which point storage fees have eaten the margin.

Voluntary removals (strategic) ​

You pull slow movers proactively. Either the IPI score is dragging your storage allowance down, or you want to relist on Walmart / eBay / BackMarket at a better margin, or aged inventory surcharges are about to hit.

Voluntary removals get treated as "we chose this, no leak" — so almost nobody tracks the per-unit cost. You're paying $0.97-$2.30 per unit in removal fees plus return shipping. On 800 units, that's $776-$1,840 that should hit the unit's per-unit P&L, not vanish into "marketplace operating costs."

Why spreadsheets fail for removals ​

Removal tracking breaks spreadsheets fast.

Manual matching. Each removal has an order ID. To know what you got back, you have to match it to the original inbound shipment, the FNSKU, the original cost, and the specific units that left. At 50 removals/month across 30 SKUs you can keep up. At 300 removals across 100 SKUs, you can't.

No serial-level visibility. Refurbishers get crushed here. If you sent 12 units in, sold 10, and 2 came back — which two? The A-grade or the B-grade? The unit tested twice or the one that limped out the door? Without serial tracking, you have no cost basis on the returned unit, which means no real margin on this SKU.

Condition discrepancies. Amazon says "sellable," you open it and the screen is cracked. Amazon says "unfulfillable," you open it and the unit is mint. Your spreadsheet has one column for what Amazon told you and zero for what you found. Re-grading happens in someone's head, and the unit walks off the floor.

Scale. At 100+ removals/month, tracking removals is a 10-15 hour/week job for one person if done well. Most teams don't have a person. They have a half-attentive operations lead and a spreadsheet 18 months out of date.

What end-to-end removals tracking actually looks like ​

Real removals tracking has four pieces. Most operators have one or two. The leak is in the gaps.

1. Automatic removal-order import ​

Removal Orders pull in from Amazon's Manage Inventory data the same way orders and shipments do. Each tied to the original FNSKU, inbound shipment, and cost basis on the units that left. No manual matching. The system knows what came back the moment Amazon ships it.

2. Serial-level receiving + regrading ​

Returned units hit the dock. Someone scans the serial on arrival. The system knows: this is unit X, it left as A-grade, it came back from an FBA Removal Order tied to order Y, original cost $43.20. Inspector grades it — A, B, C, or parts — and the unit auto-routes to the correct bin. Grade lives on the unit, not in someone's head. See how regrading works in Rilk.

3. Reimbursement eligibility tracking ​

The system flags warehouse-damaged units, units lost in transit, and anything Amazon owes you for. Your operations lead gets a list of claims with FNSKU, shipment ID, and cost basis ready to submit. The first month most sellers run this report, they find $1,000-$5,000 of stuck reimbursements they never knew existed.

4. Per-unit P&L recovery ​

Once the returned unit re-sells (re-listed on Amazon, sent to Walmart at a different price point, or liquidated as parts), the system writes the recovery value back to the unit. True P&L = what you paid, minus what you originally sold it for, plus the removal fee, plus re-sale recovery, minus any service cost. Reality, not a spreadsheet estimate. More on per-unit reporting.

The metric this gives you is recovery rate — what percentage of removal value you recapture across re-sale, reimbursement, and liquidation. A serious refurbisher recovers 60-85%. A seller without tracking recovers 15-30%, because most of it walks off the floor.

How Rilk handles FBA removals end-to-end ​

We built this because we needed it. Running a multi-channel refurbishment operation, removals were the single biggest line of leaked margin we couldn't explain. So we built it in.

Removal Orders pull in from Amazon automatically. Each matches to the original shipment and product record. When units land on your dock, scanning the serial pulls up the unit history — what it cost, what condition it left as, why it came back. Receiving grades it, the system routes it to the right bin, status updates in real time.

Reimbursement-eligible units surface on a dashboard with claim data pre-filled — FNSKU, shipment ID, cost basis, eligibility window. You file the claim, the recovery gets written back when Amazon reimburses, the unit's P&L closes correctly.

Per-unit margin tracks the full lifecycle. Purchased → sold → returned → re-graded → re-listed → re-sold. The number at the end is what hit your bank account, not what an estimate said. Multi-channel sync keeps the re-listed units honest.

A refurbisher running 1,200 orders/month on FBA who switches to tracked removals typically recovers $2,000-$5,000/month in the first 90 days — most of it from reimbursements already there, unclaimed.

Three things you can do today ​

Even if you never touch Rilk, do these:

  1. Export your removal orders from the last 90 days out of Seller Central and total the COGS. The number will be bigger than you think. That's the leak.
  2. Audit for reimbursement-eligible warehouse-damaged units. Amazon's eligibility window is finite — typically 18 months for most claim types. Anything older is gone forever.
  3. Set up a receiving workflow for returns. Even a spreadsheet works under 100/month. Scan serial, grade A/B/C, route to bin. Discipline matters more than the tool.

Sellers who treat removals as noise pay the leak indefinitely. The ones who track them recover five-figure margin a year. The difference is one workflow.

Built for resellers and refurbishers.

© 2026 Rilk