Amazon Selling Partner (Edge)

Configure Amazon Selling Partner as a Source in your Pipeline

Perform the following steps to configure your Amazon Selling Partner Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Amazon Selling Partner.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Amazon Selling Partner Source.

   • In the Connect to your Amazon Selling Partner account section, do the following:

     • From the Region drop-down, select the Amazon Selling Partner region for your seller account. This determines the Amazon Seller host and API endpoint Hevo uses to connect to your account. Default value: North America.

     • Click Authenticate Your Amazon Selling Partner Account, sign in, and grant Hevo access to your account.

   • In the Historical Sync Window section, from the Historical Sync Duration drop-down, select the duration for which you want to ingest existing data from the Source. This cannot be changed after the Pipeline is created. Default value: 2 Years.

     Note: Amazon Selling Partners has low API rate limits, which can slow syncing large amounts of historical data. To speed up the initial sync, consider choosing a duration of 1 year or less.

6. Click Test & Continue to test the connection to your Amazon Selling Partner Source.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests historical data for the selected objects based on the Historical Sync Duration specified when configuring the Source, and loads it into the Destination.

• Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.

For the following objects, Hevo ingests only the incremental data in subsequent Pipeline runs:

For all other objects, Hevo ingests the entire data during each Pipeline run.

Amazon SP-API enforces per-operation usage plans and rate limits that vary by SP-API operation and Amazon store, and that can adjust dynamically based on your account’s business metrics. If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records to the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---