> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data reference

> Metrics, breakdowns, refresh cadence, and limits for the Amazon Vendor Central data source in Adriel.

## Introduction

Amazon Vendor Central is the portal Amazon uses for first-party (1P) vendors — brands and manufacturers that sell their products wholesale to Amazon, which then resells them to end customers. The connector reads vendor sales reports from the Amazon Selling Partner API (SP-API) v2021-06-30, exposing shipped-revenue, shipped-cost, and shipped-unit data at ASIN and daily granularity.

Authentication uses Login with Amazon (LWA) credentials issued by an Amazon developer application — a refresh token, client ID, and client secret entered manually rather than through an OAuth pop-up. The connector targets the North America SP-API endpoint; marketplace coverage is selected via the marketplace IDs sent in each report request.

As an e-commerce connector, revenue and product breakdowns are standardized so widgets can aggregate alongside ad-platform sources without additional configuration.

<Note>
  **Vendor Central vs. Seller Central.** Vendor Central is for first-party vendors that sell wholesale to Amazon. Seller Central is for third-party sellers that list on Amazon's marketplace. The two surfaces share an SP-API root but expose different reports and require separate connectors.
</Note>

To connect this data source, see [How to connect Amazon Vendor Central to Adriel](/data-sources/a-f/amazon-vendor-central/how-to-connect).

## Data refresh strategy

### Architecture data

There is no separate product-hierarchy refresh for Vendor Central. The ASIN catalog is implicit in the sales report — ASIN identifiers are persisted as rows arrive from each daily report.

### Reports data

Reports cover shipped-sales data at ASIN and daily granularity. This is a **daily-cache** connector: dashboards read from a daily cache rather than querying the SP-API on demand.

**Initial backfill.** After connection, historical daily data from the last **180 days** is retrieved.

**Refresh schedule.** The cache refreshes **every 4 hours** (cron `0 */4 * * *`, UTC). At each refresh, the latest **5 days** of data are re-pulled, so late-arriving corrections to recently completed dates are picked up.

**Data lag.** Amazon enforces a **3-day minimum data lag** — sales for the most recent 3 days are not yet available from the SP-API and appear once Amazon releases them ([Vendor sales report (Vendor Analytics)](https://developer-docs.amazon.com/sp-api/docs/vendor-retail-analytics-reports)).

**Currency.** Each row's currency is preserved from the Amazon response; the reporting currency defaults to USD.

## Architecture levels

Vendor account → ASIN → Daily report row.

Each row represents one ASIN on one day.

## Date range limits

There is no hard per-breakdown range cap. The practical bound is the historical window: up to **180 days** of history are back-filled at connection, and the most recent **3 days** are withheld by Amazon's data lag. Date ranges that extend into either edge return no data for the uncovered days.

## Metrics

<Note>
  **How to read the columns**

  The **Data type** column uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.

  The **API Key** column uses code style like `shippedRevenue` for the literal SP-API field name. *Italic text* marks a value produced on the Adriel side rather than returned directly by the SP-API — for example a field injected at parse time or generated by the cache layer.
</Note>

### Revenue & sales

<Note>
  **Nested amount extraction.** `shippedRevenue` and `shippedCogs` arrive from the SP-API as objects of shape `{ amount, currencyCode }`. The connector extracts the `amount` for aggregation and keeps the currency code at the data-source level for display formatting.
</Note>

| Metric           | Description                                                                                                                      | Data type | API Key                        |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------- | --------- | ------------------------------ |
| Shipped Revenue  | Revenue from shipped units, extracted from the `amount` of the shipped-revenue object.                                           | Currency  | `shippedRevenue`               |
| Shipped Units    | Number of units shipped.                                                                                                         | Number    | `shippedUnits`                 |
| Customer Returns | Number of customer returns.                                                                                                      | Number    | `customerReturns`              |
| Row Count        | Aggregate count of cached rows for the period. Generated by the cache layer as a data-completeness check, not a business metric. | Number    | *Generated by the cache layer* |

### Costs

| Metric       | Description                                                                    | Data type | API Key       |
| ------------ | ------------------------------------------------------------------------------ | --------- | ------------- |
| Shipped COGS | Cost of goods shipped, extracted from the `amount` of the shipped-COGS object. | Currency  | `shippedCogs` |

## Breakdowns

### Products

| Breakdown | Description                                                                       | API Key |
| --------- | --------------------------------------------------------------------------------- | ------- |
| ASIN      | Amazon Standard Identification Number. Can be used as a breakdown or as a metric. | `asin`  |

### Time & date grouping

<Note>
  Time-grouping breakdowns are Adriel-side aggregations of the same daily report rows; the report date itself is injected at parse time rather than returned as a field by the SP-API.
</Note>

| Breakdown           | Description                                                  |
| ------------------- | ------------------------------------------------------------ |
| Date                | Report date in `yyyy-MM-dd` format.                          |
| Auto Time Breakdown | Automatically picks the best granularity for the date range. |
| Daily               | Split reports by day.                                        |
| Weekly (Start: Mon) | Split reports by week starting Monday.                       |
| Weekly (Start: Sun) | Split reports by week starting Sunday.                       |
| Monthly             | Split reports by calendar month.                             |
| Quarterly           | Split reports by calendar quarter.                           |
| Yearly              | Split reports by calendar year.                              |

### Overview & status

<Note>
  Overview breakdowns are Adriel-side groupings applied on top of the cached report data.
</Note>

| Breakdown       | Description                                   |
| --------------- | --------------------------------------------- |
| No Grouping     | Do not break down; return one aggregated row. |
| Datasource Name | Group by Adriel datasource name.              |

## Limitations

Based on the current connector, Amazon Vendor Central has:

* **A 3-day minimum data lag.** Sales for the most recent 3 days are not yet available from Amazon. Rolling "last N days" ranges should exclude or visibly mark the trailing 3-day window.
* **A 180-day historical window.** Data older than 180 days from the connection date is not back-filled.
* **A rate limit of 1 request per minute per account.** Initial 180-day backfills and large catalog syncs progress slowly; workspaces with many accounts feel this most.
* **A limited, shipped-sales-focused metric set.** Other vendor analytics surfaces — forecasts, inventory, chargebacks — are not exposed by this connector.
* **Row Count is a completeness check, not a business metric.** It is generated by the cache layer rather than returned by the SP-API.
* **Currency handling is per row.** Monetary amounts are extracted for aggregation while the currency code is retained at the data-source level; multi-currency rollups should apply conversion at the widget level.
* **Manual credential entry.** The connection uses LWA credentials (refresh token, client ID, client secret) from the vendor's own Amazon developer application rather than an interactive OAuth flow.

## API references

* [Amazon Selling Partner API overview](https://developer-docs.amazon.com/sp-api/)
* [Reports API v2021-06-30 reference](https://developer-docs.amazon.com/sp-api/docs/reports-api-v2021-06-30-reference)
* [Vendor sales report (Vendor Analytics)](https://developer-docs.amazon.com/sp-api/docs/vendor-retail-analytics-reports)
* [Authorizing Selling Partner API applications (Login with Amazon)](https://developer-docs.amazon.com/sp-api/docs/authorizing-selling-partner-api-applications)

## See also

* [How to connect Amazon Vendor Central](/data-sources/a-f/amazon-vendor-central/how-to-connect) (paired how-to)
* [Amazon Seller Central data reference](/data-sources/a-f/amazon-seller-central/data-reference) — third-party marketplace seller sales
* [Amazon Ads data reference](/data-sources/a-f/amazon-ads/data-reference) — Amazon advertising performance
* [Shopify data reference](/data-sources/o-z/shopify/data-reference) — direct-to-consumer commerce platform