# Seller Retail Analytics Reports

## Integration Overview

The Daasity Amazon Seller Central integrations utilize the Selling Partner API (SP-API) which is a REST-based API that helps Amazon selling partners programmatically access their data on orders, shipments, payments, and more.

{% hint style="warning" %}
**1-day data delay**

If you are looking at your extracted data and see that there is no data from yesterday, this is expected. This is because there is a 1-day delay for Seller Retail Analytics data to be available for extraction. For example, data from 1/1/2023 would not be loaded until 1/3/2023.&#x20;
{% endhint %}

## Integration Availability

This integration is available for:

* Enterprise
* Growth

{% hint style="info" %}
For Growth merchants, please take note that only \[`Sales and Traffic Business Report`] and \[`Sales and Traffic SKU Report`] are used.
{% endhint %}

## API Endpoints

The Daasity Amazon Seller Central - Reports API - Seller Retail Analytics extractor is built based on this [Amazon Seller Central API documentation](https://developer-docs.amazon.com/sp-api/docs/what-is-the-selling-partner-api). The following endpoints are used by Daasity to replicate data from Amazon Seller Central:

* [Reports](https://developer-docs.amazon.com/sp-api/docs/reports-api-v2021-06-30-reference)
* [Seller Retail Analytics Reports](https://developer-docs.amazon.com/sp-api/docs/report-type-values#seller-retail-analytics-reports)

## Entity Relationship Diagram (ERD)

[Click here to view the ERD for the Daasity Amazon Seller Central - Reports API - Seller Retail Analytics integration](https://lucid.app/documents/embedded/31b3406d-1276-4103-b5e7-6233aeb5314a) illustrating the different tables and keys to join across tables.

## Amazon Seller Central Schema

The Reports API will generate files in one of three formats (CSV, XML, and JSON). A report might vary slightly for each Seller Central account and thus Daasity will dynamically create the table based on the file extracted from Amazon. Thus each table will be a direct mapping from the file output to the table with no transformation.

* [Sales and Traffic Business Report](#sales-and-traffic-business-report)
* [Sales and Traffic Parent Report](#sales-and-traffic-parent-report)
* [Sales and Traffic SKU Report](#sales-and-traffic-sku-report)
* [Sales and Traffic Child Report](#sales-and-traffic-child-report)

### **Sales and Traffic Business Report**

* This report provides key sales performance metrics such as ordered product sales, revenue, units ordered, and claim amount, as well as overall traffic to your Amazon pages.
* Endpoint: [Seller Retail Analytics Reports](https://developer-docs.amazon.com/sp-api/docs/report-type-values#seller-retail-analytics-reports)
* Update Method: UPSERT
* Table Name: \
  \[`AMAZON_SELLER_CENTRAL.GET_SALES_AND_TRAFFIC_REPORT`]

{% hint style="info" %}
**Limitations:**

* This feature can **only be requested if Brand Analytics is turned on**.
  * The Brand Analytics feature availability is determined by Amazon. Not sure? Reach out to <Support@Daasity.com>
* Data updates every 24 hours.
* Requesting historical data will take a long time.
  * Before making a request for a historical report, reach out to <Support@Daasity.com>
    {% endhint %}

### **Sales and Traffic Parent Report**

* This report provides key sales performance metrics such as ordered product sales, revenue, units ordered, as well as page traffic metrics such as page views and buy box percentage of the seller’s entire catalog of items aggregated by date and Parent ASIN.
* Endpoint: [Seller Retail Analytics Reports](https://developer-docs.amazon.com/sp-api/docs/report-type-values#seller-retail-analytics-reports)
* Update Method: UPSERT
* Table Name: \
  \[`AMAZON_SELLER_CENTRAL.SALES_AND_TRAFFIC_PARENT_ASIN_REPORT`]

{% hint style="info" %}
**Limitations:**

* This feature can **only be requested if Brand Analytics is turned on**.
  * The Brand Analytics feature availability is determined by Amazon. Not sure? Reach out to <Support@Daasity.com>
* Data updates every 24 hours.
* Requesting historical data will take a long time.
  * Before making a request for a historical report, reach out to <Support@Daasity.com>
    {% endhint %}

### **Sales and Traffic SKU Report**

* This report provides key sales performance metrics such as ordered product sales, revenue, units ordered, as well as page traffic metrics such as page views and buy box percentage of the seller’s entire catalog of items aggregated by date and SKU.
* Endpoint: [Seller Retail Analytics Reports](https://developer-docs.amazon.com/sp-api/docs/report-type-values#seller-retail-analytics-reports)
* Update Method: UPSERT
* Table Name: \
  \[`AMAZON_SELLER_CENTRAL.SALES_AND_TRAFFIC_SKU_REPORT`]

{% hint style="info" %}
**Limitations:**

* This feature can **only be requested if Brand Analytics is turned on**.
  * The Brand Analytics feature availability is determined by Amazon. Not sure? Reach out to <Support@Daasity.com>
* Data updates every 24 hours.
* Requesting historical data will take a long time.
  * Before making a request for a historical report, reach out to <Support@Daasity.com>
    {% endhint %}

### **Sales and Traffic Child Report**

* This report provides key sales performance metrics such as ordered product sales, revenue, units ordered, as well as page traffic metrics such as page views and buy box percentage of the seller’s entire catalog of items aggregated by date and Child ASIN.
* Endpoint: [Seller Retail Analytics Reports](https://developer-docs.amazon.com/sp-api/docs/report-type-values#seller-retail-analytics-reports)
* Update Method: UPSERT
* Table Name: \
  \[`AMAZON_SELLER_CENTRAL.SALES_AND_TRAFFIC_CHILD_ASIN_REPORT`]

{% hint style="info" %}
**Limitations:**

* This feature can **only be requested if Brand Analytics is turned on**.
  * The Brand Analytics feature availability is determined by Amazon. Not sure? Reach out to <Support@Daasity.com>
* Data updates every 24 hours.
* Requesting historical data will take a long time.
  * Before making a request for a historical report, reach out to <Support@Daasity.com>
    {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.daasity.com/core-concepts/data-integrations/setup-guides/digital-integrations/amazon-seller-central/integration-specifications/seller-retail-analytics-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
