How to Sell on Amazon with Multiple Seller Accounts

Amazon's policy on multiple seller accounts is straightforward on paper: one account per seller, unless you have explicit written approval for a second. The reality is more nuanced. Legitimate reasons to run multiple accounts exist — separate brands, different product categories, distinct legal entities — and Amazon does grant exceptions. The problem isn't the policy itself. It's that most sellers who try to run multiple accounts get linked and suspended not because of what they're selling, but because of how their accounts are connected.

This guide covers the operational side: what Amazon actually detects, how to structure accounts so they don't collapse together, and where environment isolation fits into a multi-account setup.

Why Amazon Links Accounts in the First Place

Amazon's seller surveillance is extensive. Every time you log in, the platform collects browser fingerprint data, IP address, device identifiers, and behavioral patterns. These signals get compared across all accounts touching the same infrastructure.

Two accounts that share an IP address look related. Two accounts that log in from the same browser profile are related — Amazon sees identical fingerprint parameters and treats them as the same person regardless of the name on the account. Payment method overlap, shared phone numbers, or the same bank account across multiple seller accounts will trigger a review almost immediately.

The core issue is that Amazon isn't just checking your credentials — it's mapping the environment those credentials come from. That's what makes the standard advice ("just use a different email") so inadequate. The email is the last thing they're looking at.

Legitimate Grounds for Multiple Accounts

Before the infrastructure discussion, the use case has to make sense. Amazon permits multiple accounts under specific conditions:

Separate legal entities. If you operate two genuinely distinct business entities — different LLC or company registration, different tax IDs, different payment accounts — Amazon is more likely to approve a second account. The businesses should be independently verifiable, not just different names on the same bank account.

Different brand portfolios. Sellers with meaningfully distinct brands, particularly those serving different customer segments or product categories, have a stronger case. A brand that sells professional audio equipment and a separate brand doing children's toys is a cleaner split than two similar storefronts.

Explicit Amazon approval. If you have a legitimate case, you can request permission directly through Seller Central. It's not guaranteed, but approved dual-account operations have a fundamentally different risk profile than unauthorized ones.

Without one of these foundations, running multiple accounts is a policy violation regardless of how well the environments are separated. Isolation reduces detection risk — it doesn't change what you're doing.

Account Structure: What Needs to Be Separate

Assuming there's a legitimate basis, the operational structure matters enormously. Each account needs its own complete identity stack:

• Separate legal entity (LLC, Ltd, sole trader registration)
• Separate bank account and payment method
• Separate phone number for verification and 2FA
• Separate email address and address history
• Separate Seller Central login credentials

None of these can overlap. A shared phone number between two accounts is enough to trigger a linkage review. Amazon's own marketplace guidance makes clear that account integrity is evaluated holistically — one shared data point can surface the connection.

This is also why buying an aged account or inheriting a seller account from someone else introduces risk: you inherit their history, their linked data, and their past violations.

Environment Isolation: The Part Most Sellers Miss

Clean entities and separate credentials get you halfway there. The other half is the browser environment — the layer Amazon can't see from your documentation but reads from every login.

Browser fingerprint. Every browser session emits a fingerprint: GPU renderer, Canvas hash, installed fonts, screen geometry, hardware concurrency, navigator properties. Two accounts with identical fingerprints are flagged as the same operator regardless of the business registration underneath. Digital fingerprinting is what makes shared-browser multi-accounting so consistently detectable.

IP address. Each account should have a dedicated proxy — residential or mobile, never datacenter. Residential proxies tied to the billing address geography of the account's registered entity are the cleanest option. Shared IPs across accounts, or IPs that have been previously flagged on Amazon, create immediate risk.

Cookie isolation. Sessions need to be fully separated. Cookie isolation at the browser profile level ensures that login sessions, tracking cookies, and Amazon session data from one account never bleed into another. This matters more than most sellers expect — Amazon's session tracking is persistent and cross-references heavily.

Separate profiles for each account. The practical implementation is one browser profile per seller account, with its own persistent fingerprint, its own proxy, and its own cookie store. Managing this manually across multiple accounts without dedicated tooling is error-prone at any scale above two.

Managing Sessions Without Cross-Contamination

Even with well-structured profiles, operational mistakes cause most linkages. The patterns that get sellers caught:

Logging into two accounts from the same profile. Even once. Even "just to check something." The session history gets written to that profile and the fingerprint is now connected to both accounts.

Switching accounts without switching environments. Closing a tab and opening a new one in the same browser window doesn't change the fingerprint, the cookies, or the IP. Environment switching has to be complete — different profile, different proxy session.

Shared devices among team members. A customer service employee who manages returns for two different seller accounts from their personal laptop has just linked those accounts. Team access needs to be managed through assigned profiles, not through shared logins on personal machines.

Backup and restoration. When migrating to a new machine or restoring an account setup, carrying over browser data from the old environment can reintroduce old fingerprints. Exporting and importing cookies needs to happen at the profile level, not at the browser level, to keep environments clean.

The multi-account management fundamentals apply here regardless of platform — the mechanics of keeping sessions isolated are the same whether you're managing seller accounts or social media profiles.

What Happens When an Account Gets Flagged

Amazon's suspension process for linked accounts typically follows a pattern: one account gets flagged first, triggering a review of related accounts. If the linkage is clear — same IP, same fingerprint, same payment method — all connected accounts get suspended simultaneously.

Appeals are possible but difficult. Amazon requires documentation proving the accounts are genuinely separate operations: different business registrations, different bank statements, different physical addresses. If the environmental connection is also visible in their logs, documentation of corporate separation won't be enough on its own.

For proxies and profile configurations, this is the argument for investing in proper isolation from day one rather than retrofitting it after a suspension. Retroactively separating accounts that have already been linked in Amazon's system is significantly harder than building them correctly from the start.