Multi-Accounting on Marketplaces: What's Allowed and What Isn't

GetAntik editorial team · September 28, 2026 · 10 min read

A practical guide to running multiple marketplace seller accounts legally — platform rules, technical setup, team access, and common mistakes to avoid.

Why a seller needs more than one account in the first place

A seller on a marketplace rarely runs a single store forever. The reasons to open a second, third, or tenth account are usually mundane:

• Different legal entities — one owner often has several registered companies covering different brands or product lines.
• Different brands for similar products — testing packaging, naming, and positioning without mixing reviews and ratings.
• Geographic separation — a separate account for Amazon.com, Amazon.de, Amazon.ae, because each marketplace has different document and tax requirements.
• Agency work — an agency or fulfillment team manages stores for several clients at once and needs to keep them strictly isolated from each other.
• Testing a new niche without risking the main account — a new product, a new category, a pricing experiment.

All of this is a legitimate business scenario. The problem isn't having multiple accounts — it's how you technically separate them, and what the platform actually considers a violation.

What platform rules actually forbid

It's worth not confusing "multi-accounting for convenience" with "multi-accounting to game the system." The second category is review manipulation, self-purchases to boost search ranking, ban evasion, and duplicate listings of the same product posing as competitors. This is banned everywhere, and an antidetect browser is not a workaround for it — the rules are still broken, just harder to spot technically.

A quick rundown by platform (rules change, so check the current seller agreement before you start):

The toughest case is Amazon. The platform explicitly requires you to disclose related accounts and get approval based on a business justification. If you skip this and Amazon discovers the connection itself — through IP, payment details, or device fingerprint — every linked account goes down at once, including the one bringing in most of your revenue. So for Amazon, the question isn't "how do I hide this," it's "how do I document legitimacy in advance."

Why accounts get flagged even when the business is honest

Platforms don't spot the connection between accounts by store name — they spot it through the technical trail:

1. Identical browser fingerprint — if two seller dashboards log in with the same set of parameters (fonts, screen resolution, browser version, timezone), the system links them with high confidence, even if it's two different employees.
2. Shared IP — office Wi-Fi, home internet, the same data-center proxy across several accounts. To a platform, one IP behind five stores is a signal, not a coincidence.
3. Shared cookies and localStorage — if stores are opened one after another in the same browser profile, the platform sees the same set of session identifiers and trackers.
4. A shared device with no profile separation — even with different browsers (Chrome for one store, Firefox for another), a lot of hardware parameters still match.

There's a separate issue worth its own diagnosis: internal fingerprint consistency. If the profile's timezone doesn't match the proxy's geolocation, or the browser language doesn't match the marketplace's locale, that's another suspicious pattern.

The fix isn't to "hide" an account — it's to give every store its own full technical footprint: its own browser profile with a managed fingerprint, its own IP, its own cookies and history.

How to set up multi-accounting technically

Step 1. One browser profile per store. An antidetect browser lets you create an isolated profile for each account: separate cookies, history, bookmarks, extensions, and its own fingerprint (OS, browser version, screen, fonts, WebGL/canvas noise). Profiles don't see or affect each other.

Step 2. A dedicated proxy per profile. For marketplaces, geo consistency and IP stability matter even more than for social platforms. If a store is registered in a specific country or region, the profile's timezone and interface language need to match the proxy's geo — otherwise you get exactly the mismatch that exposes linked accounts. Which type of proxy to use for which task — residential, mobile, or datacenter — is covered in the article on choosing proxy types for multi-accounting. It helps to keep proxies in one place, in a proxy manager with checks and IP rotation links, so you don't lose track of which address belongs to which store.

Step 3. Don't let payment and documents cross accounts by IP. You can technically pay with different cards from a single profile, but if the IP and fingerprint are identical across five stores, that's still a visible link. Separation has to happen at every level at once: device (virtually, through the profile), network (proxy), and session (cookies).

Step 4. Warm up a new account before ramping up activity. A sudden spike in activity on a freshly created account is a review trigger on its own, regardless of how many stores you run. How to prepare a profile for its first actions so it doesn't get restricted right out of the gate is covered in the article on account warm-up.

Cookies and 2FA — a separate headache for sellers

Marketplace accounts usually have two-factor authentication enabled, and often more than once — separately for logging into the seller dashboard and separately for financial operations and withdrawals. If one person is running five stores, 2FA codes turn into their own source of chaos: SMS messages get lost, an authenticator app on a phone isn't in sync with whoever is currently working on a given account.

It's more practical to keep the 2FA secret key attached to the profile itself — the code gets generated right where the relevant store is open, with no jumping between apps on a phone.

Cookies are worth preserving too: exporting them as JSON or Netscape format before scheduled maintenance or before handing a store off to another employee saves you from re-solving captchas and 2FA prompts on every re-login. Scheduled cookie warm-up is also useful for "dormant" stores — ones that run seasonally (a storefront for holiday gear sits idle in the off-season and needs to come back to life in spring without a sudden activity spike).

When it's not one person running multi-accounting, but a team

For a fulfillment agency or a seller with hired managers, a second problem appears — not technical, but organizational: who has access to which stores.

A practice that tends to hold up:

• Roles instead of a shared login and password. A category manager gets access only to their own stores, without the financial section; a finance person gets access to reports without the ability to edit product listings; the owner gets everything.
• Profile limits per employee. An intern shouldn't physically have access to all twenty of the company's stores, even if it's technically possible.
• Handing off a store without re-issuing passwords. When a manager goes on vacation or leaves, their stores get handed to a colleague along with cookies, history, and a saved session — no 2FA reset, no risk of losing access for a week.
• Viewing a teammate's screen to sort out disputes. If a manager complains that an account got suspended "for no reason," it's easier for a manager to check the session live than to piece it together from screenshots.

All of this is covered in detail in the article on roles, limits, and profile handoff in a team, and the underlying mechanics of team work are described in the team features section.

For an agency owner with a dozen clients and fifty stores, a shared dashboard is useful: who's currently working, how many browsers are open, where proxy and ad budget is being spent. Without that unified view, it's hard to figure out at the end of the month what you actually paid for.

Common mistakes

Cutting corners on proxies. One cheap datacenter IP behind five stores looks like a reasonable saving until the platform suspends all five at once. A proper proxy for a marketplace store is part of your cost of doing business, not a line item to trim.

Changing geo without updating the proxy and profile locale. A seller moves to a new warehouse in another region, updates the shipping address in the dashboard, and forgets to switch the proxy — so the browser timezone keeps not matching the new address.

Using the same recovery email or phone number across all accounts. This isn't formally banned by platforms, but during a review it links accounts faster than a matching IP does.

Migrating all stores to a new device at the same time. Replacing a laptop or onboarding a new employee is normal, but if five accounts "move" from one fingerprint to another on the same day, it looks suspicious to the platform's protection systems. It's better to spread the migration out and move profiles one at a time.

Ignoring Amazon's related accounts policy. Silence isn't a strategy here. If a business genuinely needs multiple Amazon accounts, the justification should be filed in advance, not after an automatic suspension.

Matching scale to business size

For a single seller running 2–5 stores, a basic plan with a limited number of profiles is enough — getting the proxy and fingerprint setup right matters more than chasing higher numbers. An agency managing dozens of clients needs a plan with hundreds of profiles and team roles. You can compare limits and pricing on the pricing page: from a free plan with 3 profiles to test the approach, up to plans covering hundreds and thousands of profiles for larger teams.

The simplest way to start is downloading the app for macOS or Windows and creating your first isolated profile for a single store — before scaling the process to a dozen accounts.

FAQ

Can I run two stores from one computer without an antidetect browser? Technically yes, using different regular browsers or incognito mode. But that doesn't solve the shared IP and matching device fingerprint problem — the platform can still link the accounts through these parameters.

Does each store need its own proxy, or can they share one? For marketplaces — a dedicated proxy per store, especially when registration geos differ. A shared IP across several accounts is the most common reason for a suspension on suspicion of linked accounts.

What if the platform has already suspended linked accounts? Work through the platform's official appeal process with documents confirming your business is legitimate. Trying to bypass a suspension with a new account without addressing the cause is pointless — rules usually forbid creating a replacement account for a suspended one anyway.

How do you quickly restore access to a store if the manager running it loses or breaks their laptop? If the profile was stored in an antidetect browser with cross-device sync and client-side encryption, access is restored on a new device using the account password — without re-doing 2FA and captchas from scratch. More on how encryption and access recovery work in the article on profile security.

multi-accountingmarketplace sellersantidetect browserproxy managementteam access