Amazon Selling Partner

Seller Central and Vendor Central are the official Amazon services that allow businesses to manage their Amazon sales activity.

Selling Partner API (SP-API) is a REST-based API that helps Amazon Selling partners access their Seller Central account data.

Features

Supported deployment models

We support the SaaS Deployment model for the connector.

Setup guide

Follow our step-by-step Amazon Selling Partner setup guide to connect Amazon Selling Partner with your destination using Fivetran connectors.

Schema information

This schema applies to all Amazon Selling Partner connections.

Explore Amazon Selling Partner schema ERD

Explore the interactive ERD

Seller modules

The following modules are available for the sellers:

• A+ CONTENT MANAGEMENT
• CATALOG
• EASYSHIP
• FBA
• FINANCE
• FULFILLMENT OUTBOUND
• LISTED ITEM
• ORDERS
• PRODUCT PRICING
• SERVICES
• SHIPPING

FINANCE

The FINANCIAL_SHIPMENT_EVENT table and its child table, FINANCIAL_SHIPMENT_EVEN_ITEM store shipment events data, such as the order_id, event_type, and quantity_shipped.

The charges or fees associated with these shipment events and items, such as order charges, shipment fees, item charges, item fees, and promotions, is stored in the FINANCIAL_CHARGE_COMPONENT as following:

• For charges related to the SHIPMENT_EVENT table, the corresponding columns in the FINANCIAL_CHARGE_COMPONENT table have the following values:

  • linked_to: SHIPMENT_EVENT

  • linked_to_id: shipment_event_id (_fivetran_id)

  • charge_kind: OrderCharge

• For charges related to the FINANCIAL_SHIPMENT_EVEN_ITEM, the corresponding columns have the following values:

  • linked_to: SHIPMENT_EVENT_ITEM

  • linked_to_id: shipment_event_item_id (_fivetran_id)

  • chargeKind: ItemCharge

Vendor modules

The two modules, A+ CONTENT MANAGEMENT and VENDOR are available for the vendors.

Report tables

We support a set of reports.

Historical sync time frame

When setting up your connection, you can configure the historical sync time frame to speed up the initial sync and subsequent re-syncs. This setting limits the amount of historical data Fivetran syncs for certain tables, thereby significantly reducing sync time.

You can modify the historical sync time frame at any time. If you change it to an earlier date, we perform a full historical re-sync, syncing data back to that new date. If you set it to a later date, we do not delete any existing data. Instead, we apply the new time frame only to subsequent re-syncs.

Authentication

The Amazon Selling Partner connector uses Selling Partner API (SP-API) applications to authenticate with Amazon. You must register a private application in the Solution Provider Portal and provide the application credentials when setting up the connection in Fivetran. For more information, see our setup instructions.

Amazon Selling Partner connections require the following credentials from your SP-API application:

Client secret rotation

Amazon sets a 6-month expiration on app client secrets. You must generate a new client secret for your app client every 6 months and update your Amazon Selling Partner connection to use the new client secret before the current secret expires. If you do not rotate the client secret in time, authentication fails, and the connector stops syncing.

Migration to new authentication method

Fivetran is updating the authentication method for the Amazon Selling Partner connector. Instead of authenticating through the Fivetran app, connections now authenticate using credentials from a Selling Partner app client or a public application listed in the Amazon Selling Partner Appstore.

You must migrate all existing Amazon Selling Partner connections that authenticate using the Fivetran app to the new authentication method before March 31, 2026. Connections that are not migrated by this date will stop syncing data.

Who needs to migrate

You must migrate if your existing Amazon Selling Partner connection authenticates using the Fivetran app. Connections that require migration display a warning message on the connection details page.

Connections that already authenticate using a private Selling Partner application do not require migration.

Migration options

Depending on how you manage the connection and its authentication, you can migrate existing Amazon Selling Partner connections using one of the following options.

Option 1: Migrate using the Fivetran dashboard

Use this option if you manage your connections directly in the Fivetran dashboard.

1. Log in to your Fivetran dashboard and click Connections.
2. Select the connection that requires migration.
3. Go to the Setup tab.
4. In the top-right corner, click the more options menu and select Edit connection.
5. Follow our setup instructions to reauthenticate the connection using the Client ID, Client Secret, and Refresh Token.

Option 2: Migrate using the Fivetran REST API

Use this option if you manage your connections programmatically.

Update the connection with new credentials obtained from the end user by calling the Update a connection endpoint.

curl --request PATCH "https://api.fivetran.com/v1/connections/{connection_id}" \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json' \
  --data '{
    "auth": {
      "client_id": "<END_USER_CLIENT_ID>",
      "client_secret": "<END_USER_CLIENT_SECRET>",
      "refresh_token": "<END_USER_REFRESH_TOKEN>"
    }
  }'

Option 3: Migrate using a Connect Card

Use this option if you want end users to enter credentials through a secure, hosted authentication flow.

1. Update the connection to indicate that credentials will be provided through a Connect Card.

   curl --request PATCH "https://api.fivetran.com/v1/connections/{connection_id}" \
     --header 'Content-Type: application/json' \
     --header 'Accept: application/json' \
     --data '{
       "auth": {
         "client_id": null
       }
     }'
   

2. Generate a Connect Card for the connection.

   curl --request POST "https://api.fivetran.com/v1/connections/{connection_id}/connect-card" \
     --header 'Content-Type: application/json' \
     --header 'Accept: application/json' \
     --data '{
       "connect_card_config": {
         "redirect_uri": "https://www.fivetran.com",
         "hide_setup_guide": false
       }
     }'
   

3. End users enter the required credentials directly in the Connect Card to complete the migration.

Option 4: Migrate using your own Selling Partner application

Use this option if you have a public Selling Partner application and want to authenticate your connections using your own app credentials.

1. Update the connection with your app credentials.

   curl --request PATCH "https://api.fivetran.com/v1/connections/{connection_id}" \
     --header 'Content-Type: application/json' \
     --header 'Accept: application/json' \
     --data '{
       "auth": {
         "client_id": "<YOUR_APP_CLIENT_ID>",
         "client_secret": "<YOUR_APP_CLIENT_SECRET>",
         "application_id": "<YOUR_AMAZON_APPLICATION_ID>"
       }
     }'
   

2. Generate a Connect Card to complete end-user authorization.

   curl --request POST "https://api.fivetran.com/v1/connections/{connection_id}/connect-card" \
     --header 'Content-Type: application/json' \
     --header 'Accept: application/json' \
     --data '{
       "connect_card_config": {
         "redirect_uri": "https://www.fivetran.com",
         "hide_setup_guide": false
       }
     }'
   

3. End users complete authentication through the Connect Card.

Limitations

• We do not sync Personally Identifiable Information (PII) for the ORDERS and SHIPPING modules as Amazon Selling Partner APIs do not return PII for them.
• For vendor data, we can sync the reports only for the marketplace ID you've registered.
• In FINANCIAL_ADJUSTMENT_EVENT tables, records with the same adjustment_type and posted_date share the same hashed primary key (fivetran_id). Since the Amazon Selling Partner API doesn’t provide unique IDs, duplicate events with identical adjustment_type and posted_date (to the millisecond) sync as a single record to the destination.