Multiple Shopee / Lazada Stores Without Getting Banned: My Full Setup

If you are running e-commerce in Southeast Asia, you already know that Shopee and Lazada are two of the most competitive and profitable marketplaces on the planet. Combined, they serve hundreds of millions of active buyers across Indonesia, Malaysia, Thailand, Vietnam, the Philippines, and Singapore. The opportunity is massive — but so is the risk if you are trying to scale across multiple seller accounts without triggering their fraud detection systems.

I have been managing multiple stores across both platforms for the past two years. I have made mistakes, lost accounts, and rebuilt my setup from scratch. This guide covers everything I now use — the tools, the logic behind each decision, and the exact workflow that keeps my stores safe and running in parallel.

Why Sellers Run Multiple Stores​

Before getting into the technical setup, let me be clear about why serious sellers operate multiple accounts in the first place — because it is not about gaming the system. It is about how these platforms are structured.

Shopee and Lazada both limit what a single store can do. You cannot promote multiple competing brands under the same seller identity without creating brand confusion for buyers. You cannot target different regional audiences with separate pricing structures from one account. Sellers who handle multiple product categories — electronics, fashion, home goods — often separate them into dedicated stores because niche stores convert better than general ones. Some sellers also operate stores for different clients as part of an agency or white-label arrangement.

The problem is that both Shopee and Lazada use aggressive fingerprinting and behavioral analysis to detect accounts linked to the same operator. Their systems flag shared IP addresses, matching device fingerprints, identical payment methods, and overlapping login sessions. When they detect a link, they do not just warn you — they suspend all associated accounts at once.

What Gets You Flagged​

Understanding the detection logic is step one. Here is what these platforms actually track:

Browser Fingerprint — Every browser session leaves a unique signature made up of your screen resolution, installed fonts, graphics card data (WebGL), canvas rendering output, timezone, language settings, and installed plugins. If two seller accounts share the same fingerprint, the platform treats them as the same person.

IP Address — This one is obvious, but many sellers underestimate it. Even rotating between sessions on the same IP is not enough. You need a dedicated IP per store, ideally from a residential source that matches the target country.

Cookie and Session Data — Browsers store cookies, local storage entries, and IndexedDB data. Logging into Store A, then switching to Store B in the same browser — even in a different tab — leaves traces that connect both sessions.

Behavioral Patterns — Login times, product upload cadence, pricing structures, and response time patterns are all analyzed. Two stores with near-identical behavior profiles raise flags even if the fingerprint and IP are different.

Payment and KYC Data — Bank accounts and identity documents linked to multiple stores are a hard flag. This requires proper separation at the business entity level, not just at the browser level.

My Full Technical Setup​

1. Antidetect Browser: BitBrowser​

The foundation of my entire setup is BitBrowser, an antidetect browser built specifically for multi-account management. The way it works is simple in concept but powerful in execution: each store gets its own isolated browser profile with a completely unique and consistent fingerprint.

When I open Profile 1 for Store A, that session has its own canvas fingerprint, WebGL renderer, screen resolution, fonts, timezone, and user agent. When I open Profile 2 for Store B, it has a completely different set of parameters — they look like two different devices to Shopee and Lazada's detection systems. These profiles are stored persistently, meaning every time I open Store A, it loads the exact same fingerprint it always has. There is no drift or inconsistency.

BitBrowser also handles full cookie and local storage isolation between profiles. Logging into one store does not touch another store's session in any way. I currently manage 8 stores across Shopee and Lazada from a single Windows machine, each in its own BitBrowser profile, and they have never been linked.

The setup process is straightforward: create a new profile in BitBrowser, assign a proxy to that profile, open Shopee or Lazada, log in, and save. The next time you open that profile, your session is exactly where you left it.

2. Proxy Strategy​

Each BitBrowser profile needs its own dedicated proxy. I use residential proxies for all Shopee and Lazada accounts because datacenter proxies are too easily flagged by these platforms — they maintain blacklists of known datacenter IP ranges.

The key rules I follow:

• One dedicated IP per store — no sharing between profiles
• Match the proxy country to the store's target market (Indonesian store = Indonesian IP, etc.)
• Use sticky sessions so the IP does not rotate mid-session
• Buy proxies from providers that offer real residential IPs sourced from ISPs

I assign the proxy directly inside the BitBrowser profile settings. This means the proxy is always tied to that specific profile — there is no risk of accidentally opening Store A with Store B's IP.

3. Separate Payment and Business Details​

Browser isolation handles the digital fingerprint side. But you also need clean separation at the business level:

• Register separate business entities or use different individual identities for each store where platform rules require it
• Link different bank accounts or payment methods to each store
• Use separate email addresses and phone numbers for each seller account
• Never use the same device for KYC photo uploads across multiple accounts

This is where many sellers cut corners and get caught. The antidetect browser protects your digital identity — but if your bank account ties two stores together, no browser tool will help you.

4. Separate Devices for Mobile Operations​

If you manage stores through mobile apps — which Shopee Seller and Lazada Seller both have — you need separate phone environments per store. Running two Shopee Seller accounts on the same phone, even through different app accounts, is a risk.

For mobile management at scale, I use BitCloudPhone, which provides cloud-based Android environments that behave like real physical phones. Each cloud phone has its own device ID, IMEI, Android fingerprint, and network identity. I assign one cloud phone per store that requires mobile activity — order confirmations, chat responses, flash sale participation — and it operates completely independently.

This is especially useful for Shopee because the platform rewards sellers who are active on mobile with better visibility in the algorithm. Having a dedicated cloud phone environment means I can keep each store active on mobile without any cross-account contamination.

Daily Workflow​

Here is how a typical day looks when managing 8 stores:

Morning check — I open each BitBrowser profile one at a time, check orders, respond to buyer messages, and process any pending shipments. I never have two profiles open at the same time during login — I wait until one is fully loaded and logged in before opening the next.

Product management — Uploads and edits are done through the dedicated profile for each store. I schedule uploads at different times across stores to avoid identical behavioral timestamps.

Promotions — Flash sales, vouchers, and ad campaigns are set up separately per store through each profile. I stagger campaign start times and use different discount structures per store.

Mobile tasks — For stores that need mobile engagement, I open the corresponding BitCloudPhone environment and handle in-app activities there.

Common Mistakes to Avoid​

Using the same browser for multiple stores — Even switching between incognito windows does not protect you. Incognito mode clears cookies but does not change your browser fingerprint. Every session still looks identical to the platform.

Sharing proxies between profiles — If two stores ever share an IP, even briefly, you create a linkage that can trigger a review.

Logging in from your regular browser — If you ever access a seller account from your normal browser — even once — you link that account to your real device fingerprint.

Inconsistent profile behavior — Do not suddenly change the timezone, user agent, or screen resolution of an existing profile. Shopee and Lazada track consistency over time. A sudden fingerprint change on an established account is a red flag.

Final Thoughts​

Running multiple Shopee and Lazada stores profitably is absolutely achievable, but it requires a disciplined technical setup from day one. The combination of BitBrowser for desktop profile isolation, residential proxies for clean IP separation, and BitCloudPhone for mobile environments gives you a complete stack that keeps each store completely independent in the eyes of both platforms.

The sellers who lose accounts are almost always the ones who try to cut corners on one of these layers. Get the setup right once, and scaling from 2 stores to 10 stores becomes a process rather than a gamble.

If you are just starting out, register for BitBrowser here — the free tier gives you enough profiles to test the setup before committing to a paid plan. Build the habit of one profile per store from the very beginning, and you will save yourself a lot of painful account recoveries down the road.

Happy selling.