Reimbursements and fee forensics: the money Amazon owes you

For losses occurring before a customer order, Amazon has since a policy change in spring 2025 reimbursed the manufacturing cost value — your bare purchase or production price, without freight, duty, handling or margin (evidence level: practice; the policy sits in Seller Central behind the login). Previously the selling price was the usual basis.

From that follows the single most important action in this lesson: maintain your cost values in the account. Without stored costs Amazon estimates — and estimates rarely fall in your favour. Concretely:

• Enter a cost value per SKU and update it with every new purchase price.
• Only include costs that match the definition. Folding in freight and duty invites queries that stall the whole claim.
• Keep evidence to hand: the supplier invoice per batch. Without it, every figure is an assertion.

The fulfilment fee follows Amazon's own measurement of the ready-to-ship unit (lesson 6). If that measurement differs from reality you pay the difference on every single sale — permanently and without warning. That makes this the most rewarding case of all: one corrected value applies to every future order.

1. Measure yourself, properly. Packed and sealed: length, width, height, weight. Several units from different batches, and note the worst value.
2. Compare with the stored values. The fee preview shows which size tier Amazon is using.
3. Request a re-measurement on any discrepancy. With photos: product against a tape measure, scale with the reading visible, both in the same frame as the label.
4. Always check after packaging changes. New packaging does not automatically mean a new measurement — otherwise the old tier stays.

Deadlines differ by claim type, and the publicly circulating figures contradict each other: 60 days from the loss or damage notice for warehouse cases, markedly longer periods for other claim types and 90 days for removal orders are all cited (evidence level: disputed — what counts is the figure in your account). For practice that means two things, both independent of the exact number:

• A monthly audit run beats any deadline debate. Check every month and you are never in the position of having to invoke a deadline.
• Plan against the shortest circulating deadline. The same logic as the conservative corridor in Listing L16: work to the strictest figure and you lose nothing if a more generous one applies.

1. Pull the inventory ledger (previous month) and reconcile per SKU: opening stock plus receipts minus sales minus returns received = closing stock. Every discrepancy is a candidate.
2. Put the reimbursements report beside it. Amazon reimburses many warehouse cases automatically today (evidence level: practice) — anything already listed there is settled and is not filed again.
3. Check returns against inventory receipts: which refunded order has no return into the warehouse?
4. Reconcile open shipments: shipped versus received, per shipment.
5. Spot-check the fee preview against your own measurements — two or three SKUs a month give rolling coverage.
6. Open cases: one per matter, with a report extract, period, SKU, unit count and amount. Bundled claims across several matters get a blanket answer.

Providers exist who run the reconciliation automatically and keep a share of the reimbursement. The sober assessment:

• In favour: completeness on large ranges. With 300 SKUs you will never find everything by hand.
• Against: access to your account and responsibility for the claims. In an abuse case your account is liable, not the provider.
• The line sits, practically, where your own audit run takes more than an hour a month. Below that, doing it yourself is cheaper and more instructive — you see problems no reimbursement report shows.

The difference between “rejected” and “reimbursed” almost never lies in the facts but in the form. A claim an agent can follow in two minutes gets processed; one that raises questions gets closed. A solid chain of evidence has four links:

Evidence all four links with lines from Amazon's own reports and you are not making a claim, you are presenting an invoice. Link 4 is the one most people omit — and it is the most common rejection reason: “already reimbursed”. A claim that proves for itself that it is not a duplicate takes the easiest rejection out of the agent's hands.

Three subtleties separate a good process from a very good one:

• Pick generous periods and precise numbers. A loss is sometimes booked weeks after the event. Pull reports across two months but name exact lines in the claim — the wide window finds the case, the tight figures make it checkable.
• Keep your own numbering. Every case gets an identifier in your own sheet, with date, amount, case number and outcome. Without that sheet you will eventually file a duplicate — and that is the one way a legitimate routine turns into an account risk.
• Analyse rejections rather than filing them away. When the same reason comes back three times, your claim is missing a link. That is process information, not a run of bad luck.

And one thought beyond reimbursement: forensics is also an early warning system. If damage clusters on one SKU, the warehouse is rarely at fault — the packaging is. If receiving discrepancies cluster with one supplier, Amazon is rarely at fault — the count at packing is. Recover only the money and miss the pattern, and you recover the same money every month instead of fixing the cause once.