Amazon Selling Partner: Setup guide
On this page
This guide explains how to collect data from Amazon Selling Partner.
Introduction
For a list of the fields that you can collect from Amazon Selling Partner, see Amazon Selling Partner.
Limitations
Collecting data from Amazon Selling Partner comes with the following limitations:
-
Not every report type is available for each marketplace.
-
The Amazon Selling Partner API reports in UTC timezone only.
-
Some reports are not ready in real time. This means when you try to collect data on a report that is not ready, an error could occur.
-
Search Query Performance report type has a data lookback window of 17 months.
Creating a datastream to collect data from Amazon Selling Partner
The basics of creating a datastream to collect data from any data source are explained in our guide to Collecting data in Adverity. This guide contains information about the specific steps to create a datastream to fetch data from Amazon Selling Partner.
Configuration: Choose the data you want to collect from Amazon Selling Partner
To choose what data to collect and customize the Amazon Selling Partner datastream configuration, follow these steps:
-
(Optional) Rename your datastream.
-
In Report category, select the report category for which to collect data.
-
In Report type, select the type of data to collect from Amazon Selling Partner.
-
In Identifier type, select the identifier type to use when collecting data.
-
In Date Granularity, select the time unit in which to collect data.
-
In Marketplaces, select the marketplaces for which to collect data.
-
In ASINs, select the ASINs (Amazon Standard Identification Numbers) for which to collect data.
Troubleshooting
Revenue number alignment
Compare fetched data with client UI Orders reports when revenue numbers don’t align:
-
Granularity differences: Ensure same level of detail in both reports
-
Timezone mismatches: Account for UTC vs local timezone differences
-
Filter variations: Verify same date ranges and status filters applied
Marketplace naming standardization
USA marketplace standardization: Marketplace for USA comes through as “United States of America”. To align with standard country mapping, change this to “United States” for consistency across reporting platforms.
Fetch consistency considerations
1-day vs 2-day fetch comparison: You may need to use Receive extracts as they are fetched local data retention configuration as numbers won’t always align between different fetch periods. The underlying cause for this discrepancy is not definitively known, making consistent fetch strategy important.
Recommendations:
-
Establish consistent fetch frequency based on business requirements.
-
Monitor for data discrepancies between different fetch intervals.
-
Use Receive extracts as they are fetched local data retention configuration to maintain data integrity when inconsistencies occur.
Tips and best practices
Understanding connector capabilities
The Amazon Selling Partner connector provides access to ecommerce data for vendors on Amazon marketplace through the Amazon Selling Partner API (SP-API). This REST-based API enables programmatic access to orders, shipments, payments, and comprehensive marketplace analytics.
Timezone considerations and data alignment
Critical timezone awareness API reports return data in UTC timezone whereas client UIs may be set to a different timezone. This is particularly problematic for US clients who typically work in EST/PST timezones.
Data alignment strategies: - Compare with client UI Orders reports to ensure granularity, timezone, and filters align - Consider implementing a timezone transformation for orders reports to match client expectations - Verify date ranges match between API extracts and client dashboard views
Data collection configuration
Local data retention
Set Receive extracts as they are fetched as the recommended local data retention method to handle potential data inconsistencies between fetches.
Overwrite settings
Use purchase-date as the recommended overwrite field to ensure proper data versioning and historical accuracy.
Recommended datastream configurations
Amazon Selling Partner | Orders
Report category: FBA Sales Report type: Flat file All Orders Report by Order Date Local data retention: Receive extracts as they are fetched Overwrite: purchase-date
Field mapping recommendations: - Map marketplace to country_name for geographic analysis - Map item-price to revenue for financial reporting consistency
API limitations and considerations
-
UTC timezone reporting may not align with business timezone expectations
-
Data consistency can vary between different fetch periods
-
Marketplace naming conventions may require standardization for reporting consistency
-
Regional data access depends on proper API authorization and account permissions
Best practices for implementation
-
Test timezone alignment before production deployment
-
Validate revenue calculations against client UI reports
-
Standardize marketplace naming for consistent geographic reporting
-
Monitor fetch consistency and adjust retention strategy as needed
-
Document field mappings for clarity in downstream reporting systems
Authentication and setup
Ensure proper Amazon Selling Partner API credentials are configured with appropriate permissions for accessing order and marketplace data. The connector requires valid SP-API access tokens and proper authorization for the specific marketplaces being monitored.
What’s next?
-
Apply Data Mapping to your collected data to harmonize data collected from different sources in Adverity.
-
Transform your data to meet your needs by creating and applying transformations to your datastream.
-
Load your data into a warehouse to continue working with your data in Adverity.
-
Load your data into an external destination of your choice.