Multi-Accounting for Buyers: Alibaba & Global Sources Accounts

GetAntik editorial team · October 12, 2026 · 9 min read

How sourcing agencies and procurement teams run parallel supplier accounts on Alibaba and Global Sources safely — proxies, roles, warm-up, and rules.

A procurement team working with a dozen suppliers across Alibaba, Global Sources, and Made-in-China hits a problem that rarely gets discussed openly: a single account remembers too much. The supplier sees your request history, past order volumes, who else you've been messaging, and uses all of that when quoting a price. And if a buyer is sourcing the same product for two different clients at once, there's a real risk the seller connects the two projects and starts playing them against each other.

This isn't a gray-area trick — it's standard practice for procurement and sourcing agencies running parallel RFQs (requests for quotation) for different clients, each of whom needs to look like an independent buyer. Here's how to do it cleanly and within platform rules.

Why a buyer needs more than one account

Client confidentiality. If a sourcing agency is hunting for a supplier on behalf of Brand A and, in parallel, for a competing Brand B, the two searches can't live in one profile. A supplier might casually — or deliberately — mention to one client that they're fielding a similar inquiry from someone else.

Protection against price discrimination. An account with a history of large orders and obvious interest in one category gets quoted differently than a fresh buyer. Running independent parallel requests from separate accounts gives you a more honest read on the market — you're comparing real prices, not prices tailored to your account history.

Parallel RFQs without hitting platform limits. Marketplaces cap how many requests an account can send per day, and they flag accounts that blast identical RFQs to multiple suppliers at once. Splitting requests across client-specific profiles keeps each individual account's activity within normal bounds.

Different legal entities and payment setups. An agency may be buying on behalf of several importers, each with its own contract, payment details, and shipping address. Mixing all of that into one account is both inconvenient and risky from a bookkeeping standpoint.

What platforms allow — and what they don't

Alibaba, Global Sources, and similar B2B marketplaces don't ban having multiple buyer accounts — it's normal practice for companies with separate divisions, or for agencies acting on behalf of several clients. What's typically prohibited:

• faking reviews and ratings through fictitious orders across multiple accounts;
• dodging restrictions or bans placed on a specific seller account after a block;
• mass automated spamming of identical requests via bots;
• manipulating a platform's tender or auction system.

If you're simply running honest, parallel sourcing projects for different clients, that fits within ordinary business practice. A similar logic applies to sellers, covered in the marketplace multi-accounting guide — the core principle, "separate your projects, don't break the specific platform's rules," holds either way.

Structure: one profile, one client project

The most workable model is tying a profile to a project or client rather than to an individual employee. This matters when buyers on the team rotate but the client relationships stick around for years.

Once you're past fifty projects, profiles turn into a mess without grouping by client and tagging — someone logs into the wrong account and mixes up suppliers. For a detailed breakdown of how to organize a large profile fleet without losing track, see organizing hundreds of profiles at scale.

Proxies: geography matters more than it seems

Suppliers on Asian B2B platforms often show different terms to buyers from different regions — this isn't paranoia, it's an observable pattern: minimum order quantity, per-unit price, and lead times can shift depending on where the seller believes the buyer is located.

If the client is an importer based in Germany, the procurement account should be exiting through a German or at least European IP, not a random datacenter address. That requires proxies with a clean reputation and a correct country match — in GetAntik this runs through the proxy manager, with IP-cleanliness checks and built-in HollyProxy integration so you're not hunting for addresses manually for every new project.

Different proxy types suit different tasks — residential proxies mimic a regular buyer better, mobile proxies cost more but hold up longer in authenticated sessions. The selection criteria for sourcing scenarios specifically are covered in choosing proxy types for multi-accounting.

Warming up an account before a big deal

A brand-new buyer account that immediately requests a quote for a full container of goods looks suspicious — both to the platform and to the supplier. A smarter approach is giving the account some history first: a few small inquiries, browsing the catalog, correspondence about minor orders before moving to serious volume. That reduces the chance a seller reads the request as competitor reconnaissance or spam, and it builds trust when you eventually negotiate a large order.

Two-factor authentication is mandatory on most B2B platforms for confirming large deals or changing payment details. Storing codes in a shared team chat is a bad habit — when staff turns over, keys scatter and you can't revoke access selectively. A per-profile 2FA vault fixes this: the code is tied to the specific account, not to a manager's personal phone.

Team access: who gets into which client project

At a sourcing agency, a buyer rarely runs the same project for years — people switch roles, take leave, or leave the company. If access to supplier accounts is tied to employees' personal logins, every staff change turns into a password-reset exercise across a dozen counterparties.

It's cleaner to build access around roles and a shared profile pool:

• Admin sees all projects and can reassign profiles between buyers;
• Member only works with profiles for their own clients, with a visible list and limit;
• Finance gets access to profiles with payment details for invoice reconciliation, without the ability to change account settings;
• when a project is handed off to another employee, the profile moves along with its message history and cookies, without creating a new account with the supplier.

How profile handoff between employees works, and what restrictions make sense for each role, is covered in team roles and profile handoff.

A procurement manager also benefits from seeing the full picture: how many profiles are open right now, who's talking to which supplier, how much is being spent on proxies and subscriptions. That's a team-level calculation, not an individual one — the approach to budgeting profiles and infrastructure is covered in the economics of multi-accounting.

Common mistakes

One email address for every project. If the registration email is the same across projects, the platform — and the suppliers themselves — quickly spot the connection between supposedly independent buyers. Email should be as isolated a project asset as the proxy.

Mixing personal and work browsers. A manager logs into a client account from their regular Chrome, already signed into a personal Gmail with a dozen extensions installed. The browser fingerprint becomes recognizable, and when the employee changes, access is physically tied to their machine.

Ignoring platform RFQ limits. Even with separate profiles per client, it's easy to accidentally send ten identical requests to the same supplier in one day from different accounts — the platform's algorithm catches this and can throttle the accounts involved.

No backup of correspondence. Negotiation history with a supplier is an asset: terms discussed over months, samples sent, files exchanged. If a profile lives only on an employee's personal device and that device fails, negotiations start over from scratch.

No proxy-to-client-geo match. A buyer cuts corners and uses a cheap datacenter proxy instead of a residential one matching the importer's country — the supplier notices the mismatch and either gets suspicious or simply quotes a higher price.

Protecting client data

A sourcing agency stores commercially sensitive information in its profiles: client order volumes, contract terms, pricing correspondence the client doesn't want competitors to see. GetAntik encrypts profile data on the device using the account password, and the server has no access to it — that reduces exposure even if server-side infrastructure is compromised. Details on how profile encryption and access recovery work are covered on the security page.

Where to start

1. List every active procurement project and flag which ones can't be mixed due to client confidentiality.
2. Set up a separate profile per project, with a proxy matching the client's or importer's country.
3. Configure team roles so profiles get handed off, not rebuilt from scratch, when a buyer changes.
4. Warm up new accounts with small inquiries before pushing into large orders.
5. Turn on the 2FA vault for any account involved in payments or payment-detail changes.

For a small team, the Starter plan with 20 profiles on the pricing page covers an agency running a dozen active client projects; larger agencies managing hundreds of supplier accounts will want the Team or Enterprise plan, with a shared profile pool and role-based access.

FAQ

Can I source for competing clients from the same laptop? Technically yes, as long as each project is isolated in its own profile with its own proxy, email, and cookies. The key is preventing any data overlap between profiles and never using a shared browser session across both clients.

Do I need a separate proxy for every supplier, or just one per client? Usually one stable proxy per client project is enough — what matters is correct geography and a consistent IP, not a link to a specific supplier. Switching IPs mid-negotiation with the same seller looks suspicious.

What if a supplier asks for multiple quotes from the same company under different names? That goes beyond normal sourcing and edges into price manipulation on the buyer's side — most platforms explicitly prohibit this, and an agency should decline that kind of request from a client.

How do we hand off a project when the previous manager has left? If the profile was managed in the team's shared pool with role-based access, the handoff happens without recreating the account — the new employee gets the profile with its history and 2FA intact, and the former employee's access is simply disabled.

Should we automate RFQ submissions? If you do, be very careful and stay within platform limits — mass automated sending of identical requests is typically against marketplace rules and gets caught quickly by their anti-fraud systems.

sourcingprocurementmulti-accountingb2b marketplacesproxy management