How to Run Multiple Amazon, eBay or Shopee Seller Accounts Without Linking

Most guides on "avoiding account linking" jump straight to anti-detect browsers and proxies. That skips the question that decides whether any of it matters: is a second account allowed in the first place? This guide starts there, then walks through a clean technical setup for sellers who are operating multiple stores legitimately.

Step one: read the marketplace rules

Amazon. Amazon's Seller Code of Conduct has generally limited sellers to one selling account per region. If you have a legitimate business need for more, you're typically expected to request approval from Amazon before opening or operating additional accounts. The exact wording and process change over time, so check the current policy in Seller Central help before you do anything else.

eBay and Shopee. Both have their own rules on multiple and related accounts. A common line across marketplaces is that a new account can't be used to get around a suspension, a selling limit or other restrictions. Read the seller policies for each site you sell on.

If your additional stores aren't permitted, no browser or proxy will make them safe; you'll just raise the stakes when they're linked. Everything below is meant for legitimate multi-store setups: separate legal entities with their own stores, accounts Amazon has approved, or agencies managing client stores who need to keep environments from bleeding into each other.

What marketplaces use to connect accounts

Anti-detect browsers and proxies only address the first two rows. The rest depends on genuinely separate business information.

The setup: one store, one profile, one IP

1. Give every store its own browser profile

Create one profile per store in AdsPower or GoLogin. Each profile keeps its own cookies, cache, local storage and fingerprint, so logging into Store B never touches Store A's session data. AdsPower's free plan covers 2 profiles and GoLogin's covers 3, enough to test the workflow (checked on 2026-10-05). Our AdsPower vs GoLogin comparison covers pricing, RPA and refunds in detail.

2. Bind each profile to a dedicated static ISP IP

A seller account should log in from the same place every time, so skip rotating residential pools. Use a dedicated static ISP proxy. Two options built for this:

• IPFoxy: dedicated static residential at $7.99/month with unlimited data in 25+ countries
• Proxy-Seller: ISP proxies from $0.98/IP, with HTTP, HTTPS and SOCKS5

Prices checked on 2026-10-05. For four more providers and what to check before buying, see Best Static ISP Proxies for Long-Lived Accounts.

3. Match the IP to the marketplace

A US store gets a US IP. Set each profile's timezone, language and geolocation to match the IP so the browser and the network tell the same story.

4. Keep the IP for the long haul

Renew before it expires. If a provider reclaims your IP and you get a new one, the store effectively "moves," which is exactly the kind of change you're trying to avoid.

5. Use team permissions, not shared passwords

Both browsers support team members and profile sharing with permissions, so each person only opens the stores they're responsible for, and you can see who accessed what.

What it looks like for three stores

Every row is its own business with its own documents, payout account, phone and email. The only thing the three stores share is the operator's computer, and the profiles keep that from leaking.

Before you add the next store

• The marketplace rules allow it, or you have the approval in writing.
• The new store has its own registration details, card, payout account, phone and email.
• You've bought a new dedicated IP in the right country and confirmed it's classified as ISP.
• You've created a fresh profile, set its proxy, and checked the result on a fingerprint test page.
• You've decided who on the team gets access and set permissions before the first login.

Identity and payments: no tool separates these

This is where most "linked account" problems actually come from.

• Registration details must be real and belong to the business that operates the store. Fabricating identities or borrowing someone else's documents breaks marketplace rules and may be illegal. Identity verification isn't something a browser profile can isolate.
• Don't reuse cards or payout accounts across stores.
• Keep phone numbers and email addresses separate for each store.

Common mistakes

1. Logging into Seller Central through a rotating residential pool. The IP changes on every session.
2. Several stores on one IP. That's a direct link you created yourself.
3. Switching between two stores inside one profile. Cookies from the first login stay behind.
4. Using the seller app on your personal phone for every store. The phone's device data gets recorded too.
5. Letting an IP lapse, or downgrading to a datacenter IP to save a few dollars.
6. Separating the tech but not the paperwork. Shared addresses, cards or listings will still connect the accounts.

Summary

Confirm the rules allow what you're doing, then build one profile and one dedicated static IP per store, with timezone and language matched to the marketplace. Keep identity and payment details genuinely separate. Run one store through the full workflow on a free plan or trial before you scale.

For more on how anti-detect browsers work, read How to Choose an Anti-Detect Browser. To browse every listed option, see the anti-detect browser comparison.