If a platform allows you to run more than one storefront, run each as if it were its own business: its own browser profile and sign-in, its own network exit in the market it sells to, its own staff access, and its own payment and contact details. Mixing stores in one browser is how a seller ends up replying to a customer from the wrong shop, editing the wrong listing, or seeing prices as the seller rather than as the store's buyers do.
This post covers the rules to check first, what to keep apart, a setup per store, staff access, and routine work across stores.
Check the platform's rules first
Marketplaces and commerce platforms differ a lot here:
- Some let a seller open several storefronts under one business, often with a setting or a request to support.
- Some allow separate stores for separate brands or separate legal entities.
- Some allow one storefront per region or marketplace country.
- Some limit each seller to one account, or require approval for a second.
The rules usually sit in the seller agreement or a help article about multiple accounts. Read them for each platform you sell on, follow them, and keep the approval in writing if the platform gave one. Where the platform offers a built-in way to switch between stores, that is the first choice. A separate browser profile keeps permitted stores tidy; it does not make an extra store permitted. Our acceptable use policy applies to every profile.
What to keep apart for each store
A store is more than a login. Keep each of these with the store it belongs to:
- The sign-in and session. One store per profile, so switching stores is opening another profile, never signing out and in.
- Contact and recovery details. The email inbox, phone number and 2FA device that belong to that store's business.
- Payment and payout details. Each store's own bank account or payment method, as the platform's rules require. Never reuse one store's details on another unless the platform asks you to link them.
- The market. A store that sells in Germany is run from Germany and in German, so you see prices, shipping and listings as its buyers see them.
- Staff. The people who work on one store are not automatically the people who work on another.
- Records. Who changed a listing, who refunded an order, who signed in from where.
One profile and one exit per store
For each storefront:
- Create one browser profile named for the store and its market:
Store – DE – Main,Store – UK – Outlet. - Give it a stable exit in the store's market. A static ISP proxy is the usual choice: the same address every visit, registered to a consumer internet provider. Assign proxies one to one, so no two stores share an address. Our guide to residential, datacenter, ISP and mobile proxies explains the types.
- Match the profile to that exit. Timezone and languages should follow the exit, so the store's own seller pages show local time and the right formats (match timezone and location to a proxy).
- Sign in once with the store's own login, complete 2FA, and stop the profile. Next time it opens signed in.
- Refuse a moved exit. If a store's proxy suddenly exits in another country, it is better for the profile to refuse to start than to sign in from somewhere the store has never been.
Seeing the store as buyers do
A profile in the store's market is also a quick way to check what buyers see: the listing as it appears in search, the shipping estimate, the currency and tax shown at checkout. Use a second, signed-out profile in the same market for a clean buyer's view, separate from the seller's session.
Staff access by store
Small sellers often hand the whole team one login. As the business grows, give access per store and per job:
| Person | Access to | Level |
|---|---|---|
| Owner | Every store | Manage |
| Store manager | Their store | Edit |
| Customer service | The stores they cover | Launch |
| Bookkeeper | The stores they reconcile | Launch |
| Agency or freelancer | The store they work on | Launch |
Prefer the platform's own staff accounts where it offers them, so each person has their own login on the platform's side too. Where staff work in the store's main login, share the store's profile rather than the password, and have the profile open on one computer at a time. We cover the mechanics in share account access with a team.
Routine work across stores
Order checks, stock checks and message queues repeat across every store. Doing them store by store, by hand, is where mistakes creep in. Automate the read-only parts first: open each store's orders page and extract the statuses, then review the results in one place. Keep anything that changes a store (refunds, price changes, replies) for a person in that store's profile.
How Browz supports several storefronts
Sellers who run several storefronts on platforms that allow it keep each one in its own Browz profile, with its own sessions and an exit in the market it sells to (Browz for e-commerce sellers).
- A profile per storefront. Each store keeps its own cookies, storage, extensions and downloads, saved between sessions, so switching stores is one click (browser profiles).
- A checked exit per store. One proxy per profile, from any provider, over HTTP, HTTPS, SOCKS4, SOCKS5 or SSH. Every check opens a real tunnel and measures the exit IP, country, city and timezone over HTTPS, and the profile's timezone and WebRTC follow it (proxies).
- Assignment by policy. Assign proxies one to one across all your store profiles, preview the plan, and roll it back before launch if it is not what you meant.
- Launch guards. Refuse if the exit country changed records each profile's exit country at first launch and refuses a later start from another country until you check it. A profile whose proxy fails its check is refused at Start and never starts on your own connection.
- Teams. Share each store's profiles at view, launch, edit or manage, block cookie export per member, and see launches and edits in the activity log (teams).
- Saved flows. Save an RPA flow that opens your order pages and extracts statuses, then run it on every store profile.
- Encrypted sync on every plan, so the store opens signed in on your other computer too, with the server holding only ciphertext.
Set up three stores from the command line
browz proxy add "Berlin ISP 1" --host <proxy-host> --port 8080 --scheme http --user <user> --country DE
browz proxy add "London ISP 1" --host <proxy-host> --port 8080 --scheme http --user <user> --country GB
browz proxy add "Sydney ISP 1" --host <proxy-host> --port 8080 --scheme http --user <user> --country AU
browz check "Berlin ISP 1"
browz create "Store – DE – Main" --proxy "Berlin ISP 1" --group "Shops"
browz create "Store – UK – Main" --proxy "London ISP 1" --group "Shops"
browz create "Store – AU – Main" --proxy "Sydney ISP 1" --group "Shops"Check each proxy before its store's first sign-in. The Free plan covers 5 profiles; paid plans start from $4.99 a month, with a 14-day refund on the first payment.
Frequently asked questions
Can I have more than one seller account on a marketplace?
Some marketplaces allow it, some allow it with approval or for separate brands or businesses, and some do not. The seller agreement and the marketplace's help pages on multiple accounts give the answer. Follow them, and keep any approval in writing.
Should each storefront use a different IP address?
Each store should have its own stable exit, in the market it sells to, so it is always run from the same place. Assign proxies one to one so that separate stores do not share an address.
How do I give staff access to one store but not another?
Use the platform's own staff accounts where they exist. Where staff need to work in the store's main login, share only that store's browser profile with them, at the lowest access level that does the job, and keep other stores' profiles unshared.
Can I see my store as a customer in another country sees it?
Yes: open a signed-out profile with an exit in that country, with its timezone and languages following the exit. You see the listing, currency, shipping and tax the way a local buyer does, separate from your seller session.