Amazon’s Rapid Retail Analytics, via the Selling Partner API (SP API), enables brands to access near real-time Vendor retail analytics – sales, traffic, and inventory data.

Previously, metrics shared with brands via interfaces like Vendor Central and the Selling Partner API were only available at a daily grain and delayed 72 hours. Rapid Retail Analytics offers new levels of granularity and significantly reduced latency to critical performance data.

Our integration is a code-free, fully-automated integration to Amazon’s Rapid Retail Analytics API for available traffic, sales, and inventory data. Your data is delivered to a private cloud warehouse or data lake destination owned by you.

There are three primary data feeds associated with the Rapid Retail data;

Note: The Openbridge integration currently supports Vendor accounts only. Sellers will be supported at a later date. For Sellers, we suggest using Sales Reports or the Orders API. Both offer more robust sales data solutions than the current Rapid Retail Analytics release.

The following is an overview of the metrics and their definitions for Sales, Inventory, and Traffic data feeds:

Note: Here is feedback from Amazon about variations when comparing Rapid Retail Event Data to Amazon Vendor Reports:

"Hourly metrics in rapid retail analytics and daily retail analytics in other datasets will not align. These reports differ particularly with the methods used to identify traffic from shoppers and remove robotic traffic. Many signals contribute to identifying and classifying traffic from shoppers vs. robotic traffic. Although the best available signals are used to classify traffic intraday, additional information may lead to Glance Views being reclassified in the future. This results in differences (both +/-) when comparing datasets across granularity (hourly vs. daily, weekly, etc). We recommend that users continue to use other datasets for non-hourly use cases and, generally, avoid trying to compare hourly datasets to other sources."

See this post from Amazon for more details on how this data works and how it varies from other Vendor Reports.

Each data feed is ASIN-specific and provides a key set of core metrics.

The Traffic Report contains information about a specific time range, ASIN (Amazon Standard Identification Number), and the number of glance views.

The Inventory Report also provides a time range and ASIN, but it includes the number of highly available inventory instead of glance views.

Lastly, the Sales Report provides a time range and ASIN, but two metrics; order units and order revenue.

Following are examples of the core data elements in each;

Rapid Retail data feeds are available in these markets;

Rapid Retail Analytics is a robust data analysis tool that captures cancellations with high accuracy, precisely logging the time at which they occur. The system offers transactional-level data, ensuring detailed information is available without summarization or aggregation. However, when interpreting and analyzing the data, it is essential to understand its contents clearly.

The cancellation data provided by Rapid Retail Analytics is presented in a granular form, maintaining the individual transaction details without any consolidation. This level of data granularity ensures comprehensive insights into cancellations, enabling thorough analysis and evaluation.

Below are Examples A, B, and C for ASIN B123456789154. These examples show how an order for one (1) unit and subsequent cancellation is handled over time. It is important to note a specific scenario related to cancellations, referred to as "Example B" for illustrative purposes. In this scenario, it is crucial to be aware that Amazon may deduct an order from the dataset if canceled after a certain period. This time period can vary, spanning from several hours to even days. It is imperative to account for this deduction when analyzing and interpreting the cancellation data, ensuring accurate insights and conclusions are drawn.

The order and cancelation occur within the same hour. This would net to 0 for that hour, and the ASIN combination (+1 quantity, followed by -1 quantity) and the results would be:

In “Example B”, the output would have two events (order and cancelation) represented in the hour they occurred. The output would be:

In “Example C”, the output would be the same as in Example B. The output will represent each event (order and cancelation) as they occur. The hour and ASIN combination are omitted with no events (orders or cancellations) in the 10:00 am hour. Zero values would only return if events occur and net to zero as in “Example A”.