Connect Amazon Seller

Register in the Solution Provider Portal

1. Open the Solution Provider Portal, read the general guidance, tick the agreement, and click Acknowledge & Continue.
2. On Enroll in New Program, choose your actual Seller Central business account, not any entry prefixed BR; those are Brand Registry records, and they are not the seller entity the API needs.
3. Amazon congratulates you on being able to create sandbox apps. Sandbox is not the goal; production data needs the identity-verified path. Click Get Started under identity verification.

Identity verification

1. Submit your business registration information and an identity document.
2. Amazon analyses them and may email follow-up questions within 2 business days. This is the wait to start early; the rest of this page continues once it clears.

Complete the Solution Provider Profile

Once identity is verified, the portal opens the Solution Provider Profile. Contact details are your real business details. For the Data Access dropdown, choose the private option: "Private Solution Provider: I build application(s) to integrate my organization with Amazon APIs". You are integrating your own business, not offering an app to others.

Under Roles, select exactly three: Inventory and Order Tracking, Finance and Accounting, and Amazon Fulfillment. Skip every restricted or PII role; the dashboard never needs buyer names, addresses, emails or phone numbers.

Two textboxes want a written answer. For the primary business activity:

• The Security Controls checklist wants truthful answers about your own practices; for a founder running Abaxar on their own machine with a password manager and disk encryption, the honest answer to each is normally Yes.
• Tick the agreement and click Register. Developer Central then shows your registration as under review; approvals have come back in minutes, but Amazon can take longer and can ask for clarification.

Create the production app client

1. Once the developer review clears, open Developer Central and click Add new app client.
2. Name it something recognisable (2 to 40 characters), for example your brand plus Dashboard.
3. API Type: SP API. App Type: Production. Business entities supported: Sellers, with Vendors unchecked.
4. When the Sellers roles appear, select the same three: Finance and Accounting, Inventory and Order Tracking, Amazon Fulfillment.
5. For the PII delegation question, answer No: you will not delegate access to PII to another developer’s application.
6. Click Save and exit. The app row appears with status Draft; Draft is fine for private self-authorization.

Copy the credentials and self-authorize

• "This account does not contain an entity supported by the app" here means one of four things: the app doesn’t have Sellers ticked, the browser is signed into the wrong Amazon account, you aren’t the Seller Central primary/admin user, or the seller account is on the Individual plan. The Individual plan is the usual culprit, and upgrading to Professional makes the seller entity appear.

1. On the app row, open LWA credentials → View, and copy the client id and client secret.
2. Open the dropdown to the right of Edit App and click Authorize.
3. Manage Authorizations shows your seller account with an Authorize app button. Click it, and copy the refresh token it generates.

Enter the values in Abaxar

You only type the four values Amazon’s portal actually shows, and they all sit on the Developer Central app row: the App ID (it starts amzn1.sp.solution), the LWA client id and secret, and the refresh token. Abaxar detects the rest (the region code, the regional endpoint and the marketplace id) from the saved credentials.

• If detection couldn’t run (an Amazon outage, or a wrong credential), the keys still save, the card says what failed, and the Auto-detect button beside Run backfill retries it. The three region values can also be entered by hand under the card’s "Detected automatically — override" section; the full per-marketplace table is in the runbook that ships with the product.

1. In Abaxar, open Settings → Connectors and find the Amazon card.
2. Fill in the four fields and click Save Amazon keys. Saving in stages is fine; already-saved fields read Saved, and the card lists what is still missing.
3. The card then checks the three Amazon regions and fills in the region, endpoint and marketplace id itself, reporting what it found, for example "Detected amazon.co.uk (UK) — eu region." If you sell in several countries it lists them and asks you to pick your home marketplace (the country you registered your seller account in), then Save selection.
4. Once everything is saved the badge flips to Credentials saved. Click Verify.
5. Choose the backfill window and click Run backfill.

If something looks wrong

• No recent orders is not a broken connector. A seasonal or paused account legitimately returns nothing for recent dates; backfill a historical window you know contains orders before concluding anything failed.
• A report coming back CANCELLED is Amazon saying "this report has no rows", not an error. An account with no FBA stock sees some FBA reports answer CANCELLED every time, while the others fill normally.
• A role added later (for example to light up an optional feed a run warning names) doesn’t reach the existing token by itself: reopen the app in the portal, add the role, save, and Authorize again for a fresh refresh token.

Set up the next connector