Our platform uses the Amazon Selling Partner API as a data source
As you probably know, a new retail analytics reporting experience is available from Vendor Central platform on Amazon.
Thanks to our new integration with the Selling Partner API (SPAPI), our platform has been migrated to this new source on the 5th of December 2022.
Reports impacted were previously available in the Brand Analytics and ARA Basic experiences but Amazon will be redirecting users to the new experience soon, and the legacy sources will no longer be accessible from the Vendor Central Account. Depreciated date of the old reports is not defined at the moment from Amazon.
We have started collecting data from this new data source SPAPI in June 2022 to ensure continuity and a long enough look back period.
Which reports are concerned by the new data sources ?
Sales
Traffic
Inventory
Metrics : What does this mean for you?
Your entire configuration remains unchanged : all your dashboards, exports etc will be maintained. No action required from your side.
Some metrics will no longer be available from Amazon side so we won’t be able to update those ones from the platform. Please find the list of those metrics below.
Consequently, those legacy metrics collected from the old reports will no longer be refreshed from the platform but still available from your account if needed
These metrics will be marked as legacy in your account (ie “Rep OOS (Manufacturing Ordered) (Legacy)“)
We decided to keep the former reports as a source in order to provide you a way to collect those metrics until now.
Several metrics will be computed by ourselves such as “Conversion rate" which is no longer provided by Amazon.
All metrics still available from the new sources have been mapped with the new ones will automatically be replaced. No specific action needed to use your software.
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 case 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.
Metrics no longer available from AMAZON SPAPI
|
|
|
|
AMAZON SOURCE | ARA 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” |
Data granularity
Because of the very limited lookback window from the new source, we are computing daily data to create a weekly, monthly & yearly view.
Thanks to the migration to new Vendor Central reporting API, you will have access to a more granular data source from the studio. Traffic & Sales data will be available at a daily level (vs weekly formerly)
With the new data source, not all Inventory metrics are available at the daily granularity. Therefore short term, Amazon is unable to provide a daily grain Inventory report without removing the metrics which are only available weekly. Metrics only available weekly include: sellThroughRate, unhealthyInventory, and unhealthyUnits.
SPAPI Data Granularity
|
|
|
|
|
AMAZON SOURCE | GRANULARITY | LOOKBACK FORMER SOURCE | LOOKBACK NEW SOURCE | COMMENT |
TRAFIC | Days | - | 1460 |
|
TRAFIC | Weeks | 104 | 7 | Because of the very limited lookback window from the new source, we are computing daily data to create a weekly view. |
TRAFIC | Months | 24 | 36 |
|
TRAFIC | Quarter | - | 8 |
|
TRAFIC | Year | - | 3 |
|
SALES | Days | - | 1460 |
|
SALES | Weeks | 104 | 7 | Because of the very limited lookback window from the new source, we are computing daily data to create a weekly view. |
SALES | Months | 24 | 36 |
|
SALES | Quarter | - | 8 |
|
SALES | Year | - | 3 |
|
INVENTORY | Weeks | 104 | 7 | Because of the very limited lookback window from the new source, we are computing daily data to create a weekly view. |
INVENTORY | Months | 24 | 36 |
|
INVENTORY | Quarter | - | 8 |
|
INVENTORY | Year | - | 3 |
|
What was the process carried out by Jellyfish?
June 2022 : Migration to the last version of Selling Partner API (SPAPI) in our sandbox environment : We started to collect data from the new source.
June to November 2022 : Data quality check between the old & the new source. Discussions with Amazon to improve data accuracy with the new source.
End of November 2022 : Validation of our data integrity control. The Amazon SPAPI data source seems to be accurate, completeness, and consistent. We are ready to migrate.