Multiple Amazon Seller Accounts: Rules and Setup Guide
Amazon may permit multiple Amazon seller accounts for a legitimate business need, without prior approval, according to its own staff forum post. An anti-detect browser can isolate the technical signals that link accounts (IP, device, cookies, fingerprint), but it can’t change identity details (entity, bank, tax ID, address), and it guarantees nothing. A deactivation on one account can still affect every associated account.
Running multiple Amazon seller accounts comes up when you launch a second brand, sell in a second marketplace region, or run stores for unrelated clients as an agency. Guides disagree on the rules, so this one starts from Amazon’s own wording.
Donut Browser, an anti-detect browser, doesn’t sell proxies or earn from proxy providers, so the trade-offs are stated plainly. You’ll be able to test whether a second account is justified, separate identity from technical signals, set up consistent profiles, and respond to a link or suspension.
Key Takeaways
- Employee or contractor access, management services and global accounts without ID verification can all link accounts.
- Use a named timezone like
Europe/Berlinthat matches the proxy, not just a matching UTC offset.- Resolve the original violation before the secondary account.
- A browser fixes only technical signals; bank, tax and contact details must be separate for real.
Are multiple Amazon seller accounts allowed, and do you need approval?
Amazon allows multiple seller accounts when there is a legitimate business need, and a staff forum post says no prior approval is needed. Each account must still follow every Amazon policy.

Check the multiple-accounts help page in Seller Central for the exact wording before you open a second account.
Roxy_Amazon’s Seller Central forum post (shown as 2 years old) says Amazon’s standard policy “is to allow one Seller Central account per seller.” One account is the default.
The exception is in the same post: “in certain cases of legitimate business needs, Amazon may permit sellers to operate multiple selling accounts, without prior approval.” The condition is the business need, not a form you file.
This is not a new change: the staff post is about two years old and already says it.
Open Amazon’s multiple-accounts help page in Seller Central, then the page titled “Address a Multiple Account Policy violation.” Copy the wording and today’s date into your launch notes. If a guide disagrees with Amazon’s own pages, Amazon’s pages win.
A legitimate reason for a second account doesn’t exempt it from any rule.
In scope: separate brands, separate marketplace regions, accounts for unrelated clients, and testing. Out of scope: opening a new account to escape a suspension or to get around Amazon’s rules. That is abuse, and no browser makes it safe.
How do you prove a legitimate need for a second account?
You prove a legitimate need for a second account by writing down, before you open it, why one account can’t do the job, and by keeping paperwork that shows the two businesses are separate.
Amazon’s staff post gives no list of qualifying reasons. Easync names separate brands, distinct legal entities and different geographic markets, and sellers also describe 3PL or manufacturing work for unrelated clients. Treat these as situations people report, not an official list.
Run this test before you open anything:
- State in one sentence why one account can’t serve this need. If the sentence is vague, the need probably isn’t real.
- Confirm the second account has its own legal entity, bank account, tax details and contact details. Reusing your first account’s details is the common mistake here.
- Check that the product catalog is different, or sold in a different region.
- Test whether you could hand the paperwork to Amazon if asked. If you’d hesitate, fix that first.
- Rule out a reaction to a suspension or policy violation. The answer must be no.
For each account, keep a simple record: purpose, entity, owner, who has access, and date opened.
Read Amazon’s seller registration requirements for your marketplace. Collect every identity, business, bank and tax document it asks for, separately for each account, and work from Amazon’s list rather than one in a blog post.
If step 5 fails, stop there.
Which signals link multiple Amazon seller accounts?
Multiple Amazon seller accounts get linked by two families of signals: identity signals, which belong to your business, and technical signals, which belong to your browser and network.
| Identity signals | Technical signals | |
|---|---|---|
| What it is | Legal entity, bank account, tax ID, address, phone, email, payment card | IP, device, cookies, browser fingerprint |
| Who can fix it | You, with separate real business details | You, with per-account isolation |
| What a browser does | Nothing | Gives each profile its own cookies, fingerprint and proxy IP |
No browser fixes the identity group. Only separate, real business details do. Easync’s guide says “Every seller account must have its own complete set of unique details, separate bank accounts, distinct tax IDs, unique contact information, and individual login credentials.”
Amazon’s seller registration requirements page in Seller Central lists the documents each account needs. Use it as a checklist so no document is shared between accounts by accident.
The technical group is what browser fingerprinting covers: the device traits a site reads from your browser. An anti-detect browser like Donut Browser removes those links. Amazon’s rules, your behavior and your business details still apply.
What a browser does not fix
Run this audit before you open a second account:
- Same bank account or the same payout destination.
- Same payment card on both accounts.
- Same product photos reused across listings.
- Same supplier listings or identical catalog data.
- Shared shipping accounts with one carrier login.
- Shared phone or email for verification and contact.
- Saved password autofill that signs one profile into another account.
- Wi-Fi fallback to your real IP when a proxy drops.
If any line is a yes, fix it with real, separate details first. The browser only covers the second column of the table, and it helps only once the identity details are already separate.
How do employees, contractors and agencies link your accounts?
Employees, contractors and agencies link your accounts when one person or one service gets access to accounts that don’t share an owner.
A staff post by Roxy_Amazon on the Seller Central forum warns that a deactivation “could affect the selling ability across all associated accounts.” The post names three ways accounts become associated: employee or contractor access, third-party account management services, and global accounts without ID verification.
The fix is a workflow. Amazon’s permissions are the primary control, and a browser profile is an extra layer on top.
- Give each person their own Amazon login. Open User Permissions in Seller Central and invite them by email. Don’t hand over your password or share one login.
- Grant the narrowest role that fits. A listing editor doesn’t need payment settings. Review the user list whenever the work changes.
- Give each person or client one isolated browser profile. In Donut Browser, a profile keeps its own cookies, fingerprint and proxy. Lock it with a password so a shared computer doesn’t open it.
- Keep unrelated owners apart. Never let one contractor open accounts of unrelated owners from the same profile or machine. Agencies should use one profile per client, organized with groups and tags such as client name and marketplace.
- Remove access when the work ends. Delete the user in Seller Central first, then delete the profile or hand it over.
When this works, every account shows a named login per person, and no profile has ever opened two unrelated owners’ stores.
If several people need the same profiles, the Donut Browser Team plan covers profile sharing and access control for small teams.
A profile can’t change who a contractor is or whether a global account was ID-verified. It only stops the technical overlap, so keep the Amazon roles tight.
How do you set up proxies and profiles without a mismatch?
You set up proxies and profiles without a mismatch by giving each profile its own dedicated proxy, then setting that profile’s timezone, language and geolocation to the proxy’s location. A mismatch is an inconsistency a site can read, so remove it before you open Seller Central.
The browser reports a named timezone, as MDN says Intl.DateTimeFormat().resolvedOptions() returns the locale and formatting options computed for the formatter, and the timezone is one of them. MDN also says navigator.language returns the user’s preferred language.
A proxy that exits in New York with a profile reporting Asia/Ho_Chi_Minh tells two different stories. A Berlin proxy with Europe/Prague is still a mismatch even though both zones share a UTC offset, because the page reads a zone name, not an offset.
Checklist for each profile:
- One dedicated proxy, never shared between accounts.
- Timezone, language and geolocation set to the proxy’s location.
- An IP lookup and a WebRTC leak test, run before you log in.
The proxy type is a trade-off between cost, stability and trust:
| Static ISP | Datacenter | Mobile | |
|---|---|---|---|
| Cost | Moderate | Lowest | Highest |
| Stability | Stable single IP | Stable | IP can change, shared |
| Trust | High | Lowest | Highest |
| Fit for seller accounts | Long-lived accounts | Non-sensitive tasks | Special cases |
Datacenter proxies cost least, but sites tend to trust them least. Mobile proxies carry the most trust, yet their shared, changing IPs can be unstable and costly. Static ISP proxies sit between them and give you one steady address.
- Static ISP: the default for accounts you plan to keep for years.
- Datacenter: research, testing and other tasks that don’t involve a seller login.
- Mobile: a fallback when a stable ISP address isn’t enough, if you accept the cost and the shifting IPs.
For the full setup, see the guide to proxies for anti-detect browsers.
Matching these signals lowers technical linking risk. It doesn’t guarantee an outcome, and your identity details and behavior still count.
What if one of your multiple Amazon seller accounts is suspended or linked?
If one of your multiple Amazon seller accounts is suspended or linked, fix the original violation first and deal with the secondary account second.
Roxy_Amazon, an Amazon staff member, wrote on the Seller Central forum that the violations behind the original deactivation “must first be resolved individually.” The same post says: “Only when the original account is reactivated, can the secondary account be reactivated.”
Work through it in this order:
- Read the notice and name the account and the policy. Write one sentence: which account got the notice, and which policy it cites. A multiple-account notice and a listing-policy notice need different answers, so don’t start writing until you know which one you have.
- Stop making changes to the other account. Don’t swap bank details, addresses or listings to hide a link, and don’t hand logins to anyone to “look into it.” Changes made in a panic can make the picture worse.
- Fix the root cause on the original account. Then write a plain plan of action: what happened, what you changed, and what stops it from happening again. Keep it short and factual.
- Appeal the secondary account after that. Amazon’s page, “Address a Multiple Account Policy violation,” is the place to confirm what it accepts and where to submit the appeal.
- Keep records. Save every notice, appeal, reply and date in one folder. You’ll want them if a case is reopened.
If you no longer own an associated account, expect to prove it. As general guidance, not Amazon’s list, gather:
- documents showing the date and terms of the sale or transfer,
- proof that you have no access to that account,
- proof that the other account is unrelated to your business.
Amazon’s page decides what counts as acceptable evidence.
Don’t open new accounts to get around a suspension. That is abuse of the policy, and no browser, Donut Browser included, changes it. These steps also don’t promise reinstatement; Amazon makes that call.
Where does Donut Browser fit in a multi-account Amazon setup?
Donut Browser covers the technical half of a multi-account Amazon setup: it keeps the IP, device, cookies and fingerprint of each account apart, and nothing else.
I make Donut Browser, an open-source anti-detect browser. Each profile has its own fingerprint, cookies, local storage, cache, history and extensions.
Each profile can use its own proxy, and the Distribute Proxies action gives each profile the next proxy in your list. Timezone, language and WebRTC settings are set inside the Wayfern engine. The Wayfern docs page has the exact list.
For agencies and contractors, groups and tags sort profiles by client or brand. Profiles can be password-locked, data stays on your machine, and the app has zero telemetry.
Donut Browser does not sell proxies, and it is not a VPN or Tor. It can’t guarantee an account is never banned, and it can’t change your legal entity, bank account, behavior or Amazon’s rules.
If you use another browser, the same rules apply: one dedicated proxy per profile, and a named timezone that matches the proxy’s location.
Selling on Amazon is business use, and the pricing page lists commercial use from the Solo plan. To test the setup, create one profile per account; the quickstart walks through the first one.
Frequently asked questions
Can I have more than one Amazon seller account?
Yes, Amazon allows multiple seller accounts when there’s a legitimate business need, such as separate brands, entities or regions. An Amazon staff post says this can happen “without prior approval.” Every account must still follow all Amazon policies, and shared details can link them. Verify the current help page wording.
Do I have to ask Amazon for approval first?
Not according to Amazon’s own wording. Some guides say to ask first, but the staff post says Amazon “may permit” multiple accounts “without prior approval.” “May” isn’t a promise, so document your business reason.
Will an anti-detect browser keep my accounts from being banned?
No, nothing guarantees that. A browser removes technical signals like a shared IP, cookies and fingerprint. It can’t change your bank account, tax ID or Amazon’s rules.
Can I use a VPN or a proxy instead of a browser profile?
You can, but they only change your IP address. Your fingerprint, cookies and identity details stay the same, so accounts can still link. See the proxy guide for anti-detect browsers.
Which Donut Browser plan covers commercial use?
Donut Browser’s pricing page lists commercial use from the Solo plan. The free plan has unlimited local profiles and proxy support, and it needs no account.
What should you do next with multiple Amazon seller accounts?
Today: Read Amazon’s multiple-accounts help page and its “Address a Multiple Account Policy violation” page. Then write one sentence that says why the second account exists. If you can’t write it, don’t open the account.
This week: Run the identity-signal audit: bank, card, tax ID, address, phone, email, photos, suppliers and shipping accounts. Set up user roles instead of shared logins.
Before the first login: Create one profile and one dedicated proxy per account. Give each a named timezone, language and geolocation that match the proxy’s location.
The setup guide for multiple social media accounts covers warmup and leak tests that apply here too.
Ready for the technical half? Compare Donut Browser’s plans and start with one profile per account. Each of your multiple Amazon seller accounts still needs a real business reason behind it.
Sources
Multiple Amazon Seller Accounts: Guidelines and Procedures · Multiple Amazon Seller Accounts: Rules, Risks & Strategies… · Team: shared profiles, controlled access — Donut Browser · Intl.DateTimeFormat.prototype.resolvedOptions() - MDN Web… · Navigator: language property - MDN Web Docs