How to review FBA fees and reimbursement discrepancies

An unexpected FBA charge is a reason to investigate. It is not automatically an error or an entitlement to reimbursement. Start with the transaction, relevant product details and the policy that applies to that event in the marketplace.

Amazon's public FBA page introduces the programme and fee categories.¹ For an actual reconciliation, use the current detailed fee schedule and charged account data. Keep estimates separate from amounts already assessed.

Reconcile one type of issue at a time

Separate fulfilment charges, storage charges, inbound discrepancies, customer returns and inventory reimbursement events. Each has different evidence and policy questions. A single total labelled Amazon owes us hides those differences.

For every potential discrepancy, record the marketplace, transaction date, SKU, ASIN, charged amount, reason for review and supporting reference. Preserve the original report. Put calculations and explanations in a separate working sheet so the source remains inspectable.

Match evidence to the question

For a dimensional concern, compare the relevant packaged dimensions and weight with the charged classification and current rules. For a shipment concern, preserve the shipment references, quantities and genuine dispatch or receipt evidence. For a reimbursement event, identify the policy and valuation basis that applies.

Check for reversals, partial adjustments and earlier payments before opening another case. A reimbursement posted in a later period can otherwise look like an unresolved loss in the original report.

Do not reuse outdated assumptions

An Amazon announcement in 2025 moved a manufacturing-cost reimbursement implementation date to 31 March 2025.² That historical announcement is a reason to verify the current policy, not a complete statement of every present reimbursement rule.

Confirm eligibility, evidence, valuation and submission timing for the specific event. Do not assume retail selling price is the correct reimbursement value. Avoid a universal claim deadline copied from an old blog or applied across unrelated event types.

Keep a case calculation readable

Imagine a shipment of 120 units, a later record of 114 received units and a further adjustment of 4 units. The remaining quantity to investigate is 2, subject to the actual receiving and reconciliation status. Claiming 6 without incorporating the adjustment would overstate the discrepancy. These are illustrative quantities, not evidence of an Amazon case.

A case should show the source quantity, adjustments, remaining difference and evidence. Keep the original currency. Do not add speculative profit or unrelated costs unless the applicable policy expressly supports them.

Close the loop

Track submitted, awaiting response, further evidence requested, adjusted and closed states. Close a case only after reconciling the outcome to the account. Use recurring issues to improve packaging records, shipment handoffs or document retention.

Discuss a scoped FBA review with Ecomtik and confirm specialist availability. For prevention through better stock records, read the inventory planning guide.

Footnotes

1. Amazon. Fulfillment by Amazon ↩

2. Amazon. Amazon inventory reimbursement update ↩