Amazon Delays FBA Lost and Damaged Inventory Reimbursement Policy to March 31, 2025
Amazon has pushed the new FBA lost‑and‑damaged reimbursement policy to March 31 2025, giving sellers about 21 extra days to upload landed‑cost data via the new Cost Management page in Seller Central. Reimbursements will be calculated on the submitted landed cost (e.g., $21.50 per unit) instead of default estimates, affecting payouts for lost or damaged inventory.
Overview
Amazon has moved the launch of its revised FBA lost‑and‑damaged inventory reimbursement policy from March 10, 2025 to March 31, 2025. The three‑week extension gives sellers extra time to enter accurate landed‑cost data through the new Cost Management page in Seller Central. Because the new formula bases reimbursements on the seller’s actual product cost rather than the selling price minus fees, precise cost reporting will directly affect the amount sellers receive when inventory is lost, damaged, or destroyed.
Key Points
- Effective Date Shift — The updated reimbursement rules will now apply on March 31, 2025, instead of the originally announced March 10 deadline.
- Extra Preparation Time — Sellers receive roughly 21 additional days to collect cost information and upload it before the new calculations take effect.
- Cost Management Page Launch — A dedicated page in Seller Central lets sellers record landed costs, including purchase price, inbound shipping, customs duties, and any other direct expenses.
- Full Access by Late February — All seller accounts will be able to view and edit the Cost Management page by February 28, 2025, providing a one‑month window to populate data.
- Reimbursement Formula Change — Amazon will reimburse based on the landed cost you submit; accounts without cost data will fall back to Amazon’s default assumptions, which often result in lower payouts.
- Scope of Covered Events — The policy covers inventory lost in inbound transit, damaged inside fulfillment centers, lost during the returns process, or destroyed without seller consent.
How the New Reimbursement Model Works
- Cost Data Entry — Sellers log into Seller Central, navigate to the Cost Management page, and input the landed cost for each SKU. For example, a seller of a $30 Bluetooth speaker would record the purchase price ($18), inbound freight ($2), customs duty ($1), and any handling fees ($0.50), resulting in a total landed cost of $21.50 per unit.
- Amazon’s Default Assumption — If a seller does not provide landed‑cost data, Amazon applies a generic cost estimate (often a percentage of the selling price). In the same speaker example, Amazon might assume a cost of 40 % of the $30 price, or $12, which would lower the reimbursement amount.
Analysis & Recommendations
Why This Matters
The 21‑day extension lets sellers enter accurate cost components (purchase, freight, duties) before the March 31 2025 go‑live, preventing lower default payouts such as $12 vs $21.50 per unit. Missing data could reduce reimbursements by up to 44% and affect cash flow for high‑value SKUs.
Key Takeaways
- Effective date moved from March 10 2025 to March 31 2025, adding ~21 days for preparation.
- A new Cost Management page in Seller Central lets sellers record landed cost details (purchase price, inbound freight, customs, handling) per SKU.
- Reimbursement now multiplies submitted landed cost by quantity; e.g., 5 units at $21.50 yields $107.50 versus $60 using the default 40% estimate.
- Full access to the Cost Management page is available by February 28 2025, giving a one‑month window to populate data for up to 80% of inventory.
Recommended Actions
- →In Seller Central, navigate to Inventory > Cost Management and begin entering landed‑cost data for top‑selling SKUs today.
- →By February 28 2025, use the “FBA Inventory Reimbursements” report to identify high‑loss SKUs and upload cost data plus supporting invoices for at ...
- →Share the completed cost spreadsheet with any third‑party reimbursement service before March 31 2025 to ensure claims use the correct landed costs.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!