Connect Amazon Seller Central to Rig

Check you have access

Two things have to be true before any of this works, and they fail differently. Check both before you start filling in forms.

• A Professional Seller plan. Individual plans have no Selling Partner API access at all, and no amount of correct setup works around it.
• You are the Primary User of the Seller Central account. Amazon only lets the Primary User authorise an application against the account, so ordinary admin access is not enough here even though it is enough for everything else in Seller Central.

Register as an Amazon developer

You register once, Amazon reviews it, and roughly 72 hours later they email a decision along with the link you use to create the application. Nothing else on this page can happen until that clears, so start it early rather than saving it for the onboarding call.

Start the developer profile

1. Sign in to sellercentral.amazon.com as the Primary User.
2. Open the hamburger icon at the top left, then Apps and Services → Develop Apps.
3. Click Get started on the right, then complete the two-step verification and submission process.
4. Select the seller account you are registering for.
5. Name the developer profile. Rig Data Sync is the name we use, and it is worth using something recognisable because you will be looking for it again in three days.
6. Work through Authenticate all emails, which covers the address you are signed in with and any secondary addresses on the account.
7. Fill in the business information.

Choose your data access roles

• If Amazon asks what you need the application for, to create SP-API keys is a complete answer.
• Brand Analytics, Product Listing and Pricing are necessary. Select more depending on the kind of information you want to use in Rig.
• Leave out the restricted roles.

Click Register.

When it goes through, the page tells you the registration is under review. Amazon emails their decision in roughly 72 hours, and that email carries the link you need for the next section.

Get your credentials

Rig needs a client ID, a client secret and at least one refresh token. All three come out of an application you create once the approval lands, and you can collect all three yourself.

Create the client app

1. Follow the link in Amazon's approval email, or go back to Apps and Services → Develop Apps, the same path you used to register.
2. Create the application.
3. For the app type, select Production rather than Sandbox. The sandbox returns mock responses, so a connection built against it looks healthy and carries nothing real.

Get the client ID and secret

1. Find the application in the list and choose Edit app.
2. Under LWA credentials, choose View.
3. Copy the client ID. It starts amzn1.application-oa2-client.
4. Copy the client secret from the same place, and treat it like a password.

Authorise the app for a refresh token

1. Open the Authorize application page for that application.
2. Choose Authorize app for the selling partner account you want Rig to read. A refresh token appears on screen. They start Atzr|.
3. Repeat for each region you sell in.

Generating a new refresh token does not invalidate the ones you already hold, so re-running this will not break a working connection. An application does have a maximum number of authorisations, and that ceiling cannot be raised once you reach it.

Connect it in Rig

1. In Rig, open Connections and go to Sources & actions.
2. Search for Amazon Seller Central and open the card.
3. LWA client ID and client secret: from the application you just created.
4. Refresh token: the EU token, the US token, or both.
5. Marketplace IDs (optional): leave blank. Rig discovers your marketplaces from the authorisation itself on this path.
6. Days of history to pull: defaults to 90.
7. Click Test, then Sync.

What Rig pulls in

Amazon lands in an amazon_sp_api schema. Every row is tagged with its marketplace, so multi-market sellers can split or combine as they like.

• Orders and order items
• Financial transactions
• Marketplaces
• FBA inventory, including aged inventory
• Listings
• Sales and traffic
• Subscribe and Save
• Search query performance, from the Brand Analytics role
• Amazon-fulfilled shipments, which needs the restricted Tax Invoicing role and so stays empty unless you deliberately took it

Two limits are Amazon's rather than Rig's. Search query performance is retained for about 16 months on a rolling basis, so older weeks are simply not available. Sales and traffic is off by default: it costs a report per marketplace per day against a shared, tight budget, so ask us to enable it rather than assuming it is missing.

Troubleshooting

• Nothing works and the account looks fine: check the seller plan. Individual plans have no API access at all, and this is the single most common cause.
• The registration form will not submit: check the web link field. Amazon requires the scheme, so https:// has to be there.
• One marketplace is empty and the others are fine: that is usually correct rather than broken. Rig skips a marketplace your account cannot reach and carries on with the rest, so a genuine bug shows up as every marketplace failing, not one.
• Search query performance is missing: the application does not hold the Brand Analytics role. Roles are set during registration, so adding one means going back through Amazon's review.
• Connected successfully but every sync fails: an incomplete credential set. Confirm the client ID, the client secret and at least one region refresh token are all present.
• Older search query weeks never appear: Amazon retains search query performance for roughly 16 months on a rolling basis, so older weeks are no longer available from Amazon at all.