How to Track and Update Your FBA Sourcing Costs in Seller Central
Amazon provides an FBA sourcing cost management page in Seller Central where sellers can view and update their product acquisition costs at the FNSKU level. Accurate sourcing costs are important for reimbursement calculations and profitability tracking.
Overview
Amazon now provides a dedicated page within Seller Central where FBA sellers can view and manage the sourcing costs associated with their inventory items. Understanding and accurately recording your sourcing costs is essential for tracking profitability, ensuring correct reimbursement calculations, and maintaining a clear picture of your FBA business finances.
Key Points / What Sellers Need to Know
- Sourcing cost defined — Amazon defines sourcing cost as the amount you pay to acquire a product from a manufacturer, wholesaler, or reseller, or the cost to produce the item if you manufacture it yourself. This figure specifically excludes shipping, handling, customs duties, and other ancillary expenses.
- FNSKU-level tracking — Costs are managed at the FNSKU level, meaning each unique fulfillment unit in Amazon's network can have its own sourcing cost entry.
- Active listings only — The page displays FNSKUs that currently have planned shipments or existing inventory within Amazon's fulfillment network.
- Older FNSKUs may be missing — Items shipped before 2024 that have not had a recent reimbursement may not appear on the page until a new reimbursement event triggers their inclusion.
- Store selection matters — If you operate multiple storefronts, you need to select the correct store from the drop-down menu to see the relevant FNSKUs.
How It Works
The sourcing cost management page serves as a centralized dashboard for all your active FBA inventory items. When you navigate to the page, you will see a list of FNSKUs that either have inbound shipments in progress or units currently stored in Amazon's fulfillment centers. For each item, you can enter or update the sourcing cost, which reflects what you actually paid to acquire or manufacture the product. Amazon uses this information in various financial calculations, including reimbursement valuations when inventory is lost or damaged. The page is regularly updated by Amazon to incorporate newly created FNSKUs, so sellers should check back periodically if a recently added item does not yet appear.
Managing Older Inventory
Sellers who have been using FBA for several years may notice that some of their older FNSKUs are not listed on the sourcing cost page. Amazon has noted that items shipped prior to 2024 will only appear once a new reimbursement has been issued for that particular FNSKU. This means that legacy inventory items may remain invisible on the page until Amazon processes a claim or reimbursement event related to them. Once that occurs, the FNSKU becomes available for sourcing cost updates. If you are unable to locate a specific item, Amazon recommends verifying that you have the correct store selected and checking the page again at a later date, as new FNSKUs are added on a rolling basis.
Analysis & Recommendations
Why This Matters
Accurate sourcing costs directly affect how Amazon calculates reimbursements for lost or damaged FBA inventory. Sellers who maintain up-to-date figures are better protected financially and can track product-level profitability more effectively.
Key Takeaways
- Sourcing cost covers only product acquisition — not shipping, duties, or handling fees
- FNSKUs shipped before 2024 may not appear until a new reimbursement is issued
- Accurate sourcing costs help ensure fair reimbursements for lost or damaged inventory
- Always verify the correct store is selected when looking for specific FNSKUs
Recommended Actions
- →Review and update sourcing costs for all active FNSKUs in Seller Central to ensure reimbursement accuracy
- →Check the page periodically for newly added FNSKUs, especially after creating new shipments
- →Verify your store selection if you operate multiple storefronts and cannot locate specific items
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!