When should I expect data to update?
As you probably know, we use several Amazon APIs to collect & process your data.
Amazon needs 3 days to make consolidated data available via the API.
As soon as the data is made available by Amazon, you can access it directly from J+Retail analytics.
So please keep in mind that for analyses:
at a daily level → Data is available after 3 days
at a weekly level → Data is available the week after, on the following Wednesday
at a monthly level →Data is available from the 3rd day of the following month
Example 1 : We are on Friday the 3rd of February at 9AM, I want to track Shipped COGS amount from the previous period :
✅ Daily data is available until the 30th January
✅ The consolidated view of the previous week is available since the Wednesday
❌ The consolidated view the previous month is NOT available. We have to wait the 4th of the month.
💡 In that case, we recommend to make analysis at a daily level. It enables you to get the trend of the previous month while waiting to get the consolidated view of the last month
Example 2 : We are on Monday the 6th of February at 9AM, I want to track Shipped COGS amount from the previous period :
✅ Daily data is available until the 2nd of February
❌ The consolidated view of the previous week is NOT available. You have to wait for the Wednesday
✅ The consolidated view the previous month is available since the 4th of February.
Is there a delta between J+ Retail Analytics & dashboards in Vendor Central ?
The migration aligns data that is shared between API report types and internal retail reporting tools but several specific cases could cause temporary data discrepancies :
Data may change after the daily report is made available by Amazon API :
To ensure data accuracy we have decided to do not aggregate daily data for consolidate weekly or monthly report from the console.We noticed data consistency issue from Amazon side for monthly reports.
For instance, a monthly report can be updated several months after (without any reason provided by Amazon). We have created a dedicated monitoring to limit the risk.
Why are we migrating to the last version of Selling Partner API?
Data differences between external API reporting and internal retail reporting were the biggest reporting pain point for both vendors and retail stakeholders. This migration aligns data that is shared between API report types and internal retail reporting tools. With the transition to API 2.0 report types, we are migrating to a new data source.
What are the benefits of the new API report types compared to the former?
There are 2 main benefits :
Source data parity: the new source data for API 2.0 report types is now the same source used by Amazon retail category teams, as well as the retail analytics dashboards in Vendor Central.
Expanded historical daily data: daily historical data now increases from 13 months to 3 years, providing vendors increased visibility into their business historically.
Why is Lost Buy Box Price (LBB Price) not available in reports?
LBB (Price) is no longer supported by the Amazon Retail Pricing team, and Amazon will not be able to provide an LBB metric in the vendor retail analytics report types until an effective replacement metric is available. An alternative metric is in development, but we have not received guidance as to when Amazon will be able to share that metric externally.
Fortunately for you, we collect "buy box" data via another method: our web scraping service. This way, we guarantee that all use cases are still managed.
Which metrics are no longer available in the new Amazon data source
Some of the metrics that were available in the legacy data source backing API 1.0 report types are not available in the new data sourcing powering API 2.0 report types. If you have a specific business use cases for a metric no longer available in an API 2.0 report type, share your feedback with us.
However, we have managed to find some alternatives in the table below.
AMAZON SOURCE | METRIC | STATUS | NOTES |
SALES | Conversion Rate | Alternative available | Derivative metric be calculated by Jellyfish as |
SALES | Average Sales Price | Alternative available | Not available at the new data source. Derivative metric be calculated by Jellyfish as |
SALES | Lost Buy Box price | Not available | Not available at the new data source |
SALES | Free Replacements | Not available | Not available at the new data source. |
SALES | Subcategory (Sales Rank) (Ordered) | Not available | Not available at the new data source. This metric does not match the PDP "Best Sellers Rank," as is expected by vendors. |
SALES | Subcategory (Sales Rank) (Shipped) | Not available | Not available at the new data source. This metric does not match the PDP "Best Sellers Rank," as is expected by vendors. |
INVENTORY | Replenishment Category | Not available | Not available at the new data source |
INVENTORY | Available Inventory | Alternative available | Not available at the new data source ; derivative metric. Can be replace by “sellableOnHandInventoryUnits” |