Refunded but Never Returned: The 60-Day Rule Every FBA Seller Should Track

Amazon's return experience is famously customer-first: refunds are often issued the moment a return is initiated, before the item ships back — sometimes before it ever will. That's Amazon's business decision, and the FBA policy contains the counterweight most sellers only half-know:

If a customer receives a refund but doesn't send the item back within 60 days, Amazon is supposed to reimburse you for it.

Much of the time, that reimbursement happens automatically. The leak is in the word much. A meaningful fraction of refunded-never-returned cases produce no reimbursement — and unlike a missing item, nothing in your day-to-day workflow will ever surface them. The order looks closed. The refund looks handled. The money is simply gone.

How to check whether you're owed

Three data sources have to agree before you can claim:

1. Refund events— which orders were refunded, when, and for how much (your transaction/payments data is the truth here; reports that track physical returns don't carry amounts).
2. The FBA customer returns report — which refunded items physically arrived back at a fulfillment center. An order present here came back; the claim only exists for refunds with no matching return within 60 days.
3. The reimbursements report — whether Amazon already paid you for the unreturned item (reason CustomerReturn). Claiming money you were already paid is the fastest way to lose credibility on every future case.

A refund that is 60+ days old, absent from the returns report, and absent from the reimbursements report is a case worth filing — with the order ID, refund date, and days elapsed as your evidence.

The trap: the claim window

These claims have a filing window measured in months, not years — materially shorter than warehouse-loss claims. In practice that means a quarterly spreadsheet review will systematically miss claims that were valid when they arose and expired before you looked. This category, more than any other, rewards continuous monitoring over periodic cleanup.

Edge cases worth knowing

• Partial refunds: reimbursement follows what was actually refunded, not the list price.
• Returned but unsellable: an item that comes back customer-damaged is a different situation — you got the unit back, just not in sellable condition. Different policy, different (weaker) claim.
• Returnless refunds: for some low-value items Amazon refunds without requesting a return at all; these follow the same 60-day reimbursement logic.

Put a clock on every refund

Clawbackingests your refund events daily, cross-references every one against physical returns and reimbursements, and starts a visible countdown on each unreturned refund — surfacing the claim on day 60 with the case text already written, and warning you before the filing window closes. It's one of five audits that run on every sync; underpaid reimbursements and fee overcharges are two of the others. Run the free scan — it checks your last six months in one pass.