In most FBA audits we run, one category tops the money list: the Amazon return not restocked. A customer gets refunded, the item is supposed to come back and re-enter your sellable inventory — and then, quietly, it doesn't. No restock, no reimbursement, no notification. Just a refund debit on your statement and a unit that no longer exists anywhere. Multiply that by every refund you issue, and you can see why the FBA customer returns claim is the highest-dollar recovery category for most sellers.
- Every customer refund should end one of three ways: the unit is restocked as sellable, graded unsellable (with a valid reason), or reimbursed because it never came back. Anything else is a leak.
- Customers have roughly 30 days to physically return a refunded item. If it never arrives, Amazon generally owes you a reimbursement.
- The FBA customer returns claim window is 60–120 days after the refund date. You can't file before day 60, and after day 120 the money is gone forever.
- Amazon auto-reimburses many cases, but automation misses units — and with only a 60-day filing corridor, misses expire fast. Audit monthly, not annually.
- Finding an Amazon return not restocked is a matching exercise: refund events vs. the Returns report, Inventory Ledger, and Reimbursements report, joined by order ID.
The three things that can happen after a customer return
When a customer requests a refund on an FBA order, Amazon usually refunds them immediately — often before the item has even shipped back. From that moment, your unit is in limbo, and only three legitimate outcomes exist under Amazon's FBA reimbursement policy:
| Outcome | What happens | What you're owed | Where it shows up |
|---|---|---|---|
| 1. Returned & restocked sellable | Item arrives at the FC, passes grading, re-enters your sellable pool. | Nothing — you have the unit back. (You still ate the refund and fees, but the inventory is whole.) | Returns report shows the return; Inventory Ledger shows a positive adjustment back to sellable. |
| 2. Returned but unsellable | Item arrives damaged or opened. If customer-damaged, it sits in unsellable — that's on the customer, not Amazon. But if Amazon or its carrier damaged it, or it's misgraded, a reimbursement is due. | Depends on fault — customer-damaged: no claim; Amazon/carrier-damaged or wrongly graded: reimbursement. | Returns report shows a disposition (customer-damaged, defective, carrier-damaged, etc.). |
| 3. Never returned at all | Customer keeps the refund and the item. After ~60 days with no return receipt, Amazon owes you the unit's value. | Reimbursement — typically the sale price minus applicable fees, since the loss happened after a customer order. | Refund exists in payments; no matching entry in the Returns report or Inventory Ledger. This absence is the claim. |
Units fall through the cracks in the seams between these outcomes. A return gets scanned in but never re-enters sellable inventory. A unit gets graded "customer damaged" when the customer's return comment says the box arrived crushed. A refund is issued and nothing ever happens again — no return, no reimbursement, no event of any kind. Each of those is potentially money owed to you, and none of them generate an alert.
The third outcome — refunded, never returned, never reimbursed — is the classic Amazon return not restocked case and usually the biggest pile of dollars. It's invisible precisely because it's defined by an absence of data, and absences don't show up when you skim reports.
How to find every Amazon return not restocked in your reports
The audit logic is simple to state: every refund needs a matching return receipt, a reimbursement, or a valid disposition. No match, no explanation — that's a claim. You need three reports, all in Seller Central, all matched by order ID.
Pull your refunds
Go to Reports → Payments → Transaction View (or the date-range reports) and filter to refund events. Export a window that is 60–120 days old — that's the range you can actually still file on. Note the order ID, SKU, quantity, and refund date for each.
Pull the FBA Returns report
Go to Reports → Fulfillment → FBA Customer Returns for the same window plus a 60-day buffer after it. This shows every unit that physically arrived back at a fulfillment center, with its disposition (sellable, customer-damaged, defective, carrier-damaged, and so on).
Pull the Inventory Ledger
Under Reports → Fulfillment → Inventory Ledger, look for the adjustment events tied to your returned SKUs. A return that was received should produce a corresponding inventory movement back into sellable or unsellable. If the Returns report says "received" but the ledger never shows the unit re-entering stock, you've found a gap.
Pull the Reimbursements report
Under Reports → Fulfillment → Reimbursements, list every reimbursement in the period with its reason and amount. Match these against your unexplained refunds by order ID. Check quantities and values too — a refund for two units matched by a reimbursement for one is still half a claim, and a reimbursement at the wrong value is a discrepancy of its own.
Match by order ID and flag the orphans
For each refund, ask: is there a return receipt? If yes, did it restock or get a valid disposition? If no return receipt, is there a reimbursement for the full quantity and a sensible value? Any refund left with no return, no reimbursement, and no valid disposition — and a refund date at least 60 days old — is a claimable FBA customer returns case. File it via Help → Get Support with the order ID and the report evidence.
Don't just check whether a match exists — check that it's whole. Sellers routinely find refunds for a quantity of 2 with a return receipt for 1, or a reimbursement for a unit whose refund was larger than the reimbursed value. Unit-level matching, not summary-level totals, is what surfaces these. It's also why an Amazon return not restocked can hide inside an order that looks "resolved" at a glance.
The timing rule: 30 days to return, 60–120 days to claim
Here's the mechanic that makes this category unusual. When Amazon refunds a customer, the customer has roughly 30 days to actually send the item back. Amazon then needs time to receive, grade, and process it. So Amazon won't even look at a "never returned" claim until 60 days after the refund date — before that, the case isn't ripe, because the item could still legitimately show up.
But the window doesn't stay open. Under the policy that took effect October 23, 2024, FBA customer returns claims must be filed no later than 120 days after the refund or replacement date. Day 60 opens the door; day 120 slams it. That leaves a filing corridor exactly 60 days wide.
You cannot file an FBA customer returns claim before day 60 after the refund, and you cannot file after day 120. Miss the corridor and the reimbursement is gone forever — there is no appeal path for an expired window. This is why the old habit of doing one big annual reimbursement audit is now worthless: by the time an annual audit runs, roughly two-thirds of the year's return claims have already expired. Under the pre-October-2024 rules you had 18 months; that lookback no longer exists. We break down all the current windows in The 60-Day Deadline: How Amazon Shrank FBA Reimbursement Windows.
The practical consequence: this audit has to run monthly. Each month, the set of refunds aged 60–120 days is a fresh batch of claimable cases — and last month's unfiled batch is partly expired. A returns-not-restocked process that runs quarterly forfeits money by design.
Why this is the #1 leak by dollar value
Lost inbound shipments and warehouse damage get more attention, but in audit after audit, returns not restocked recovers the most dollars. Three reasons:
1. Volume. Every FBA seller issues refunds constantly, and high-return categories — apparel, home & kitchen, electronics accessories — generate hundreds of return events per month. Each one is a chance for a unit to fall through the cracks. Warehouse damage happens to some of your inventory; returns processing happens to all of your refunds.
2. Item-not-returned refunds. Refund-at-first-scan and returnless-refund mechanics mean customers are often paid before Amazon has the item in hand. Some fraction of those items simply never arrive. Amazon's automation catches and reimburses many of these — but not all, and the misses skew toward messy cases: multi-unit orders, partial refunds, replacements, and exchanges.
3. Partial refund mismatches. When a customer gets a partial refund, or returns one unit of a three-unit order, the bookkeeping gets fuzzy. These are exactly the cases summary-level tools mark "resolved" because something matched — even though the quantities or values don't reconcile. The residue is real money.
Add it up and it tracks with the broader industry finding that FBA sellers lose 1–3% of annual revenue to unclaimed discrepancies — with returns not restocked typically the largest single slice. If you want to put a number on your whole leak, not just this category, see How Much Does Amazon Owe Me? The 2026 FBA Reimbursement Math.
One more point in this category's favor: valuation. Since March 2025, inventory lost or damaged before a customer order is reimbursed at manufacturing cost. But a return not restocked happens after a customer order — so it's still reimbursed at the sale price minus fees. Dollar for dollar, these are among the most valuable claims you can file.
A worked example: the $85k/month home & kitchen seller
The numbers below are illustrative — a composite of what this category typically looks like, not a statistic. Your mix will differ.
Take a home & kitchen seller doing $85,000/month in FBA revenue at an average selling price of $34. Home & kitchen returns run meaningfully higher than, say, supplements; assume a 7% refund rate for the illustration:
Of those 175 refunds, suppose 12% — about 21 units, roughly $715 in sale value — are never physically returned. Amazon's auto-reimbursement handles most, say three-quarters. The remainder, plus a couple of misgraded "customer damaged" units and a partial-quantity mismatch, leaves about $170–$250/month unclaimed in this one category. That's $2,000–$3,000/year — from a single leak, at a single revenue level, recoverable only if each month's batch is filed inside its 60-day corridor.
Scale the same ratios to a $300k/month seller and the category alone approaches five figures annually. The math is why "returns not restocked" sits at the top of ClawbackPro's eight recovery categories — and why we match at the unit level rather than trusting order-level totals.
FAQ: Amazon returns not restocked
How long does Amazon give a customer to send back a refunded item?
Roughly 30 days. Amazon usually refunds at first carrier scan — sometimes before the item ships at all — and the customer then has about 30 days to get it back to a fulfillment center. That's why the FBA customer returns claim window doesn't open until day 60 after the refund: Amazon wants the full return-and-processing cycle to finish before you can file.
What if the customer never returns the item at all?
If a refunded item hasn't come back within roughly 60 days of the refund, Amazon generally owes you a reimbursement for it — typically at the sale price minus fees, since the loss occurred after a customer order. Many of these are paid automatically, but the misses become manual claims you must file between day 60 and day 120 after the refund date.
Doesn't Amazon automatically reimburse returns that aren't restocked?
Often, yes. Since late 2024, Amazon says it proactively reimburses many customer-return cases. In practice, sellers still find gaps: mismatched quantities, partial reimbursements, wrong values, and refunds that never trigger any follow-up event. Because the manual window is only 60 days wide, anything automation misses expires fast — which is the argument for a monthly audit, whether you do it yourself, with software, or through an agency.
How far back can I claim an Amazon return not restocked?
Not far. Under the policy in effect since October 23, 2024, FBA customer returns claims can only be submitted 60–120 days after the customer refund or replacement date. The old 18-month lookback is gone. A refund from five months ago is already unclaimable, no matter how clear the evidence is.
Returns not restocked is the leak that punishes inattention most, because the clock starts on every single refund and never pauses. Run the matching audit monthly, file everything inside the corridor, and this stops being your biggest leak — and starts being your biggest recovery line.