Support › Getting started › Connecting Amazon
Connecting your Amazon Seller account
TrueBooks talks to Amazon through the Selling Partner API (SP-API). The connection takes a minute, and you'll authorise it inside Seller Central — not by handing over a password.
Pick the right region first
Amazon splits Selling Partner accounts into three regions, and each one lives on a different SP-API endpoint. Before you click Connect, choose the region your seller account is registered against:
| Region | Marketplaces it covers | Sign-in domain |
|---|---|---|
| Europe (EU) | UK, DE, FR, IT, ES, NL, SE, PL | sellercentral.amazon.co.uk |
| North America (NA) | US, CA, MX | sellercentral.amazon.com |
| Far East (FE) | JP, AU | sellercentral.amazon.co.jp |
If you sell across more than one region, connect them as separate Amazon accounts in TrueBooks — settlement reports are scoped to a region and TrueBooks treats each connection independently.
The connection flow, step by step
- In TrueBooks, open Settings → Account and click Connect Amazon.
- Pick your region and click through.
- You'll be sent to Seller Central. Sign in if you aren't already.
- Amazon shows the authorisation screen — it tells you exactly which scopes TrueBooks is asking for (settlement reports, finances). Click Confirm.
- Seller Central redirects you back to TrueBooks. Within a couple of seconds the connection appears in your account list with the marketplaces it covers (e.g. "Amazon UK · Amazon DE · Amazon FR").
That's it — TrueBooks will now check for new settlement reports automatically. The first one usually shows up the day after Amazon disburses to your bank.
What TrueBooks can and can't do over SP-API
It's worth knowing the boundary: SP-API only lets us read settlement reports Amazon has already generated. We can't ask Amazon to make a brand-new settlement file for an arbitrary date range, and we can't change the 14-day disbursement cycle. What we can do is fetch any existing reports Amazon has on file (it keeps them for ~90 days) and pick up any reports you ask Amazon to regenerate from Seller Central. There's a separate guide on backfilling history that walks through both.
Reauthorising or disconnecting
Amazon's authorisations sit on top of refresh tokens that don't expire on a fixed schedule, but they can be revoked — by you, by an Amazon-side policy change, or by a password reset. When that happens, TrueBooks marks the connection as Reconnect required in Settings → Account, no settlements come in, and the next-sync job logs the failure.
To reconnect, click Reconnect on the connection row and run through the SP-API authorisation again. Existing settlements stay in your account — only the live link is being re-established.
To disconnect cleanly: click Disconnect. TrueBooks revokes the token with Amazon first, then zeroes the credentials in our database. Existing imported settlements remain visible and posted invoices stay in Xero; we just stop pulling new ones in.
If the redirect fails
The most common failure is the redirect bouncing without completing — usually because the browser blocked third-party cookies on Seller Central, or because you signed into the wrong Amazon account in another tab. Try in a fresh private/incognito window with only your seller-central tab open. If you see a specific error code in the URL bar, copy it and email support — that gives us enough to trace it.