Track fees with the new SKU Economics report
We’ve launched a new SKU Economics report to make financial information in the SKU Economics tool more accessible and to illustrate the breakdown of fees, including the recently launched low-inventory-level fee.
SKU Economics is a tool on SKU Central, for all third-party sellers, that collects fees, sales, ads, off-Amazon costs, and net proceeds in a single view to help you optimize costs and understand your product selection performance. The new SKU Economics report is a downloadable report that enables you to view the costs and fees for each product in your catalog at once. It includes historical charges information for each fee type.
The report allows you to view the economics of your selection at the FNSKU, MSKU, ASIN, and parent-ASIN level. This single source for historical economics data eliminates the need to merge sales, fees, and ads reports to understand your net proceeds.
To learn more about the data included in the report, go to SKU Economics report.
To download your report, go to SKU Economics report.
34 replies
Seller_Yj3KUpV4BoBQF
Is there any way to download this report into a .csv or Excel file? When I download it's just a new webpage of gibberish.
Seller_rsphq7X7pXC92
The report idea is great indeed! Unfortunately at the moment it may not be accurate - in my case all of my FBM SKUs are duplicated multiple time in the report, making it hard to properly analyze the data. I also noticed that only sponsored product ads are added (while other ad types are missing). There is also a very strange representation of the fees value and quantity - as an example, FBA fees quantity is not equal to number on units sold, and FBA fee per unit is incorrect accordingly. I hope it will be fixed soon, and the report will be very a great tool to use.
Seller_tzb0Adb4whsRu
None of the reports available are accurate, never have been.
Seller_rsphq7X7pXC92
:) what is your way to track the data?
Seller_tzb0Adb4whsRu
Unfortunately, there is no one way to track data. There are so many reports, some are way too big to print, there are double or more of the same transactions, and it's just an overall mess.
This new SKU Economic Report is no different, it' very large, has repeated lines of exact same information, there are ASIN's or FNSKU's on our report that don't even exist in our catalog. Where did these come from? It's a mess!
So to answer your question, we try to look at multiple reports and compare to the settlement periods, which by the way "double dip" on the first and last day of the settlement periods, so they count these 1st and last days twice!
There is not a good way to track everything and that's where we were hoping this new report would be handy, but it has items on it that we haven't sold in years and FNSKU's and/or ASIN's that are not ours.
So if anyone has any suggestions as to how to keep track of all of the sales, returns, refunds, and the 500 fees we are being charged, we're looking forward to seeing your suggestions and tips. :)
Thank you,
Jim_Amazon
@Seller_rsphq7X7pXC92
Thank you for sharing these issues you experienced with your report. Our tech teams are addressing some data quality issues discovered after the release. We are aware of these issues and actively addressing them!
-Jim
Seller_NpqQK9PCW1Nep
Accodring to new SKU Economics report, there is data of "costOfGoodsSold", which is a Cost to manufacture or acquire the product. This value is provided by the seller and is applicable to both Fulfillment by Amazon (FBA) and Merchant Fulfilled Network (MFN) products.
Anyone know where we can put "cost of goods sold" at seller central?
Seller_Ggt6s7zXEwLbA
The fnsku report had some Amazon fees but no sales data so every product was showing a loss.
The msku report has so many DUPLICATES its virtually unreadable. For one product - 17 yes 17 lines of duplicate entries for a report spanning 7 days, so its not even a duplicate being entered for every day. Some of the columns also seem to be duplicate of their data.
I suppose I could spend the time doing a duplicate removal in Excel, but frankly, its a mess. Maybe someday I'll circle back, if I think of it, to try to again.
Seller_79ggWm617PHw3
Great idea, but no sales data showing up in ASIN report so useless at this time.
Seller_sxzMpLPSqxKJm
Duplicate lines, missing data, and possibly the worst error in this report--NO LOW INVENTORY FEE column. So the entire reason the report was created is missing from the report.
Thank you for your prompt correction of this report as it's essential to our business.
Seller_Sn1lURvF5srVf
- report data is not even nearly up-to-date: we need to know when the data was last updated by Amazon.
- aggregate by MSKU requested, but multiple lines appear for many MSKUs (one line will have the correct FNSKU in the FNSKU column; the near-duplicate line will have the ASIN in the FNSKU column)
- you need to separate the fee amount and the tax-on-fee amount in the generated file, which currently includes taxes in the 'Closing fee per unit' and 'Referral Fee per unit' (I understand that this is available via API)
- 'Base fulfillment fee' quantity can exceed 'Units Sold' qty and 'Net Units Sold' quantity
- for a 7-days file request submitted on Apr 24: your 'Generated Reports' line shows 'Date Range 04/16/24 to 04/22/24'; but the actual file shows Start Date 04/17/24, End Date 04/23/24
Track fees with the new SKU Economics report
We’ve launched a new SKU Economics report to make financial information in the SKU Economics tool more accessible and to illustrate the breakdown of fees, including the recently launched low-inventory-level fee.
SKU Economics is a tool on SKU Central, for all third-party sellers, that collects fees, sales, ads, off-Amazon costs, and net proceeds in a single view to help you optimize costs and understand your product selection performance. The new SKU Economics report is a downloadable report that enables you to view the costs and fees for each product in your catalog at once. It includes historical charges information for each fee type.
The report allows you to view the economics of your selection at the FNSKU, MSKU, ASIN, and parent-ASIN level. This single source for historical economics data eliminates the need to merge sales, fees, and ads reports to understand your net proceeds.
To learn more about the data included in the report, go to SKU Economics report.
To download your report, go to SKU Economics report.
Track fees with the new SKU Economics report
We’ve launched a new SKU Economics report to make financial information in the SKU Economics tool more accessible and to illustrate the breakdown of fees, including the recently launched low-inventory-level fee.
SKU Economics is a tool on SKU Central, for all third-party sellers, that collects fees, sales, ads, off-Amazon costs, and net proceeds in a single view to help you optimize costs and understand your product selection performance. The new SKU Economics report is a downloadable report that enables you to view the costs and fees for each product in your catalog at once. It includes historical charges information for each fee type.
The report allows you to view the economics of your selection at the FNSKU, MSKU, ASIN, and parent-ASIN level. This single source for historical economics data eliminates the need to merge sales, fees, and ads reports to understand your net proceeds.
To learn more about the data included in the report, go to SKU Economics report.
To download your report, go to SKU Economics report.
34 replies
34 replies
Seller_Yj3KUpV4BoBQF
Is there any way to download this report into a .csv or Excel file? When I download it's just a new webpage of gibberish.
Seller_rsphq7X7pXC92
The report idea is great indeed! Unfortunately at the moment it may not be accurate - in my case all of my FBM SKUs are duplicated multiple time in the report, making it hard to properly analyze the data. I also noticed that only sponsored product ads are added (while other ad types are missing). There is also a very strange representation of the fees value and quantity - as an example, FBA fees quantity is not equal to number on units sold, and FBA fee per unit is incorrect accordingly. I hope it will be fixed soon, and the report will be very a great tool to use.
Seller_tzb0Adb4whsRu
None of the reports available are accurate, never have been.
Seller_rsphq7X7pXC92
:) what is your way to track the data?
Seller_tzb0Adb4whsRu
Unfortunately, there is no one way to track data. There are so many reports, some are way too big to print, there are double or more of the same transactions, and it's just an overall mess.
This new SKU Economic Report is no different, it' very large, has repeated lines of exact same information, there are ASIN's or FNSKU's on our report that don't even exist in our catalog. Where did these come from? It's a mess!
So to answer your question, we try to look at multiple reports and compare to the settlement periods, which by the way "double dip" on the first and last day of the settlement periods, so they count these 1st and last days twice!
There is not a good way to track everything and that's where we were hoping this new report would be handy, but it has items on it that we haven't sold in years and FNSKU's and/or ASIN's that are not ours.
So if anyone has any suggestions as to how to keep track of all of the sales, returns, refunds, and the 500 fees we are being charged, we're looking forward to seeing your suggestions and tips. :)
Thank you,
Jim_Amazon
@Seller_rsphq7X7pXC92
Thank you for sharing these issues you experienced with your report. Our tech teams are addressing some data quality issues discovered after the release. We are aware of these issues and actively addressing them!
-Jim
Seller_NpqQK9PCW1Nep
Accodring to new SKU Economics report, there is data of "costOfGoodsSold", which is a Cost to manufacture or acquire the product. This value is provided by the seller and is applicable to both Fulfillment by Amazon (FBA) and Merchant Fulfilled Network (MFN) products.
Anyone know where we can put "cost of goods sold" at seller central?
Seller_Ggt6s7zXEwLbA
The fnsku report had some Amazon fees but no sales data so every product was showing a loss.
The msku report has so many DUPLICATES its virtually unreadable. For one product - 17 yes 17 lines of duplicate entries for a report spanning 7 days, so its not even a duplicate being entered for every day. Some of the columns also seem to be duplicate of their data.
I suppose I could spend the time doing a duplicate removal in Excel, but frankly, its a mess. Maybe someday I'll circle back, if I think of it, to try to again.
Seller_79ggWm617PHw3
Great idea, but no sales data showing up in ASIN report so useless at this time.
Seller_sxzMpLPSqxKJm
Duplicate lines, missing data, and possibly the worst error in this report--NO LOW INVENTORY FEE column. So the entire reason the report was created is missing from the report.
Thank you for your prompt correction of this report as it's essential to our business.
Seller_Sn1lURvF5srVf
- report data is not even nearly up-to-date: we need to know when the data was last updated by Amazon.
- aggregate by MSKU requested, but multiple lines appear for many MSKUs (one line will have the correct FNSKU in the FNSKU column; the near-duplicate line will have the ASIN in the FNSKU column)
- you need to separate the fee amount and the tax-on-fee amount in the generated file, which currently includes taxes in the 'Closing fee per unit' and 'Referral Fee per unit' (I understand that this is available via API)
- 'Base fulfillment fee' quantity can exceed 'Units Sold' qty and 'Net Units Sold' quantity
- for a 7-days file request submitted on Apr 24: your 'Generated Reports' line shows 'Date Range 04/16/24 to 04/22/24'; but the actual file shows Start Date 04/17/24, End Date 04/23/24
Seller_Yj3KUpV4BoBQF
Is there any way to download this report into a .csv or Excel file? When I download it's just a new webpage of gibberish.
Seller_Yj3KUpV4BoBQF
Is there any way to download this report into a .csv or Excel file? When I download it's just a new webpage of gibberish.
Seller_rsphq7X7pXC92
The report idea is great indeed! Unfortunately at the moment it may not be accurate - in my case all of my FBM SKUs are duplicated multiple time in the report, making it hard to properly analyze the data. I also noticed that only sponsored product ads are added (while other ad types are missing). There is also a very strange representation of the fees value and quantity - as an example, FBA fees quantity is not equal to number on units sold, and FBA fee per unit is incorrect accordingly. I hope it will be fixed soon, and the report will be very a great tool to use.
Seller_rsphq7X7pXC92
The report idea is great indeed! Unfortunately at the moment it may not be accurate - in my case all of my FBM SKUs are duplicated multiple time in the report, making it hard to properly analyze the data. I also noticed that only sponsored product ads are added (while other ad types are missing). There is also a very strange representation of the fees value and quantity - as an example, FBA fees quantity is not equal to number on units sold, and FBA fee per unit is incorrect accordingly. I hope it will be fixed soon, and the report will be very a great tool to use.
Seller_tzb0Adb4whsRu
None of the reports available are accurate, never have been.
Seller_tzb0Adb4whsRu
None of the reports available are accurate, never have been.
Seller_rsphq7X7pXC92
:) what is your way to track the data?
Seller_rsphq7X7pXC92
:) what is your way to track the data?
Seller_tzb0Adb4whsRu
Unfortunately, there is no one way to track data. There are so many reports, some are way too big to print, there are double or more of the same transactions, and it's just an overall mess.
This new SKU Economic Report is no different, it' very large, has repeated lines of exact same information, there are ASIN's or FNSKU's on our report that don't even exist in our catalog. Where did these come from? It's a mess!
So to answer your question, we try to look at multiple reports and compare to the settlement periods, which by the way "double dip" on the first and last day of the settlement periods, so they count these 1st and last days twice!
There is not a good way to track everything and that's where we were hoping this new report would be handy, but it has items on it that we haven't sold in years and FNSKU's and/or ASIN's that are not ours.
So if anyone has any suggestions as to how to keep track of all of the sales, returns, refunds, and the 500 fees we are being charged, we're looking forward to seeing your suggestions and tips. :)
Thank you,
Seller_tzb0Adb4whsRu
Unfortunately, there is no one way to track data. There are so many reports, some are way too big to print, there are double or more of the same transactions, and it's just an overall mess.
This new SKU Economic Report is no different, it' very large, has repeated lines of exact same information, there are ASIN's or FNSKU's on our report that don't even exist in our catalog. Where did these come from? It's a mess!
So to answer your question, we try to look at multiple reports and compare to the settlement periods, which by the way "double dip" on the first and last day of the settlement periods, so they count these 1st and last days twice!
There is not a good way to track everything and that's where we were hoping this new report would be handy, but it has items on it that we haven't sold in years and FNSKU's and/or ASIN's that are not ours.
So if anyone has any suggestions as to how to keep track of all of the sales, returns, refunds, and the 500 fees we are being charged, we're looking forward to seeing your suggestions and tips. :)
Thank you,
Jim_Amazon
@Seller_rsphq7X7pXC92
Thank you for sharing these issues you experienced with your report. Our tech teams are addressing some data quality issues discovered after the release. We are aware of these issues and actively addressing them!
-Jim
Jim_Amazon
@Seller_rsphq7X7pXC92
Thank you for sharing these issues you experienced with your report. Our tech teams are addressing some data quality issues discovered after the release. We are aware of these issues and actively addressing them!
-Jim
Seller_NpqQK9PCW1Nep
Accodring to new SKU Economics report, there is data of "costOfGoodsSold", which is a Cost to manufacture or acquire the product. This value is provided by the seller and is applicable to both Fulfillment by Amazon (FBA) and Merchant Fulfilled Network (MFN) products.
Anyone know where we can put "cost of goods sold" at seller central?
Seller_NpqQK9PCW1Nep
Accodring to new SKU Economics report, there is data of "costOfGoodsSold", which is a Cost to manufacture or acquire the product. This value is provided by the seller and is applicable to both Fulfillment by Amazon (FBA) and Merchant Fulfilled Network (MFN) products.
Anyone know where we can put "cost of goods sold" at seller central?
Seller_Ggt6s7zXEwLbA
The fnsku report had some Amazon fees but no sales data so every product was showing a loss.
The msku report has so many DUPLICATES its virtually unreadable. For one product - 17 yes 17 lines of duplicate entries for a report spanning 7 days, so its not even a duplicate being entered for every day. Some of the columns also seem to be duplicate of their data.
I suppose I could spend the time doing a duplicate removal in Excel, but frankly, its a mess. Maybe someday I'll circle back, if I think of it, to try to again.
Seller_Ggt6s7zXEwLbA
The fnsku report had some Amazon fees but no sales data so every product was showing a loss.
The msku report has so many DUPLICATES its virtually unreadable. For one product - 17 yes 17 lines of duplicate entries for a report spanning 7 days, so its not even a duplicate being entered for every day. Some of the columns also seem to be duplicate of their data.
I suppose I could spend the time doing a duplicate removal in Excel, but frankly, its a mess. Maybe someday I'll circle back, if I think of it, to try to again.
Seller_79ggWm617PHw3
Great idea, but no sales data showing up in ASIN report so useless at this time.
Seller_79ggWm617PHw3
Great idea, but no sales data showing up in ASIN report so useless at this time.
Seller_sxzMpLPSqxKJm
Duplicate lines, missing data, and possibly the worst error in this report--NO LOW INVENTORY FEE column. So the entire reason the report was created is missing from the report.
Thank you for your prompt correction of this report as it's essential to our business.
Seller_sxzMpLPSqxKJm
Duplicate lines, missing data, and possibly the worst error in this report--NO LOW INVENTORY FEE column. So the entire reason the report was created is missing from the report.
Thank you for your prompt correction of this report as it's essential to our business.
Seller_Sn1lURvF5srVf
- report data is not even nearly up-to-date: we need to know when the data was last updated by Amazon.
- aggregate by MSKU requested, but multiple lines appear for many MSKUs (one line will have the correct FNSKU in the FNSKU column; the near-duplicate line will have the ASIN in the FNSKU column)
- you need to separate the fee amount and the tax-on-fee amount in the generated file, which currently includes taxes in the 'Closing fee per unit' and 'Referral Fee per unit' (I understand that this is available via API)
- 'Base fulfillment fee' quantity can exceed 'Units Sold' qty and 'Net Units Sold' quantity
- for a 7-days file request submitted on Apr 24: your 'Generated Reports' line shows 'Date Range 04/16/24 to 04/22/24'; but the actual file shows Start Date 04/17/24, End Date 04/23/24
Seller_Sn1lURvF5srVf
- report data is not even nearly up-to-date: we need to know when the data was last updated by Amazon.
- aggregate by MSKU requested, but multiple lines appear for many MSKUs (one line will have the correct FNSKU in the FNSKU column; the near-duplicate line will have the ASIN in the FNSKU column)
- you need to separate the fee amount and the tax-on-fee amount in the generated file, which currently includes taxes in the 'Closing fee per unit' and 'Referral Fee per unit' (I understand that this is available via API)
- 'Base fulfillment fee' quantity can exceed 'Units Sold' qty and 'Net Units Sold' quantity
- for a 7-days file request submitted on Apr 24: your 'Generated Reports' line shows 'Date Range 04/16/24 to 04/22/24'; but the actual file shows Start Date 04/17/24, End Date 04/23/24
