The question this page answers
Did Amazon accept my authorisation; is my Seller Central account connected to Tightly now, or do I have to go back and try again? This address is the one Amazon sends you back to after you approve the connection. It reads what Amazon sent, once, connects the account straight away, because Amazon's code expires within minutes, and then sends you to Settings under Integrations.
What you see
- 1The empty state's title, on the address itself, when Amazon sent nothing back to read.
- 2The reason, the server's own sentence, printed under the title rather than a code.
- 3Try Again starts the authorisation afresh and leaves for Amazon's consent screen.
While it connects, one line under a spinner:
Connecting your Amazon account…
When the connection is made, a notice says so and you land on the Integrations page:
You have successfully connected Amazon Seller Central. The first sync can take up to a couple of hours.
When it is not, the page stays and says We couldn't connect your Amazon account, with the reason under it: the server's own sentence where it refused the request; where the authorisation Tightly started has expired,
Your session expired. Please reconnect to Amazon.
where Amazon sent you back without the three things a connection needs,
Authorization was cancelled or incomplete.
and otherwise
Something went wrong while connecting your Amazon account. Please try again.
What to do
- Wait; nothing to press while it connects.
- Where it did not connect, press Try Again to start the authorisation afresh and leave for Amazon's consent screen.
- Or, from the Amazon row's drawer on the Integrations page, press Continue to Amazon under the lines saying Tightly reads listings, orders and FBA stock and never reads customer personal data (an unpublished application warning there is expected).
A Continue to Amazon that could not start says, in the drawer:
The Amazon Seller Central connection did not complete; try again.
The address and what Amazon sent are cleared as the page reads them, so a refresh never sends the same code twice. Tightly connects one Amazon account per organisation; a second authorisation reconnects the same one, and a paused or failed connection is set back to connected by it.
When it is empty or failed
A guest who lands here is sent to Sign in with this address remembered, and returns to it after signing in. An organisation still being set up is sent to its setup step: with what Amazon sent, so the connection lands in the wizard, or, where Amazon sent back too little, with the cancelled message. An authorisation started while creating a new organisation is finished on the setup page that started it, not here.