Search

Talk to Sales

Retail Analytics KPIs

Retail Analytics KPIs

Retail Analytics - KPIs

icon
Table Name: retail_analytics_kpis

The Retail Analytics KPIs table combines sales, traffic, and profit metrics into a single data model. It is designed to make sell-out reporting even easier by giving you once data source for all Retail Analytics performance metrics over time. It also includes new Net PPM input metrics like sales_discount and contracogs .

This table replaces the following:

  • retail_analytics_sales
  • retail_analytics_traffic
  • retail_analytics_net_ppm

Business questions & scenarios

What is this data useful for?

  • Unified reporting: This combined dataset makes it easy to report on sales, traffic, and profit without building your own model. It is intended to replace
  • Business performance review: How were sales last week, compared to the prior week and prior year?
  • Customer returns analysis: What products do customers return most often? What trends can we get ahead of?
  • Conversion rate (CVR) analysis: What is my detail page conversion rate by product?

Schema & update details

UI Report path
N/A
Amazon update frequency
Daily, with 48-72 hour latency. Learn more
Reason update frequency
Every 8 hours
Time Zone
Country local time zone
Granularity [?]
1 row per: - ASIN - Date - Period - Program - Distributor View

Historical data & change management

Time Period
DAILY
WEEKLY
MONTHLY
History available from Amazon
730 days
104 weeks
24 months
Reason lookback period
14 days
6 weeks
3 months

Data dictionary: fields in this table

Table & data nuances

  • Time periods may not match: All retail analytics tables are available at DAILY, WEEKLY, MONTHLY granularity. There may be Amazon-driven discrepancies between different granularities that Amazon has not explained. For example, if you compare WEEKLY data to the sum of the seven DAILY periods in that week, the total units/revenue/etc. may not be an exact match. We recommend using the highest-granularity data you can, to minimize discrepancies and stakeholder questions.
  • Manufacturing and sourcing view differences: This table contains data for both distributor views, manufacturing and sourcing. Each view behaves differently and contains different data. Learn more
  • Sales channels or “Programs:” Amazon provides data for Amazon Retail, Amazon Fresh, and Amazon Business, separated by the program field. Despite its name, the “Amazon Retail” program contains data for Retail, Fresh, and Business combined. Vendors can submit a case to request separate Amazon Fresh and Amazon Business data.
  • Amazon wants you to connect a product catalog. This table contains data by date by ASIN, but does not provide any product attributes like category, size, or even product title to help you identify or aggregate products. Amazon expects you to connect this table to a catalog/dimension table that maps ASINs to attributes, such as the Product Catalog table or our custom catalog upload.

How to query this table

It’s important to filter this table by period, distributor view, and program to avoid duplication. The example query below will provide ASIN-level sales by day for the current year-to-date.

  1. Change distributor view: search for and distributor_view = 'Manufacturing' and replace ‘Manufacturing’ with ‘Sourcing’.
  2. Change program: search for and program = ‘Amazon Retail’ and replace ‘Amazon Retail’ with ‘Amazon Business’ or another program.
select date
	, asin
	, ordered_revenue
	, ordered_units
	, shipped_revenue
	, shipped_cogs
	, shipped_units
	, customer_returns

from retail_analytics_sales

where period = 'DAILY'
	and distributor_view = 'Manufacturing'
	and program = 'Amazon Retail'
	and date >= '2024-01-01' and date <= '2024-03-31'

order by 1 desc, 2 asc