Amazon Selling Partner: Tips and best practices

Amazon Selling Partner: 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 timezone enrichment 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 unique by fetch 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.

Data validation and 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 ‘unique by fetch’ 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 unique by fetch to maintain data integrity when inconsistencies occur

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.

Contents