The Openbridge Amazon Seller Central data connector allows you to tap into inventory, order, returns, and a host of other information. 

This guide will walk you through the process to activate your Amazon Seller Central data feed to a target data lake or warehouse.

If you already have an Openbridge account, you can skip to Step 2.

Creating an account and attaching BigQuery (or another destination) are detailed in these two links;

BigQuery is where we store your data. However, you can choose Amazon Athena, Amazon Redshift, or Amazon Redshift Spectrum as a destination! BigQuery is not required, just used as an example for this guide.
​
If you want to attach an existing BigQuery instance, or any other supported destination data lake or warehouse, check out our setup docs for data lakes and warehouses:

Let’s get started!

One of the first steps you will take is to log in with your Openbridge account. This will verify everything is set up correctly and you have access to the system: The link and credentials are as follows:

Once you log in, you will see your account info in the top nav. This tells you that the system has logged you in. It will also display some new navigational elements for management and setup. If you click “Sources” you will see a collection of options. Select any of the Amazon Seller Central (MWS) data connectors.
​
If you are not sure which to select, we details the different options here: https://docs.openbridge.com/en/articles/3667338-amazon-mws-and-advertising-data-feed-list
​

Go to the Amazon Seller Central activation page: 

This page allows you to activate your data feeds. One of the first things we need to have you do is authorize our connection. For us to connect Amazon a seller must authorize Openbridge to make calls to the Amazon MWS API on the seller's behalf. The process is simple enough and should take a minute.

Here are the steps to authorize Openbridge as a developer within the Amazon Seller Central web site:

You will see an initial authorization page. Enter a name, say "openbridge", and then the developer ID for the correct marketplace as shown above:

You will see a confirmation page. Click "Next".

If all goes well, Amazon will provide an MWS Auth Token.  Below is a screenshot that contains your Seller ID and MWS Auth Token.  Take note of both and keep them safe. We will need both in our next step.
​

 Make sure you are on the activation page for Openbridge from Step 3. This is where you enter your MWS credentials:

You will need your MWS Auth token as shown below, along with your Seller ID. The screen below highlights the information we need:
​

Once you add this information, it will show up as an "Existing Amazon Identity". Select the identity and continue.
​

This is the last step! 

You need to provide a label for this subscription. Typically, you would want to use something that aligns with the connected Amazon Seller Central account. If you have multiple data connectors for different Amazon Seller Central accounts, this will ensure you can easily identify which connector belongs to a given seller account. 

Lastly, you need to select the target destination. This is where you want us to store the data from the Amazon Seller Central API. 

Once you are done, review the information for accuracy, then click the "Pay and Launch" button.
​

That’s it! 

After you complete the order you will see a "Thank You" page and get a confirmation email. Your order will be processed according to the specific frequency and format described in our docs. For Amazon Seller Central, the collection frequency is once daily. This is in accordance with Amazon API limits. 

To see the list of the MWS Marketplaces we support, go here.
​

Currently, we are pulling data once a day. Again, this largely a function of the limits Amazon has on how frequently calls to their API can occur. Given we are pulling a broad cross-section of reporting data, making those calls more frequently would cause Amazon to throttle our connection to your account.

Based on our testing, Amazon does not consistently have data available when we call the MWS API. For example, we may call the API for export "X".  Amazon will respond to our request saying there is no data available for "X".  We will attempt a series of retries over a number of hours, within API limits, to retrieve "X".  As a result, there may be some inconsistency in how Amazon is making data available which limits our ability to collect it on your behalf.

In some cases, Amazon will not return any data because there is no data. For example, if there are no customer returns, Amazon will not return any data for the customer returns data feed. Likewise, if all your listings are inactive, your active listings feed would not contain any data.