Refunded, but no box ever arrived
A customer orders a set of garden lights, asks for a return saying the item is not as described, and gets a refund. Amazon expects the item to come back to a fulfilment centre. Weeks pass. It never arrives. Under Amazon's policy you may be due a reimbursement for that unit, but only if someone notices, and only if it has not already been paid automatically.
Across a busy month there may be dozens of these, mixed in with thousands of normal refunds and returns. The data to find them is in your reports. Linking it is the part nobody has time for.
Why these gaps stay hidden
Refunds and returns live in different reports with different dates. The refund appears in your settlement when it is issued. The return appears in the FBA customer returns report when the item is received, which may be weeks later. Some returns arrive with a different item or an empty box. Some refunds are reimbursed automatically. Matching them means following each order across reports and time.
- Refunds are dated when issued, returns when received, so they rarely sit next to each other.
- Returns can arrive under a different disposition or with a different FNSKU.
- Some gaps are already reimbursed automatically and must be excluded.
- Replacements and exchanges look like refunds but follow a different path.
- The window for raising a case is limited, so waiting too long loses the option.
What goes uncollected
Each unmatched refund is a sale you have paid back with no stock to show for it. For low value items it may not be worth pursuing; for higher value ones it often is. The bigger issue is that without a routine you do not know how many there are, so you cannot decide whether it is worth the effort.
There is a second cost too. Returns that arrive with the wrong item or an empty box are a sign of return abuse on particular products. Without matching, that pattern stays invisible.
A small worked example shows how quickly it gets messy. An order is refunded on the 3rd. On the 20th a unit comes back under the same order but with a different FNSKU, because the customer sent a cheaper variant. On the 28th an automatic reimbursement is paid for part of the value. Looking at any one report, the order seems either fine or fully missing. Only by following it across all three can you see what actually happened and whether anything is left to raise.
The refund and return matching we build
- Daily reads through the Selling Partner API of refunds from your settlement and transaction data, customer returns, replacements and reimbursements.
- Matching by order ID and SKU, so each refund is linked to a return received, a reimbursement paid, or nothing yet.
- A waiting period you set, after the refund date, before an unmatched refund counts as a gap.
- Separate flags for returns that came back as a different item or with a disposition suggesting the wrong product was sent back.
- A list of candidate cases, sorted by value and by the time left under the case window you configure, with order ID, dates, SKU and refund amount ready to paste.
- A log of cases raised and outcomes, so nothing is raised twice and results feed into your reconciliation.
| Refund state | Result |
|---|---|
| Return received as expected | Closed, no action |
| Reimbursed automatically | Closed, recorded |
| No return, inside waiting period | Watching |
| No return, waiting period passed | Candidate for a case |
| Wrong item or empty box returned | Flagged for review |
The check does not decide who is right. It shows you what the reports say. Whether to raise a case, and how, is your team's call under Amazon's current policy.
What changes for your team
A short list appears each week with refunds that have no matching return after the waiting period. Your team looks through it, raises cases where it makes sense and records the outcome. The list does not grow unmanaged because each item has a status.
You also get a clearer view of which products attract returns that never come back or come back wrong. That feeds into listing changes, packaging decisions and sometimes the decision to stop selling a product through FBA at all.
The same data is useful to your bookkeeper, because refunds, returns and reimbursements finally link up by order instead of sitting in separate totals.
Could this be your account?
- You have never matched FBA refunds against returns received.
- Nobody knows how many refunded items never came back.
- Returns sometimes arrive as a different product or an empty box.
- Cases for missing returns are raised only when someone happens to notice.
- Your reimbursement figures are not linked to individual orders.