Amazon Is Resetting Who Can Touch Your Seller Central Account
By Archit Mathur · Published · Last updated
Short answer
Amazon replaced the invite-based process for granting Seller Central access to outside providers on 10 August 2026. Providers must verify their approved role coverage by 3 September, and access you granted expires unless you reauthorise by the date Amazon issues to your account. Amazon, not you, now approves which roles a provider may hold.
Most sellers cannot name, without checking, everyone who currently has access to their Seller Central account. The bookkeeper, certainly. The agency, probably. The freelancer who fixed forty listings in 2024 and was never removed, less certainly. A tool trialled once and forgotten, almost never.
That list is about to be rebuilt whether you look at it or not. Amazon changed how outside access is granted on 10 August and attached a deadline to the provider side of it. Do nothing and, on Amazon's own account of the change, the access you have already granted runs out.
Check your own account, not this page
Rollouts like this are staged, and the seller-facing date arrives per account rather than as one public deadline. Everything below is the published shape of the change. The date that binds you arrives in your own Seller Central notifications; your providers see their side of it in the Solution Provider Portal.
What replaced the invite process
Until August, delegating Seller Central access to an outside service ran through a multi-step invite. That was retired on 10 August 2026 and replaced with two routes, set out in the notice Amazon sent to providers and reproduced in full by one of them (opens in a new tab).
| If the service is | How access is granted | Who acts first |
|---|---|---|
| Listed on the Solution Provider Network | An Authorise Now action on the SPN listing, confirmed by the provider on the View All Requests page in the Solution Provider Portal | You |
| Listed on SPN, contacted directly | You contact the service through its SPN listing and grant authorisation once they agree | You |
| Not listed on SPN | The provider copies a unique authorisation link from the Solution Provider Portal homepage and sends it to you | The provider |
The third row is the one that strands people. If a provider you rely on is not on SPN and has not sent you a link, nothing will happen on its own — there is no invite sitting in your account waiting to be accepted, because the invite process is the thing that was removed. Chasing that link is the single highest-value thing on the list.
Two deadlines, and only one of them is yours
Coverage of this change tends to report 3 September as though it were a seller deadline. It is not, and the distinction changes what you are supposed to do with it.
| Date | Whose deadline | What happens |
|---|---|---|
| 10 August 2026 | Passed | Invite-based delegation retired; the routes above go live |
| 3 September 2026 | Your providers | Providers verify and update the Seller Central roles their service is approved to hold |
| Issued per account | You | Reauthorise your providers, or access already granted expires |
The provider deadline still lands on you, one step removed. A role your provider uses today that falls outside their approved set simply will not be there after you reauthorise. Nothing announces which capability went missing. You find out when a task that worked last month stops working, which in October is an expensive way to find out.
Who decides what an outsider may hold
The mechanical description — a new authorisation flow — undersells the change. Previously you assembled an outside party's permissions yourself, picking freely from everything Seller Central exposes, and the judgement about what was appropriate was yours to make and yours to get wrong.
Now the ceiling is Amazon's to set, though it is worth being exact about how. The notice describes the available permissions as the Seller Central roles a provider's service is currently approved for, and providers who need more can submit a request to have additional roles added to their service registration. So it is a propose-and-approve arrangement rather than a fixed menu by category: the provider asks, Amazon decides. Separately, some roles are reserved for the seller's own employees and no service provider can hold them at any tier.
Whether that is an improvement depends on where you sat before. A seller who had granted an agency near-blanket admin because the interface made it the path of least resistance is better off. A seller with a carefully minimal set built by hand may find the pre-approved category set is wider than what they had chosen, which is the failure mode worth watching for at the moment you click through.
How this differs from the 2025 migration
If you lived through the Solution Provider Portal migration last year, this will pattern-match to it and it is a different thing. Velocity Sellers, who managed brands through both (opens in a new tab), make the distinction well: the 2025 change ended shared agency logins and moved outside providers onto token-based, least-privilege authorisation. It changed the mechanism. This one changes who sets the limit.
The Brand Registry change running alongside
Separately, from 29 July 2026 Brand Registry administrators manage selling roles using Account IDs rather than Merchant Tokens (opens in a new tab). This is not part of the solution-provider migration and has its own mechanics, but it lands in the same few weeks and hits the same people — anyone whose brand permissions and Seller Central permissions are administered separately, which is most sellers working with an agency.
The access review worth doing while you are forced to
A reauthorisation event is an unusually good moment to answer a question that otherwise never gets asked: who has access, and would you grant it again today?
Work through it in this order. List every provider with access now. For each, ask whether you would grant that access from scratch this week — if not, do not reauthorise them, which is a decision that costs nothing and needs no conversation. For the ones that stay, read the pre-approved role set rather than accepting it blind, because the whole point of the change is that the set may differ from what they currently hold in either direction. Then write down which provider needs which capability, so that when something breaks in October you can tell a permissions problem from a real one in minutes rather than in a support case.
What a deadline does to a permissions decision
Reauthorisation asks a careful question at the least careful possible moment. The incentive under time pressure runs one way: approve everything, because an over-broad grant costs nothing visible today and a missing permission breaks a shipment during peak. That asymmetry is the problem. A reset that is supposed to narrow access will widen it wherever it is done against a clock, and the resulting configuration is not revisited because nothing ever prompts anyone to look at it again.
Who this actually affects
If you run the account entirely yourself, with no outside party and no third-party tool connected, nothing here changes anything for you today. It is still worth knowing, because the direction is consistent with the rest of 2026: Amazon narrowing who may hold what, and doing it through deadline-bearing migrations rather than through announcements anyone reads.
If you use any outside help at all — and most sellers past their first year do — the exposure is that access lapses quietly at the worst possible moment. It is not a suspension and not a penalty. It is a grant that ran out.
A deadline that reaches you through somebody else
Look at the shape of this one. The date carrying the consequence sits on your providers' side, in a portal you cannot see. The date that binds you arrives on Amazon's schedule rather than yours. And there is no counter anywhere in Seller Central telling you that three of your five providers are unreauthorised and one of them books your inbound shipments.
It is the same pattern as every fee change and every payout change this year. The information exists. It is even published. Nothing carries it to the person whose quarter depends on it.
Frequently asked questions
What changed with Amazon Seller Central provider access in August 2026?
From 10 August 2026 Amazon retired the legacy invite-based process for delegating Seller Central access to solution providers. Two paths replace it: an Authorise Now action on a provider's Solution Provider Network listing, which the provider confirms in the Solution Provider Portal, or a unique authorisation link the provider generates and sends you directly if their service is not listed on SPN.
What is the 3 September 2026 Amazon deadline?
It is a provider-side deadline, not a seller one. Solution providers must verify and update their role coverage - which Seller Central roles Amazon has approved for their service - by 3 September 2026. Anything a provider relies on today that sits outside what Amazon has approved for them simply will not carry over when you reauthorise.
Will I lose access to my Amazon account if I do nothing?
You will not lose your own access. What expires is the access you granted to outside service providers, if you do not reauthorise them by the deadline Amazon communicates to your account. Confirm that date in your own Seller Central notifications: it is issued per account rather than published as one public deadline.
Can my agency still hold the same Seller Central permissions?
Not necessarily. You no longer assemble the permission set yourself from everything Seller Central offers. It comes from the roles Amazon has approved for that particular service, and a provider needing something outside that list has to ask Amazon for it. Some roles are reserved for the seller's own employees and no service provider can hold them.
What replaced merchant tokens for Brand Registry selling roles?
Account IDs. From 29 July 2026, Brand Registry administrators manage selling roles using Account IDs instead of Merchant Tokens. This is a separate change from the 10 August solution-provider migration, though the two landed weeks apart and affect overlapping people.
How do I check who currently has access to my Amazon account?
In Seller Central, under Settings, User Permissions lists current users and their roles; third-party service authorisations are managed separately under the Manage Your Apps and authorisation screens. Review both, because a provider can appear in one and not the other depending on how access was originally granted.
Sources
- 01Amazon Solution Provider Services: New Seller Central Authorisation Process Starting 8/10/2026 (opens in a new tab) — EcomRanker, reproducing Amazon's Solution Provider Portal notice
- 02Use Account IDs to manage selling roles after 29 July (opens in a new tab) — Amazon Seller Forums
- 03
Get told automatically
Amazon emits a notification when your seller account moves between normal, at-risk and deactivated. Notifcentral subscribes to it and pushes the change to your phone within about a minute, including when the account returns to good standing. This is the alert that reaches you when you are not logged in.
How account health alerts work →notifcentral
Fee changes, buy box, listing issues, held funds, reimbursement recovery, payout confirmations - delivered to your phone before any of it costs you money.
Alerts
Compare
Guides
© 2026 Notifcentral