Why Amazon's New FBA Reimbursement Policy Is Confusing Sellers
In early 2024, Amazon overhauled how it calculates FBA reimbursements, introducing a two-tier valuation framework that caught many sellers off guard. The new structure distinguishes between:
- Pre-Order valuation — based on your Sourcing Cost, representing what you paid to acquire the inventory before it entered Amazon's fulfillment network.
- Post-Order valuation — based on your actual sales proceeds, calculated as your selling price minus Amazon's standard fees.
For most reimbursement scenarios involving lost or damaged inventory, the category of damage determines which valuation applies. A "Customer Damaged" return occurs, by definition, after an order has been placed and fulfilled. That makes it a Post-Order event, meaning Amazon should base any reimbursement on the Post-Order value, then reduce it by the standard 50% adjustment for customer-caused damage.
The problem: Amazon's system is applying the Pre-Order Sourcing Cost instead, then cutting that lower number in half. The result is a reimbursement that can be a fraction of what sellers are legitimately owed.
This is not a minor rounding error. For high-margin or high-volume sellers, the difference between 50% of Post-Order value and 50% of Sourcing Cost can be hundreds or thousands of dollars per case, compounding across every affected return.
"The two-tier reimbursement structure is sound in theory, but the implementation has exposed a serious gap between policy documentation and system execution. Sellers who don't understand the distinction between Pre-Order and Post-Order valuations will accept underpayments without ever questioning them." — Dara Liston, Senior FBA Compliance Strategist, Northbridge Seller Advisory Group
For related step-by-step guidance, see A-to-Z guarantee claim guide.
The Calculation Error in Plain Terms
Let's say you source a product for $12 (Sourcing Cost) and sell it on Amazon for $40, with $10 in fees, giving you Post-Order sales proceeds of $30.
For a Customer Damaged return, the correct reimbursement calculation is:
- Post-Order value: $30
- 50% customer-damaged reduction: $15 reimbursement owed
What Amazon's broken system is doing instead:
- Pre-Order Sourcing Cost: $12
- 50% customer-damaged reduction: $6 reimbursement paid
That is a $9 shortfall on a single unit. Multiply that across dozens or hundreds of Customer Damaged returns and the cumulative loss becomes significant. For sellers processing high volumes through FBA, this error is quietly draining revenue at scale.
The seller whose case prompted this article opened two Seller Central support cases. In the first (Case 17631693171), an agent eventually acknowledged the miscalculation and corrected the reimbursement. In the second (Case 17638337871), phone support acknowledged the issue, but the internal review team continued to reject the correction. That pattern, where front-line agents recognize the error but escalation teams override them, suggests a systemic policy-interpretation problem, not a one-off mistake.
If you have been watching your reimbursements land and assuming they are correct, you have probably already absorbed this loss quietly for months.
Who Is Affected and How Widespread Is This?
Based on how Amazon's reimbursement calculation logic is structured, this error likely affects any FBA seller who has received a Customer Damaged reimbursement since the new policy took effect. Sellers who do not audit their reimbursements line by line will never notice the discrepancy, because the reimbursement appears in Seller Central as a standard credit with no flag indicating it used the wrong valuation basis.
If you sell products with a meaningful spread between Sourcing Cost and selling price (which describes the majority of profitable FBA businesses), treat every Customer Damaged reimbursement as suspect until you have verified the calculation basis.
You can review your reimbursement reports in Seller Central's FBA inventory reimbursement section to identify which transactions involved Customer Damaged classifications and compare the reimbursement amount against what the Post-Order formula should yield.
For sellers dealing with broader account issues tied to inventory disputes, the FBA reimbursement and account health page offers additional context on how Amazon's systems interact across policy categories.
How to Challenge an Incorrect FBA Reimbursement
Fighting an Amazon reimbursement error requires persistence and documentation. The following steps reflect the most effective escalation path based on how these cases have resolved.
- Pull your FBA Reimbursements Report from Seller Central and identify every transaction coded as "Customer Damaged" since the policy change took effect.
- For each transaction, calculate what the correct reimbursement should be using the Post-Order formula: (Selling Price minus Standard Fees) multiplied by 50%, and compare it to what Amazon actually paid you.
- Open a new support case in Seller Central for each underpaid transaction, clearly stating that Amazon applied the Pre-Order Sourcing Cost instead of the Post-Order sales proceeds value for a Customer Damaged return, and that this contradicts the published reimbursement policy.
- Attach documentation supporting your claim: your product's selling price history, the applicable fee breakdown, and a written calculation showing the correct reimbursement amount versus what was paid.
- If the first agent closes the case without correction, escalate by replying to the case thread and explicitly requesting internal review team escalation, citing the policy language that defines Customer Damaged as a Post-Order event.
- If escalation fails, open a fresh case referencing the case number of the rejected escalation and reiterate the policy basis, asking for a senior specialist review.
- Document every case number and agent response in a centralized tracker so you can demonstrate a pattern of rejection if you need to escalate further through Amazon's Executive Seller Relations channel.
Patience matters here. The seller whose story prompted this article had one case corrected and one still under dispute. The correction proves Amazon's system can fix these errors. The ongoing dispute proves that clear documentation and persistence are required to get there.
Why Amazon's Agents Are Getting This Wrong
The root issue appears to be a disconnect between the written policy and how Amazon's internal tooling calculates reimbursements. When the policy was updated, the documentation was revised, but the reimbursement system was not fully updated to reflect the correct logic for Customer Damaged classifications. Front-line agents, working from the updated documentation, can see the discrepancy when it is pointed out. Internal review teams, working from the system output, default to accepting the automated calculation as correct.
This is a known failure mode in large organizations rolling out policy changes: the policy team and the engineering team operate on different timelines, and sellers absorb the cost of the gap.
For a deeper look at how Amazon's policy categories interact with reimbursement rights, the order defect rate appeals guide covers related account health dynamics that can compound reimbursement disputes.