Amazon Replaces the Seller Central Invite Process With a New Service Provider Authorization Flow on August 10, 2026 — Providers Must Confirm Role Coverage by September 3 or Sellers Reauthorize Into Narrower Access
Amazon told solution providers that starting 8/10/2026 it is changing how sellers delegate Seller Central access to third-party services, retiring the multi-step invite process in favour of a single streamlined authorization flow. For services listed on the Service Provider Network after that date, a seller can authorize either by choosing Authorize Now on the SPN listing — which creates a service request the provider confirms in Solution Provider Portal — or by opening a unique authorization link the provider generates in SPP and sends directly. The authorization is scoped to the roles the service is currently approved for, is adjustable by the seller before confirmation, and runs for 365 days. Amazon asked providers to verify and update their role coverage before 9/3/2026, and told them that sellers who do not reauthorize by Amazon's deadline will see existing access to their Seller Central accounts expire.
Real-World Impact
Because Amazon's documentation puts the authorization term at 365 days, a seller who reauthorizes an agency on 9/3/2026 — the date Amazon gave providers for confirming role coverage — is granting access that runs to roughly 9/3/2027 and covers only the roles that agency is approved for at the moment of confirmation, not whatever the old invite happened to include.
Key Points
- Amazon's notice to solution providers states that starting 8/10/2026 the current invite process for delegating Seller Central access is replaced by a new, streamlined authorization process
- Path one — the seller opens the service's Service Provider Network listing and chooses "Authorize Now", which creates an SPN service request that the provider must confirm on the View All Requests page in Solution Provider Portal before the authorization activates
- Path two — the provider generates a unique authorization link in Solution Provider Portal and shares it with the seller directly by email or message, and the seller authorizes from that link
- The authorization covers only the Seller Central roles the service has been approved for based on its service category; the seller can optionally adjust individual roles or restrict access before confirming
- Sellers can use a country/region filter during authorization to scope a provider's access geographically rather than granting every marketplace
- Amazon's documentation states the authorization is good for 365 days, making provider access time-bound rather than open-ended
- Amazon asked providers to verify and update their role coverage before 9/3/2026 so access is not interrupted — a role the service is not approved for at reauthorization time is not carried over
- Amazon's notice states that sellers who do not reauthorize by Amazon's deadline will see all existing access to their Seller Central account(s) expire
- Once authorized, providers delegate access to their own staff inside Solution Provider Portal rather than sharing seller logins or secondary user accounts
What You Should Do Now
- 1Inventory every third party that currently touches your Seller Central account before the reauthorization prompts arrive, so you can tell a legitimate request from a phishing attempt that imitates one
- 2Ask each provider to confirm in writing that their role coverage is verified and updated ahead of 9/3/2026 — if a role they rely on is not approved by then, your reauthorization silently hands them less access than they had
- 3Treat reauthorization as a permissions audit rather than a click-through: drop roles the provider does not need and use the country/region filter to limit them to the marketplaces they actually work in
- 4Authorize only through the provider's SPN listing or a link you confirmed with them through a channel you already trust, never through an unsolicited email link
- 5Diary the 365-day expiry for each authorization you grant so a provider's access does not lapse unnoticed in the middle of a peak season
- 6If any provider is still working through a shared login or a secondary user account, move them onto Solution Provider Portal access and close the shared credential