Amazon Already Replaced Merchant Tokens With Account IDs. Here's How to Find Yours Before It Blocks Your Selling Roles

If you administer selling roles for a brand on Amazon, the identifier you've been using to do it stopped working weeks ago, and Amazon's announcement about it only went out afterward. Merchant Tokens, the identifier Brand Registry Administrators previously used to assign and modify selling roles, were replaced by Account IDs effective July 29, 2026. This is not upcoming, it already happened.

The Problem: Merchant Tokens Were a Fragmented System

Selling roles are what actually grant access to brand selling benefits, A+ Content, Stores, and Vine among them. Managing who has those roles previously ran through Merchant Tokens, and any Brand Registry Administrator handling multiple accounts or multiple marketplaces had to track a separate Merchant Token for each one. There was no single identifier tying a brand administrator's access together across regions, just a fragmented set of tokens that had to be individually tracked and referenced correctly every time a role needed to change.

What's Actually Changing

Per Amazon's August 5, 2026 seller news announcement, Brand Registry Administrators now use a single Account ID instead of Merchant Tokens to assign or modify selling roles, effective July 29, 2026.

The specifics worth knowing exactly:

• This affects three groups directly: Brand Registry Administrators, anyone who currently has a selling role assigned, and anyone who wants a selling role to access brand selling benefits.
• Account IDs are a single, worldwide identifier, replacing the need to manage separate Merchant Tokens per account or region.
• The change took effect July 29, 2026, roughly a week before Amazon's announcement was published, meaning any administrator who hasn't already located their Account ID has potentially been unable to correctly assign or modify selling roles using the old method during that gap.

Why Amazon Is Doing This

The stated rationale is straightforward simplification: one worldwide identifier is easier for administrators to manage than a separate Merchant Token per account, and it removes a real source of administrative error, using the wrong token for the wrong account or region.

There's a broader pattern worth naming too. Amazon has been steadily consolidating identity and account management systems across its seller-facing infrastructure, moving toward unified identifiers rather than context-specific tokens scattered across different tools and regions. A single Account ID model is easier for Amazon to build consistent permissions, security, and audit tooling around than a patchwork of Merchant Tokens tied to specific legacy contexts. This kind of infrastructure consolidation usually serves Amazon's own platform maintenance and security posture as much as it serves seller convenience, both things can be true at once.

How This Impacts Sellers

The upside, once you've made the switch, is real. A single Account ID per administrator, valid worldwide, is a genuine simplification if you have previously had to track multiple Merchant Tokens across accounts or marketplaces. Fewer identifiers to manage means fewer opportunities to use the wrong one when assigning a role.

The risk is entirely in the transition gap. Because this change took effect before the announcement was widely published, any Brand Registry Administrator who was not actively watching Seller Central news may not yet know their old workflow no longer applies. If you or someone on your team has tried to assign or modify a selling role recently and it didn't work as expected, this is the likely reason, not a bug or a permissions issue elsewhere.

Brand selling benefits are the real stakes here, not just an administrative inconvenience. A+ Content, Stores, and Vine access all depend on selling roles being correctly assigned. If a role assignment silently failed or stalled because of this transition, the practical effect is lost access to features that directly affect conversion and brand presentation, worth checking immediately rather than assuming everything is still working as it was in June.

If You Administer Roles for Multiple Brands

Administrators managing several brands or agency clients face a slightly larger version of this same problem. Previously, each brand relationship may have involved its own Merchant Token, multiplying the tracking burden across a portfolio. A single worldwide Account ID per administrator changes that math meaningfully, one identifier covers your access across every brand you administer, rather than a token per relationship.

That consolidation cuts both ways worth flagging: a single Account ID also means a single point of failure for access across your entire portfolio if that identifier is ever compromised or misconfigured. Treat safeguarding your Account ID with the same seriousness you'd apply to any other credential controlling access to multiple client accounts, not as a minor administrative detail.

What to Do Right Now

If you're an Account Owner, find your Account ID with these exact steps:

1. Click the gear icon at the top of the Seller Central page.
2. Select Settings.
3. Select Manage Accounts.

If you're not sure who your Account Owner is, find out with these steps:

1. Go to User Permissions.
2. Check for the user displayed as "Owner" under "Account Role."
3. If User Permissions isn't available to you, contact your Seller Central account Administrator and request access.

Beyond just locating the ID, do these three things this week:

• Confirm with your Brand Registry Administrator that any selling role changes made or attempted since July 29 actually went through correctly, rather than assuming silence means success.
• If you manage brand selling benefits across multiple accounts or regions, consolidate your reference documentation now, replace any internally stored Merchant Token references with the correct Account ID equivalents so your team isn't working from outdated instructions.
• Check A+ Content, Stores, and Vine access specifically for any brand where a role change was pending or recently made, since these are the features that depend directly on selling roles being correctly assigned.

Amazon's Brand Registry selling roles help page has the full reference documentation on how selling roles and Account IDs work together, worth reviewing directly if you administer roles for more than one brand or account.

Where This Fits Into Broader Brand Registry Management

Selling roles and Account IDs are the administrative layer underneath the brand benefits sellers actually care about day to day. Our coverage on AI-optimized A+ Content covers one of the specific benefits that depends on having a correctly assigned selling role in the first place, worth reading once you've confirmed your Account ID and role status are current. Amazon has also been tightening requirements around A+ Content more broadly, our piece on Amazon's AI-generated people tagging requirement covers a related but separate compliance change worth knowing about if you manage A+ Content for a brand.

For broader context on how large platforms are consolidating identity and account management systems generally, Harvard Business Review's coverage of digital identity infrastructure is a useful outside perspective on why this kind of unification tends to happen at scale, beyond Amazon specifically. Marketplace Pulse also tracks Amazon's seller-facing infrastructure changes at a platform-wide level over time.

Frequently Asked Questions

Do I need to do anything if I'm not a Brand Registry Administrator?

If you have a selling role assigned, or want one to access brand selling benefits, this affects you indirectly, your administrator now uses your Account ID rather than a Merchant Token to manage that access, so it's worth confirming your role status is current with them.

Will my old Merchant Token still work for anything?

Amazon's announcement does not indicate a grace period or dual-support window, the framing is that Account IDs are now used in place of Merchant Tokens for this purpose, effective July 29, 2026. Treat the Merchant Token as no longer the correct identifier for assigning or modifying selling roles.

What happens if I can't find my Account Owner and don't have User Permissions access?

Contact your Seller Central account Administrator directly and request access, per Amazon's own guidance. There isn't a self-service path around this if you don't already have User Permissions visibility.

Does this affect A+ Content, Stores, and Vine access directly, or just the administrative process?

Both. The administrative process changed, but because those brand selling benefits depend on correctly assigned selling roles, a role assignment that failed or stalled during this transition can directly affect your access to those features, not just the mechanics of who administers them.

Is this a global change or specific to certain marketplaces?

Account IDs are described as a single, worldwide identifier, meaning this change applies across marketplaces rather than being region-specific, which is part of the stated simplification benefit.

Takeaways

• Amazon replaced Merchant Tokens with Account IDs for managing Brand Registry selling roles, effective July 29, 2026, already in effect before the announcement was published.
• This affects Brand Registry Administrators, anyone with a selling role, and anyone seeking one for brand selling benefits like A+ Content, Stores, and Vine.
• The real risk is the transition gap, any role changes attempted since July 29 using old assumptions may not have gone through correctly.
• Finding your Account ID takes three clicks from Settings, finding your Account Owner takes checking User Permissions or contacting your administrator.
• Check A+ Content, Stores, and Vine access directly for any brand with a recent or pending role change, since these features depend on the role being correctly assigned.

For ongoing coverage of Amazon Seller Central and Brand Registry updates, see our newsletter, and check our free tools for listing and margin calculators worth running once your brand selling benefits are confirmed active.