Inside Seller Central, there is a Reports section where you can pull all sorts of useful reports regarding aspects of your Amazon business.
One of the problem I face as an Amazon seller, is the amount of lost and damaged inventory that goes on inside Amazon’s warehouses.
When inventory goes missing, or is damaged and destroyed, sellers should be automatically reimbursed for it. However, that is not always the case. Hence it is a good idea to run the reports and check them on a regular basis.
Reports to generate
There are a few reports we want to run. First go to “Reports” -> “Fulfillment”
You will come to the Amazon Fulfillment Reports page below.
1. Damaged Report
Go to the left-hand column, expand the “Inventory” section -> “Inventory Adjustments”
You can either view the report online or download it. Choose “Damaged” for Reason Group. For “Event Date”, I haven chosen 365 days for this case since this is the first time I’m running this report.
Click “Generate Report”. If you have chosen the “View Online” tab like me, you will get something similar to the below. You can either copy and paste into Excel or Google Sheets.
2. Destroyed Report
Repeat, but choose “Destroyed” for Reason Group. Date range remains 365 days if this is the first time you are running this report.
3. Lost Report
Repeat, but choose “Lost” for Reason Group. Date range remains 365 days if this is the first time you are running this report.
4. Found Report
Repeat, but choose “Found” for Reason Group. Date range remains 365 days if this is the first time you are running this report.
5. Reimbursement Report
Go to the left-hand column, under the “Payments” section -> “Reimbursements”
Date range remains 365 days if this is the first time you are running this report. Click “Generate Report”.
How to use these reports
I typically copy and paste the reports into Google Sheets for easier processing.
One tab for each type of report I generate. I will work my way down the list.
Lost Report / Found Report / Reimbursement Report
I will usually start with the “Lost Report”. Take the first FN SKU on the “Lost Report”, and do a search for it in the same report. You want to know how many of the same FN SKU is “Lost”.
If an item goes missing, sometimes it is found and added back to your inventory at a later date. To check if any item have been added back into your inventory, search for that FN SKU in “Found Report”.
If item is lost and have not been found and added back, you should be reimbursed for it. Check under “Reimbursement Report” for it.
In short, for the same FN SKU, each entry inside the Lost Report should have a corresponding entry in either Found Report or Reimbursement Report.
Eg, I have a FN SKU which have 4 entries in the “Lost Report”.
I found 1 corresponding entry inside “Found Report” and 1 corresponding entry inside “Reimbursement Report”. That means there are still 2 missing reimbursements. Open a case with Seller Central if this is the case.
Damaged Report / Destroyed Report/ Reimbursement Report
Next, check the same FN SKU under Damaged Report and Destroyed Report.
You should be reimbursed for every entry found in these two reports as well.
Check the same FN SKU in Reimbursement Report for the corresponding reimbursement entries. If there are missing reimbursements, open a case with Seller Central.
In short, for the same FNSKU, each entry inside the Damaged Report and Destroyed Report should have a corresponding entry in the Reimbursement Report.
Opening a case with Seller Central
This is typically what I use.
Pls refer to this FN SKU – X000Xxxxx
I ran a report from Amazon’s seller central and obtained the following info. Pls refer to attached excel file.
Damaged – 2
Destroyed – 4
Lost – 1
Reimbursements – 2
Found – 0
Please assist to check for missing reimbursements. There are a total of 7 damaged, destroyed and lost, but only 2 reimbursements and 0 found. Thank you.
As for the Excel, I will just do a “Download as” from Google Sheet into Excel format and attach it with my case.
Example of how my Excel look like. All relevant IDs in the screenshots have been changed to something random and not related to the example above 😉