This article outlines recommendations and notes certain limitations imposed by the data source API, which you may need to consider when building your queries.
If you are connecting to this data source, please follow the instructions in our connection guide, and the available fields for this connector are listed in the metrics and dimensions documentation.
Request limits and recommended refresh rate
Request limit: Request limits depend on the endpoint used:
searchCatalogItems: 2 requests per second. See Amazon’s documentation.
getReportDocument: 0.0167 requests per second. See Amazon’s documentation.
getReport: 2 requests per second. See Amazon’s documentation.
createReport: 0.0167 requests per second. See Amazon’s documentation.
Recommended refresh window: 2-3 days
Historical range
The Amazon Vendor Central connector supports three reporting granularities: Week, Month, and Year. Each granularity has specific rules for historical range which are detailed further in the Things to consider section:
Week: 7 weeks
Month: 36 months
Year: 3 years
Accounts in Amazon Vendor Central
In the Amazon Vendor Central connector, each data connection is considered a separate account within the connection.
Your Supermetrics subscription determines the number of data source accounts you can use simultaneously.
Things to consider
Time period granularities
The Amazon Vendor Central connector has specific rules for setting the date range. The query lookback and data availability depend on the selected granularity. We have outlined some tips when setting your query data ranges:
Week
Setting | Value |
|---|---|
Maximum lookback | 7 weeks |
Maximum date range per query | 7 weeks |
Date boundaries | Sunday to Saturday |
Date Availability SLA | End of Monday following the week close (48 hours after Saturday) |
How to set your date range:
The start date must be a Sunday, for example, 2026-04-05.
The end date must be a Saturday, for example, 2026-04-18.
Limitations
Only the last 7 weeks of data are available. Queries requesting data from further back will return an error or fail.
Weekly data is not available until the end of Monday after the week closes (48-hour SLA). Querying a week that ended last Saturday before Monday may result in a fatal error.
Month
Setting | Value |
|---|---|
Maximum lookback | 36 months |
Max date range per query | 15 months |
Date boundaries | First to last day of each month |
How to set your date range:
Start date must be the 1st of a month, for example, 2025-01-01.
The end date must be the last day of a month, for example, 2025-03-31.
The connector automatically snaps your dates to the nearest full month boundaries, so a range of March 15 to May 20 will be sent to Amazon as March 1 to May 31.
Limitations:
Only fully completed months are supported. Querying data for the current (ongoing) month will result in an error.
The maximum span is 15 months per query. For longer periods, you’ll need to run multiple queries.
Year
Setting | Value |
|---|---|
Maximum lookback | 3 years |
Maximum date range per query | 2 years |
Date boundaries | January 1 to December 31 |
How to set your date range:
The start date must be January 1, for example, 2025-01-01.
The end date must be December 31, for example, 2025-12-31.
The connector automatically snaps your dates to full-year boundaries.
Limitations:
Only fully completed years are supported. Querying the current year (year-to-date) isn’t supported - Amazon can’t generate a yearly report for a year that has not ended.
The maximum time span is 2 years per query.
Performance
Amazon Vendor Central reports are generated asynchronously. After a query is submitted, Amazon processes it in the background while the connector waits for the results.
All requests for the same account share a single queue. If multiple queries are submitted at the same time, they’re processed one by one, which can increase wait times.
Reports can take minutes to hours, depending on the date range, granularity, and data volume.
If multiple SP-API reports are delayed, this is due to Amazon’s reporting system. Reports may stay in
IN_QUEUEuntil Amazon completes them.Delays can also happen due to duplicate requests, multiple apps accessing the same reports, or large data volumes.
To work around these limitations, you can:
Avoid running multiple large queries simultaneously.
Reduce your query date range or data granularity if possible.
Recommended data warehouse transfer settings
Tables
Date range: Last >1 months
Refresh method: Append and deduplicate
Deduplicate by: Today
Refresh window: 2 days
Schedule
Once a month
Day of the month 1
At time: 9–11 p.m. (Latest possible trigger on the first day after the lookback window. This allows the platform to prepare the data for the report.)