Customer Returns Never Returned: the Biggest Reimbursement Category Nobody Checks

What's actually happening here

An Amazon return works in two separate steps: the customer gets refunded (or gets a replacement), and separately, the physical item is supposed to travel back to a fulfillment center. Those two events don't always both happen. Sometimes the customer never actually ships it. Sometimes it ships and gets lost in the return carrier's network. Sometimes it arrives at a fulfillment center and gets checked in against the wrong SKU or never scanned at all. In every one of those cases, you've refunded a sale and Amazon has no matching unit in your inventory ledger to show for it — and you're entitled to a reimbursement for the difference.

This is different from a straightforward return that comes back damaged or a straightforward FC loss. It's a reconciliation problem: two systems (refund records and inventory records) that should match and don't, and the gap only becomes visible if someone actually checks for it.

The window, and why it trips up more sellers than any other

You cannot file this claim before 60 days after the customer refund or replacement, and you cannot file it after 120 days. That's a comparatively narrow 60-day window, and it's the only claim type in the whole reimbursement policy where the window opens well after the loss rather than at the moment it happens. A seller checking reimbursements the same way they check FC losses — look back at what happened this month — will consistently miss this category, because the claim for a March refund isn't even eligible until May, and it's easy to have moved on by the time it becomes filable.

This is also, in our experience managing recovery across dozens of accounts, the single largest dollar category in the entire reimbursement policy — ahead of lost-inbound shipments, warehouse damage, and customer-service credits combined. It's large precisely because it's the easiest to overlook: nothing about a normal refund transaction flags itself as a potential claim. The refund looks routine. It's only routine if the item actually came back.

A worked example

A customer requests a return on 3 April and is refunded the same day. Amazon's return tracking shows the label was generated but never scanned by the carrier. On 3 April, you can't file — the window hasn't opened. On 2 June (day 60), it opens. If you haven't run a returns-reconciliation check by early June, this claim is sitting live and unfiled, earning nothing, on a clock that's already ticking toward its 1 August (day 120) close. A seller who only reviews reimbursements quarterly — say, at the end of June — catches it with weeks to spare. One who reviews annually, in December, has already lost it: day 120 passed on 1 August, five months earlier.

How to actually find these

The mechanical check is comparing your refund report against your FBA returns report for the same window, filtering for refunds with no matching received-unit record, then confirming those refunds are now inside their 60-to-120-day filing window. It's a report join, not a mystery — the data exists in Seller Central, it's just spread across two reports that don't reconcile themselves. The reason this category goes unclaimed at scale isn't that the evidence is hard to find; it's that almost nobody builds a standing process to look, because a missing return doesn't generate a notification the way an obvious FC loss sometimes does.

Running this check on a weekly rather than quarterly cadence is the difference between catching claims while they're still comfortably inside the window and racing the 120-day close. One account we track recovered $6,500 in a single fortnight running this cadence, including refunds on return shipping labels tied to items that were never actually sent back — a smaller, related category worth checking in the same pass.

Two adjacent lines are worth folding into the same check, because they share the identical root cause — a refund with no matching physical event on record. Unused return shipping labels, where Amazon generated a label the customer never scanned, are refundable in their own right. Partial returns, where a multi-unit order is refunded in full but only some units physically come back, leave the missing units eligible under the same 60-to-120-day window. Neither turns up if the check only looks for whole orders with zero units returned.

What to do when a claim in this category gets denied

The most common denial reason is that the item did arrive, just late or mis-scanned into a different SKU's inventory — in which case the claim is legitimately not owed, and pursuing it further just burns case history. Before refiling, check whether the SKU received a matching unit around the claim date under a different condition code or a bundled variant; misrouted check-ins are a real and non-fraudulent reason a return “never arrives” on paper while the physical unit is actually on a shelf. If the evidence genuinely shows no unit ever came back and the claim was denied anyway, request the specific denial basis before resubmitting — refiling the identical evidence against an unstated objection rarely changes the outcome.

A second denial pattern shows up when the claim is filed on day 61 or day 119 with thin documentation — technically inside the window, but close enough to either edge that Seller Support treats it as needing a stronger evidence trail than a claim filed comfortably mid-window. There's no published rule that says this happens, but it's a consistent enough pattern in the cases we've argued that we treat claims filed in the first or last week of the window as needing extra documentation by default, not as an afterthought if they come back denied.

Why this is the case-craft example we lead with

This category rewards exactly the kind of case discipline that a one-off audit doesn't provide: knowing the window doesn't open at loss time, running the reconciliation on a schedule, and filing once with the right evidence rather than repeatedly. Full Circle has managed more than $500M in Amazon spend across 100+ brands, and across the accounts behind our $803,457 in net reimbursements recovered since 10 February 2026, customer returns never returned was the largest single value category — ahead of every other claim type in the policy. Dr. Shield runs this check weekly rather than quarterly, priced on the call as a contingency against what's actually recovered, precisely because the 60-day delay on this window is the thing every less disciplined process misses.