Ship 1,000 units in a month, get 120 back, and if your category’s return threshold is 10% you pay a returns processing fee on 20 of them. That is one of four separate money events hiding inside a single return, and it is the only one most sellers can name. An Amazon FBA returns audit is the work of finding the other three, and the biggest of the three is the pile of units Amazon took off your inventory and never gave back. We run stores doing $200k a month for clients. The reports that settle this are already sitting in your account, unopened.
01A return is four money events, not one
The refund is the visible one. A customer sends the unit back, Amazon returns their money, and the sale disappears from your net. That much is obvious, and it is where most sellers stop looking.
Three more things happen to that same unit, and none of them announce themselves.
- The referral fee comes back, mostly. Amazon charges a referral fee of 15% in most categories on the original sale. On a refund it credits most of that back and keeps a refund administration piece. Small per unit, real across a year.
- The returns processing fee can hit. Since June 2024 this applies across all categories, not just apparel and shoes, on products with high return rates. It is threshold based, which matters more than the fee itself.
- The unit comes back in one of several conditions, or not at all. Sellable, unsellable, customer damaged, defective, carrier damaged, or missing. Each of those is a different amount of money, and one of them is not money at all.
The threshold mechanic is the one worth reading twice, because it changes how you should think about your return rate. Amazon sets a return threshold per category. You are only charged the returns processing fee on the units that exceed it. Using the numbers from the top of this post: 1,000 shipped, 120 returned, a 10% category threshold means 100 units are inside the allowance and you pay the fee on the 20 that went over.
That is a cliff, not a slope. Getting your return rate from 14% to 11% saves you almost nothing on this fee. Getting it from 12% to 9% saves you the entire line. Most sellers optimize the wrong side of that number because they assume the fee scales evenly with returns.
The fourth event is the one this post is really about. When a unit does not come back to your sellable inventory, that unit is either gone, sitting somewhere unsellable, or owed to you. Amazon’s system knows which. Your profit and loss does not, unless you go and reconcile it.
None of this is an argument for tolerating a high return rate. Returns are a profit-and-loss line the same way ad spend is, and a category that structurally drives them will eat a healthy-looking margin over months rather than weeks. We have written the full version of that math in our FBA profit margin breakdown, and the pre-launch signal that predicts it in the categories we stopped recommending. This post assumes the product is already live and the returns are already happening. The question now is how much of that money you can get back.
02The five buckets where your money ends up sitting
Reclaimable inventory is not one thing. It is five different failures that happen at five different points in the fulfillment chain, and they need five different pieces of evidence. Lumping them together is the reason most sellers file one vague case, get one templated reply, and give up.
Bucket one: lost or damaged inside the fulfillment center. Amazon received your unit, checked it in, and then misplaced it, crushed it, or wrote it off. This is the most common bucket and the one Amazon is best at catching on its own.
Bucket two: lost or damaged inbound. You shipped 500 units. Amazon’s receiving record says 486. Those 14 units disappeared between the carrier handing off the pallet and the unit hitting your inventory. This bucket is invisible unless you compare what you sent against what was received, shipment by shipment, and almost nobody does.
Bucket three: refunded but never returned. The customer got their money back and never actually shipped the item, or shipped it and it never reached the warehouse. You paid for a sale you did not make and lost a unit at the same time. This is the most expensive bucket per unit because you eat both sides.
Bucket four: returned but never restocked. The unit came back, the warehouse received it, and it never reappeared in your sellable count. Sometimes that is correct, because the item was genuinely destroyed. Sometimes it is an adjustment that never got made.
Bucket five: removal orders that went wrong. You asked for units back or asked for disposal, and what arrived at your address does not match what left the warehouse. Removals are the most-forgotten bucket because the seller has usually moved on mentally by the time the box arrives.
There is a sixth category that is not lost inventory but belongs in the same audit, because it comes out of the same reports and the same case queue. Fee overcharges. If Amazon has your product recorded at the wrong dimensions or weight, you are paying a fulfillment fee for a size tier you do not occupy, on every single unit, forever. That one compounds quietly and is worth more than most of the inventory claims.
Run those six against a real product and the shape of the problem changes. Take a unit with a landed cost around $9, which is roughly where one of our client launches sat after a 500-unit first order came in near $4,500 delivered. Thirty units stuck across those buckets is $270 of product cost, plus the margin on 30 sales you now cannot make. It is not a fortune. It is also not nothing, and it repeats every quarter you do not look.
03The reports that settle the argument
Everything above is recorded. That is the part sellers do not believe until they see it. Amazon writes down every unit movement, every adjustment, and every reimbursement it has already issued you, and it publishes all of it under Reports, then Fulfillment.
Five reports do the work.
- Inventory Ledger. The spine of the whole audit. It shows opening balance, receipts, customer shipments, adjustments, and closing balance for each product over a date range. If the arithmetic does not close, this report tells you where. Use the summary view to spot the gap and the detail view to see the individual events behind it.
- Inventory Adjustments. The line-by-line version of every change Amazon made to your counts that was not a sale. Each row carries a reason code, and the report page has the legend. This is where warehouse-lost, warehouse-damaged, warehouse-found, and disposal events live.
- Reimbursements. What Amazon has already paid you back, per unit, with the reason and the case identifier. Read this one first. Half of what looks like an open claim has already been settled, and filing again wastes a case.
- FBA Customer Returns. Every returned unit with its disposition. Sellable, unsellable, customer damaged, defective, carrier damaged. This is how you separate bucket three from bucket four.
- Received Inventory and your shipment records. Shipped quantity against received quantity per shipment. This is bucket two, and it is the one that needs your own packing list to be worth anything.
The mechanic that makes an audit possible is simple. Every unit is either sold, sitting in inventory, returned to inventory, or accounted for by an adjustment. If a unit is none of those, it is missing, and missing is claimable.
One habit makes the whole thing easier, and it costs nothing. Pull these as date-range reports on a fixed schedule and keep the files. Amazon’s report windows are not infinite, and a claim you cannot evidence is a claim you do not have. The seller who files with a clean shipment record and a ledger extract gets a different answer than the seller who files with a memory.
04Running the audit end to end
The audit is a reconciliation, and reconciliations work in one direction: prove the balance, then explain the gap. Do it in that order and it takes an afternoon. Do it in reverse, hunting for individual missing units first, and it takes a week and finds less.
Step one. Pick the window and pull everything. Take a closed month or quarter. Do not audit the current month, because open returns and in-transit units will look like discrepancies when they are just unfinished. Pull all five reports for the same date range and put them in one folder.
Step two. Close the ledger per product. Start with opening balance, add receipts, subtract customer shipments, apply adjustments, and compare to closing balance. Where it closes, you are done with that product. Where it does not, note the size of the gap in units. Most catalogues have a handful of products carrying almost all the discrepancy.
Step three. Subtract what you have already been paid. Open the Reimbursements report and match it against the gaps. Amazon has grown a lot better at issuing these automatically, so expect a real share of your gap to already be settled. What remains after this subtraction is your actual claim list.
Step four. Sort the remainder into buckets. Adjustments with warehouse reason codes go to bucket one. Shipment shortfalls go to bucket two. Refunds with no matching return record go to bucket three. Returns received but not restocked go to bucket four. Removal shortfalls go to bucket five. Each bucket becomes its own case, because each needs different evidence.
Step five. Check the value on every line. This is the step almost everyone skips. A reimbursement that arrived at the wrong amount is still a loss, and it looks like a win on the report. Compare the per-unit figure Amazon paid against what that unit actually cost you.
Step six. File, then track. One case per bucket, with the specific product identifiers, quantities, dates, and the report rows that support them. Log the case identifier and the date. Cases go quiet, and a case you forgot about is a case that closed itself.
The realistic output of a first audit on a small catalogue is a short list. Two or three products carrying most of the gap, a shipment discrepancy from a quarter you had stopped thinking about, and one fee that has been wrong since the listing went live. That last one is usually the biggest number on the page.
05What automatic reimbursement changed, and what it did not
Amazon has moved a lot of this in-house. Over 2024 and 2025 it expanded automatic reimbursement so that many warehouse-lost and warehouse-damaged units are now credited without anyone filing anything. That is a genuine improvement, and it is also why most advice written before 2024 will send you chasing claims that were settled weeks ago.
It changed the job. It did not remove it.
Automatic reimbursement is good at the failures that happen entirely inside Amazon’s four walls, because Amazon has both sides of that record. It is much weaker on the failures that involve a boundary. An inbound shipment that arrived short is a disagreement between your packing list and Amazon’s receiving scan, and Amazon only holds one of those documents. A removal order that arrived light is the same problem in reverse. Those buckets still need a human with evidence.
The second thing automation did not fix is valuation, and this is where the real money moved. In 2025 Amazon changed how it values FBA units lost or damaged in its network before a customer order. The basis moved to the manufacturing cost of the item rather than an estimated sale price, and sellers can supply their own cost figure. If you do not supply one, Amazon estimates it.
That single sentence is the most actionable thing in this post. The number in that box is the number you get paid. Go and look at what Amazon currently holds as your cost, compare it against what you actually pay your supplier, and correct it if it is wrong. It costs you one afternoon and it changes the value of every future claim on that product. An estimate that runs a few dollars light per unit is invisible on any single reimbursement and material across a year.
The windows are the part I will not put a number on. Amazon has changed the claim eligibility windows more than once across 2024 and 2025, and they differ by claim type. Any specific day count you read in a blog post, including this one, is a number that may already be stale. Open your own reimbursement policy page in Seller Central and read the current window before you build a schedule around it. The right cadence is the one that keeps you comfortably inside whatever the window says today.
06Automatic against manual: where each one actually wins
Once you accept that both systems are running at the same time, the useful question is which claims you can safely leave to Amazon and which ones only exist if you go looking. The split is cleaner than it sounds.
Leave to automation: units lost inside a fulfillment center, units damaged inside a fulfillment center, and most disposal errors. Amazon holds both sides of the record, the detection is systematic, and filing manually usually gets you a reply saying it has already been handled. Your job on these is verification. Amazon has already done the filing. Check the Reimbursements report, confirm the count matches the adjustment, and confirm the per-unit value is right.
File manually: inbound shipment shortfalls, removal order shortfalls, refunds with no returned unit, and fee overcharges from wrong dimensions or weight. Every one of these needs a document Amazon does not have or a comparison Amazon does not run on its own.
There is a third category that deserves its own line, which is claims you should not file at all. Filing speculative cases across a catalogue, hoping something sticks, is a way to burn your credibility with a support queue that remembers you. Every case should point at a specific quantity, a specific product, a specific date, and a specific report row. If you cannot produce those four things, you do not have a claim yet. You have a suspicion.
This is also where third-party reimbursement services fit. They typically work on a commission of what they recover, and for a large catalogue with years of history that arithmetic can make sense, because the audit work scales badly by hand. Two things to check before signing one. What access are you granting, and are they claiming things you could have got automatically anyway. A service that bills you a percentage of reimbursements Amazon was going to issue on its own is charging you for the weather.
07Where sellers lose claims they should have won
The claims that fail mostly fail for procedural reasons, not because the money was not owed. Five patterns cover almost all of it.
Filing before subtracting. The seller sees a gap of 40 units, files for 40, and Amazon replies that 31 were already reimbursed. The case closes, and the 9 units that were genuinely open get closed with it. Always reconcile against the Reimbursements report first.
One case for five problems. A case that says “I am missing inventory across several products” gets a templated answer, because there is nothing specific for an agent to act on. Five separate, narrow cases get five separate decisions, and narrow cases resolve faster.
No shipment evidence. For inbound discrepancies, your packing list, carton counts, and carrier proof of delivery are the case. Without them it is your word against a receiving scan, and the scan wins. This is why the prep and inbound stage matters so much to a claim you will not make for another three months.
Auditing the live month. Returns in progress, units in transit, and adjustments not yet posted all look like missing inventory. They are not. Audit closed periods and the noise disappears.
Letting cases go quiet. Support cases do not chase themselves. A polite follow-up on an open case with the original identifier, the product, and the quantity restated is normal practice and it works. A case nobody followed up on is not a decision. It is an expiry.
Underneath all five is the same habit. Treat this like bookkeeping, not like a dispute. You are not arguing with Amazon about whether returns are fair. You are reconciling two records that are supposed to match and asking for the difference. That framing gets better outcomes because it is the actual situation.
08The claim path, and the cadence that keeps you inside it
When a claim does need a human, the path through Seller Central is not obvious, because the system is designed to deflect you into help articles first. Here is the route we teach clients.
Log in and go to Help in the top right, then Get help and resources. Amazon shows a list of suggested articles. Scroll past all of them and pick My issue is not listed. Type a short, specific description of the problem, then continue. Amazon will offer a second round of articles. Ignore those too, select My issue is not listed again, and confirm it. Then choose Continue without details. When it asks you to categorize, select FBA related, which routes the case to the right team rather than general support. Then pick your contact method: email for anything that needs a paper trail, phone or chat when you need a fast answer on something simple.
Use email for reimbursement claims. You want the written record, and you want your evidence attached to the thread rather than described out loud to an agent.
On cadence, quarterly is the right default for an Amazon FBA returns audit. It is frequent enough to stay inside claim windows, and it lines up with closed accounting periods so the reports are clean. Monthly is worth it once your catalogue or unit volume gets large enough that a quarter’s worth of discrepancy is a number you would notice.
Two events should trigger an off-schedule audit regardless. The first is any large inbound shipment, where you check received against shipped within a week or two of check-in rather than waiting for the quarter. The second is after any removal or disposal order, where you reconcile what arrived against what was requested while the box is still in front of you. Both of those are the boundary cases automation does not catch, and both are much easier to evidence while the shipment is recent. If you are already reviewing aged inventory and removal decisions on a schedule, as we suggest in our storage cost tactics, fold this check into that same session.
09When this is worth handing over
For a seller with one or two products, this is a quarterly afternoon and you should do it yourself. The reports are free, the reconciliation is arithmetic, and doing it once teaches you more about your own fulfillment chain than any dashboard will.
It stops being a good use of your time at roughly the point where you have several products, a year or more of history, and inbound shipments arriving often enough that the boundary discrepancies pile up faster than you clear them. That is usually the same moment the rest of the operation gets heavy too. If that is where you are, our done-with-you launch support covers this alongside the inventory, listing, and PPC work, because it is the same operator running the same weekly review. It is the same reconciliation we run on the managed accounts doing $200k a month, on your catalogue.
Frequently asked questions
What is an Amazon FBA returns audit?
It is a reconciliation between what left your inventory and what came back to it. You pull Amazon’s own fulfillment reports for a closed period, close the ledger per product, subtract reimbursements you have already been paid, and file claims for the remaining gap. The work is closer to closing out a month of books than to arguing a case.
How much can I actually reclaim?
That depends entirely on your unit volume, your inbound frequency, and how much of your history has already been auto-reimbursed. Be skeptical of any figure quoted as a general recovery rate, including on service provider websites, because the number is driven by your catalogue rather than by the audit method. Run one quarter first and you will have your own number.
Does Amazon reimburse lost inventory automatically now?
Many warehouse lost and damaged cases yes, since Amazon expanded automatic reimbursement across 2024 and 2025. The categories that still need you are the ones crossing a boundary Amazon does not see both sides of, mainly inbound shipment shortfalls, removal shortfalls, refunds where no unit came back, and fee overcharges from wrong product dimensions.
What does Amazon pay per lost unit?
Since 2025, units lost or damaged in Amazon’s network before a customer order are valued on the manufacturing cost of the item rather than an estimated sale price, and you can supply your own cost figure. If you do not supply one, Amazon uses an estimate. Check the cost Amazon currently holds against what you actually pay, because that number is what you get paid.
How long do I have to file a reimbursement claim?
There is a window, it varies by claim type, and Amazon has changed it more than once across 2024 and 2025. Read the current window on your own reimbursement policy page in Seller Central rather than trusting a figure from any blog post. Then set your audit cadence comfortably inside it.
Are returns worth auditing if my return rate is low?
Yes, because the reclaim buckets are not driven by your return rate. Inbound shortfalls, removal errors, and fee overcharges happen to sellers with excellent return rates. The fee overcharge in particular is worth checking once even if you never audit anything else, since a wrong dimension charges you on every unit you have ever shipped.
The bottom line
Returns cost you in four places and you only see one of them. The refund is visible. The fee threshold, the condition the unit comes back in, and the units that never come back at all are all recorded somewhere you are not looking. An Amazon FBA returns audit is the habit of looking, once a quarter, on a closed period, using reports Amazon already generates for free.
Start with the smallest version. Pull the Inventory Ledger and the Reimbursements report for last quarter, close the balance on your top two products, and check the manufacturing cost Amazon holds against what you actually pay your supplier. That is an afternoon, and it will tell you whether the bigger audit is worth your time. For most sellers carrying real inventory, it is.
