Cross-Border E-Commerce: Profiles for Marketplaces by Country

GetAntik editorial team · October 26, 2026 · 10 min read

How to set up isolated browser profiles for Amazon, Mercado Libre, Shopee and other marketplaces across countries without triggering linked-account bans.

A seller expanding beyond a single country runs into a simple fact fairly quickly: every new market isn't just translated product listings — it's a separate account with its own document requirements, IP expectations, and even a typical buyer device profile. Amazon, Allegro, Mercado Libre, Shopee, Noon, Trendyol — each has its own logic for grouping markets into one account, and a mistake here costs more than it looks like: from temporary sales holds to a full ban for being "linked" to another account.

Why separate profiles are necessary here at all

Marketplaces monitor whether one seller is secretly running multiple accounts to get around the rules — undercutting prices, manipulating ratings, dodging penalties for violations. To catch this, they cross-reference IP addresses, browser fingerprints, cookies, and login patterns. If you legally sell in Germany and the US through two different legal entities or two separate marketplace agreements, but log into both accounts from the same computer, through the same IP, with the same browser profile — to the system this looks identical to two accounts belonging to one person without any separation. The result is usually the same: manual review, frozen payouts, sometimes both accounts closed at once.

An antidetect browser solves the technical side of the problem: each account gets its own isolated profile with its own proxy, timezone, interface language, and device fingerprint. This isn't a way around a marketplace's legitimacy requirements — registering a legal entity, obtaining a tax number, opening a bank account in the right jurisdiction all still has to happen according to the platform's rules. But provided each account genuinely belongs to your business and is registered legally, separating environments removes the technical trigger for bans — the false detection of a link between independent, legitimate accounts.

What must match the account's country

Four profile parameters need to match the country the account is registered for, not the country where the manager physically sits:

• IP and geolocation — a proxy exiting in the target country, ideally city-level if the marketplace is sensitive to it (common with local payment systems).
• Timezone and system language — if the account is German but the browser shows Moscow time and a Russian locale, that mismatch is visible even without deep antifraud analysis.
• Currency and address format in cookies/history — if you've previously used the same profile with a different geo, old cookies and autofill data can drag in information from the wrong market.
• Device type typical for the market — Southeast Asia has a high share of mobile traffic, Western Europe skews desktop with particular screen resolutions. This isn't a hard requirement, but it reduces the odds of landing in a "suspicious customer" manual review sample.

In GetAntik, a profile's timezone, language, and geolocation are pulled automatically from the proxy's IP, while the fingerprint — OS, browser version, screen, GPU, canvas/WebGL/audio noise — is configured separately for each market in the profile editor.

How the major platforms structure their regions

Before setting up profiles, it's worth understanding the specific platform's logic — every marketplace is different, and you won't be able to save on profiles the same way everywhere.

The specifics and figures around market grouping change periodically on the platforms' end, so check the current seller rules for that specific marketplace before launching in a new country — the antidetect browser handles technical isolation, not how many jurisdictions a given platform allows you to merge under one login.

Step-by-step profile setup for a new market

1. Check the platform's requirements — whether it needs a separate legal agreement, a local bank account, a country-specific tax number.
2. Get a proxy exiting in the target country. For regular retail platforms, a quality datacenter or residential proxy with verified geolocation is usually enough; for payment gateways with strict antifraud logic, residential is the safer bet. The proxy is attached at the profile level, and language and timezone follow from it automatically.
3. Configure the fingerprint — OS and browser typical for the market, a sensible screen resolution, nothing exotic that stands out statistically.
4. Fill the profile with content: bookmarks for local logistics and payment dashboards, saved reply templates in the local language, and, if needed, an import of existing cookies if the account was originally set up manually before switching to an antidetect browser.
5. Store the 2FA key in the profile's vault, so codes aren't passed between managers over messenger.
6. Warm up the account — a few days of ordinary activity before uploading the full catalog, without a sudden spike in listing volume on day one.

If you're opening a fifth, tenth, twentieth country, repeating this process by hand is slow and error-prone — somewhere you'll forget to change the timezone, somewhere you'll leave the wrong interface language. It helps to keep a base profile template for each platform type and clone it for a new country, changing only the proxy and locale — this approach to fast account setup is covered in more detail in the piece on profile templates for fast account setup.

Proxies deserve their own line item

A cross-border seller hits proxy costs faster than the profile limit on their plan. Every country needs at least one stable proxy, and large catalogs with frequent API calls to the marketplace sometimes need in-country rotation just to avoid hitting IP-based rate limits. Buying proxies for a dozen countries manually from different providers is slow and makes quality hard to verify. GetAntik has a built-in HollyProxy integration that lets you buy a proxy for the geolocation you need in one click, right from the profile manager.

Rotation is a separate issue. For a marketplace seller account, frequent IP changes tend to do more harm than good — the system gets used to the account's "home" address, and sudden geolocation jumps with no visible reason (business relocation, provider switch) look suspicious. Rotate only when there are clear signs of a block or degraded proxy quality, not on a "better safe than sorry" schedule — this is covered in the piece on IP rotation strategy for profiles.

Team: who owns which country

Once you're past three or four countries, one person physically doesn't have time to watch every account — regional managers get assigned. This is where team roles help: the GetAntik account owner sees the entire profile pool, a regional manager only gets access to their own countries, and a finance role sees ad and proxy spend data without access to the browser sessions themselves. Per-member profile limits prevent someone from accidentally opening a colleague's regional account, and the activity log shows who logged into which account and when.

If one manager runs several brands within the same country (not unusual for agencies managing catalogs for multiple clients on one platform), it's better to split profiles by brand rather than by country — the logic overlaps with how multi-brand e-commerce is typically structured, where each store has its own listing style, catalog, and tone with buyers — more on this in the article on profiles for different stores and brands.

Common mistakes when scaling into new countries

One shared proxy pool for every country. If a provider sells a bundle of IPs without a firm geolocation guarantee, a manager might accidentally attach a Polish proxy to a German account simply because the IP was "from Europe." Verify the proxy's country and city before attaching it to a profile — don't trust the bundle's general description.

Manually reconfiguring the fingerprint every time. Without a template it's easy to forget to switch the interface language or leave the timezone from the previous country — the marketplace sees this the moment you log in.

Mixing catalogs from several countries into one account when the platform doesn't explicitly support a unified mode. Saving on profiles here usually ends in listings getting pulled for violating a specific market's rules.

Handing off access to a country without handing off context. A new regional manager gets a login and password, but not the proxy, reply templates, or support ticket history — they effectively start from zero on an account that's been running for six months. This is one of the reasons a clean handoff process between teammates matters more than it seems at first glance.

Ignoring local requirements for payment methods and documents. This is outside the browser's scope, but worth stating plainly: even a perfectly configured profile won't save an account if the legal side is set up wrong for that jurisdiction.

What it actually costs

With five selling countries, you need at least five isolated profiles plus a few extras for test/backup accounts and support team access. The Starter plan (20 profiles, $5/month) is usually enough for a small seller with a dozen markets and a couple of team members; an agency running catalogs for several clients across dozens of countries is better suited to the Base plan (100 profiles, $44/month) or Team plan (300 profiles, $79/month), both with roles and per-member limits. The GetAntik pricing page makes it easy to compare plans and estimate how many profiles you'll actually need once test and backup accounts are factored in.

On top of that, add proxy costs per country — usually a bigger line item than the profiles themselves, especially if a market requires residential IPs with a solid reputation.

FAQ

Do I need a separate profile if I sell in several neighboring EU countries through one unified Amazon account? No, if the platform genuinely merges those markets under one login — one profile with a proxy and locale matching the account's primary registration country is enough. A separate profile is needed for regions the platform doesn't merge with the rest, like North America or Japan.

Can I run a dozen country accounts on one computer at the same time? Technically yes — profiles are isolated from each other and can run in parallel; the real limit is machine resources and open tabs, not the profile logic itself. For specifics on how many profiles a given machine can realistically handle, see the piece on how many profiles can run on one PC.

What if a platform requires login only from the IP of the business registration country, not the selling country? Use a proxy with precise geolocation matching the registration country for that specific account — the rest of the profile's parameters (language, timezone) follow suit, not the country where the manager physically sits.

How do I set up a profile for each new country quickly without configuring everything from scratch? Keep a base profile template with default settings for a given platform type and clone it, changing only the proxy and localization — this saves most of the setup time when launching sales in a new country.

cross-border e-commercemarketplace multi-accountingantidetect browserproxy managementteam roles