Running Multiple Amazon Seller Accounts: What Amazon Actually Allows

Most people who search for "multiple Amazon seller accounts" aren't trying to pull anything. They're a brand owner who just bought a second, unrelated brand. Or an agency with eleven clients in Seller Central. Or a manufacturer who makes products for two companies that have nothing to do with each other. Their real question is simpler and more nervous: if Amazon sees these accounts as connected, will it take them all down?

This post answers it: when multiple Amazon seller accounts are allowed, the official tools, why Amazon looks for related accounts, and what to do when a notice arrives.

A quick note on who's writing. We build JustBrowser, an antidetect browser, so you might expect a post about hiding accounts from Amazon. It isn't one. Hiding accounts Amazon hasn't approved is a terms violation, and bad business besides.

(There's a short section further down on where a browser like ours actually fits. It's narrower than the category's marketing — ours included — makes it sound.)

Who legitimately works across multiple Amazon seller accounts

Before the rules, the cases that keep coming up in seller forums:

Multi-brand owners. You run two or more brands as genuinely separate businesses, often separate companies, with their own books, staff and suppliers.
Aggregators. You've acquired brands that came with their own Seller Central accounts and their own histories.
Manufacturers and private-label producers selling on behalf of two distinct companies.
Agencies and freelancers who don't own any of the accounts but work inside many of them.
Staff inside one business — a finance person, a listings person, a customer-service team — who all need access to the same account.

Only the first three are about owning more than one account. The last two are about access. Amazon handles those completely differently, and a lot of trouble starts when someone treats an access problem as an ownership problem.

Multiple Amazon seller accounts: what Amazon's policy allows

Amazon's seller policies (the Seller Code of Conduct and the related help pages in Seller Central) start from a default: one Seller Central account per selling region. A region can cover several marketplaces, so a seller in North America, for instance, can list in more than one country from a single account rather than opening one per country.

A second account in the same region is allowed when there's a legitimate business need. The examples Amazon has given over the years are the ones above: separate brands run as separate businesses, or a manufacturer producing for two distinct companies. Each account has to be in good standing on its own, and each has to serve a real, separate business purpose.

What doesn't count as a business need is clearer: an account opened to get around a restriction or deactivation on another one. Sellers also report that a second account used to put duplicate offers on the same products, or to leave poor metrics or reviews behind, gets treated the same way. Check Amazon's current guidance for your case.

We won't quote the exact wording or say whether you must file a request first. Amazon has changed that procedure before. Read the current "multiple accounts" guidance in Seller Central's help pages, and if your situation is unusual, ask Seller Support before opening anything. A written answer from Amazon beats any forum thread.

Amazon's help pages don't make it obvious whether the request step applies to every case, which is why forum advice on this topic so often disagrees.

Amazon doesn't publish how its related-account matching works, and anyone claiming to know the exact model is guessing. What sellers commonly report is that Amazon looks for overlap in the things that identify a business: legal entity and tax details, bank and payment information, business and return addresses, contact details, and device or login information.

The why is more useful than the how.

When Amazon deactivates a seller for counterfeits, fake reviews or a consistently bad customer experience, the cheapest move for that seller is to come back under a new name next week. Related-account detection exists to stop that loop. Honestly, if you've ever received a fake product from Amazon, you've been on the receiving end of the problem it's trying to solve.

Amazon isn't trying to stop a business having two brands. It's trying to stop a bad account having a hidden twin. So when one of your accounts gets into trouble, any related account can be pulled into the review. That's the real risk for legitimate operators, and it has nothing to do with fingerprints. It's whether every one of your accounts is clean.

The official ways to do this

Here's the part most guides skip, because there's nothing clever about it.

User Permissions in Seller Central. The account owner can invite other people with their own logins and choose which areas each person can view or edit. This is how staff and agencies are meant to get in. Every person signs in as themselves, and the owner can remove access in a minute when someone leaves.

Selling Partner API authorization. Repricers, inventory tools, analytics dashboards and agency software connect through Amazon's Selling Partner API with the seller's authorization. No password changes hands.

Brand Registry users. If you own a registered brand, Brand Registry lets the rights owner add other people, such as an agency or outside counsel, to help manage the brand. Again, through their own logins.

A second account, where the business need is real. For multi-brand owners and aggregators, the legitimate route is to keep each account tied to the business it belongs to and to be ready to explain the structure if Amazon asks.

Sharing the owner's password sits on the wrong side of all this. It erases the record of who did what, and one leaked password exposes the whole business.

Aggregators: document the separation, don't disguise it

Aggregators have the hardest version of this problem, because centralising things is the whole business model. One finance team, one legal team, sometimes one operations lead across a dozen acquired brands.

The instinct some aggregators have is to make the brands look unconnected. That's backwards. A common parent company is a perfectly legitimate reason for accounts to be related. What Amazon wants to know is whether each account is a real, separate business in good standing. So:

Keep each brand's account tied to the legal entity that actually runs it, with accurate business, tax and banking details for that entity.
Keep a document pack per brand ready: incorporation papers, tax registration, bank letters, trademark records and the acquisition paperwork that shows how the parent relates to it.
Treat account health as a portfolio risk. One brand with a quality problem can drag related accounts into a review, so a weak brand needs fixing, not hiding.

Look, the paperwork is tedious. But when a notice arrives, a clear, documented explanation sent the same week beats a year spent making accounts look like strangers.

Strong opinion, since we're here: for an aggregator, that document pack is worth more than any tooling decision you'll make this year. Ours included.

Agencies: work in client accounts the way Amazon expects

Agencies don't own the accounts they manage, so the question isn't "how many accounts can we have". It's "how do we work in many clients' accounts without making a mess".

The baseline: every staff member gets their own invite from each client through User Permissions, with only the access their job needs. Tools connect through the API, authorized by the client. When a client leaves, they revoke access.

None of which is news. Shared logins are still the default in a lot of agencies, and another paragraph about audit trails has never once talked anyone out of it. Write it anyway, apparently.

The day-to-day risk is usually human error: a pricing file uploaded to the wrong client because three Seller Central tabs shared one browser window, or a junior account manager still signed in to a client who left. That's where a profile-per-client setup earns its keep.

Where an antidetect browser fits, and where it doesn't

An antidetect browser gives each profile its own fingerprint, cookies, storage and proxy settings, and keeps them apart. We'll be direct about what that's good for on Amazon, and what it isn't.

It isn't a way to make accounts Amazon hasn't approved look unrelated. Using it for that breaks Amazon's terms, and it wouldn't address the business, tax, bank and address details that make accounts related in the first place. If an account exists to get around a deactivation, no browser changes the outcome, and you shouldn't want it to.

It is useful for legitimate separation:

One profile per client or per brand, so sessions, cookies and saved logins never mix, and nobody acts in the wrong account by accident.
Team access under permissions. JustBrowser lets you share a profile with a teammate as view-only or launch, with owner, admin, member and viewer roles. Team seats are free, and a seat runs only the profiles shared with it, which is the right shape for "this account manager handles these three clients".
Checking listings in other marketplaces. A profile set to a German locale and timezone, routed through a proxy you supply, shows you roughly what a shopper on amazon.de sees. That's useful QA and ad-verification work. (JustBrowser doesn't include proxies; you bring your own.)
Automation. The local REST API and CDP connection let your own scripts drive profiles with Playwright, Puppeteer or Selenium. For anything that touches Seller Central data, Amazon's own Selling Partner API is still the right tool.

If you already run Multilogin or AdsPower for this and it works, there's no reason to switch mid-quarter. Comparisons and current pricing for each are on their own sites and on our comparison page. JustBrowser is one plan: $9.99/month or $99.99/year with unlimited profiles, a 7-day free trial (card required, cancel inside the seven days and you aren't charged), and it runs on Windows x64 and macOS (Apple Silicon). Our antidetect myths post covers what these browsers can and can't do in more depth, the agency and team FAQ goes into seats and sharing, and our affiliate multi-account guide covers the same questions for ad networks.

Separately, some teams use click fraud protection for their own ad traffic and privacy-first analytics on the brand's own site.

First, don't ignore it, and don't open a new account. Here's the order that tends to work.

Read the notice and Account Health. The notice and the Account Health page in Seller Central will usually say what Amazon is concerned about and where to respond. Respond from the account that received it.

Work out the real connection. If Amazon names or hints at another account, figure out honestly why the two are connected. Often the answer is legitimate (a shared parent company, a shared agency, a former employee) and sometimes it's a genuine problem with the other account.

Write a plain appeal. Amazon's appeals generally ask for the root cause, what you've already corrected, and what will prevent a repeat. Lead with the facts, attach the documents that back them up, and skip the essay. Reviewers read a lot of these. A short, specific appeal gets a better reading than three pages of indignation.

Answer follow-ups quickly, and keep operating normally. Don't change how or where you log in to look different during a review. If you use an agency, they should keep working through their own User Permissions login exactly as before.

Get help for the hard cases. If funds are held or intellectual property claims are involved, talk to a lawyer or a reinstatement specialist who works through Amazon's process, not around it.

Why getting around a deactivation backfires

Opening a fresh account after a deactivation, on new details and a new fingerprint, breaks Amazon's rules on its face. When Amazon connects it to the original, the usual result is that the new one is deactivated too, often with inventory and balance stuck behind the same review, and your chances of getting the original reinstated get worse. Use false identity or business documents and it stops being only a terms problem.

And the time spent building disguises is time not spent fixing whatever caused the deactivation. That problem follows you to the next account.

The short version

A second account is allowed for a real business reason. Check the current policy page first.
Access for staff and agencies is a different question: User Permissions and API authorization.
Related accounts aren't the problem. Related bad accounts are, so keep every one clean.
A browser organises legitimate work across multiple Amazon seller accounts. It doesn't hide accounts from the platform.

Four lines. We could have opened with them and saved you the scroll.

More guides on the JustBrowser blog.

Frequently Asked Questions

Can you have more than one Amazon seller account?

Sometimes. Amazon's seller policies expect one Seller Central account per selling region and allow another where there is a legitimate business need, such as separate brands run as separate businesses. Each account must stay in good standing. Check the current Seller Central help page, including whether you must request permission first, before opening a second account.

How should an agency or a staff member access a seller's account?

Through the access Amazon built for it. The owner invites each person with their own login through User Permissions in Seller Central and chooses what they can see or change. Software connects through the Selling Partner API with the seller's authorization. Avoid sharing the owner's password: it removes the audit trail.

Why does Amazon link seller accounts?

Because a related account is how a seller deactivated for counterfeits or fake reviews comes back under a new name. Amazon doesn't publish its method, but sellers commonly report overlap in business, bank, address and device or login details. If your accounts are related for a legitimate reason, the fix is documentation, not disguise.

Read the notice, check Account Health in Seller Central, and respond through the appeal route it points to. Explain the root cause, what you've corrected and what prevents a repeat, with supporting documents. Keep it short. Opening a new account instead breaks Amazon's rules and usually ends with that account deactivated too.

Does an antidetect browser keep Amazon accounts from being linked?

That isn't what it's for, and hiding accounts Amazon hasn't approved is a terms violation. A browser like JustBrowser helps with housekeeping: one profile per client or brand so staff don't act in the wrong account, profiles shared with teammates under role permissions, and checking how listings render in other marketplaces. Amazon's policy and your business structure decide whether your accounts are allowed.

Try JustBrowser

Antidetect browser on a custom Chromium engine, always current with upstream — not extension-based. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, so 40+ identity parameters are genuine, not faked. Local REST API and CDP for Playwright, Puppeteer and Selenium. Windows x64 and macOS (Apple Silicon). $9.99/month or $99.99/year. 7-day free trial, card required — cancel any time in the seven days and you are not charged. Unlimited profiles, unlimited cloud sync, unlimited team seats.

Get started → · How it differs from Multilogin / GoLogin / AdsPower