SEA agencies listing the same brand on Shopee VN, Lazada ID, Lazada TH, and TikTok Shop need a **country × platform matrix** — not one "Asia profile." Cross-contamination via shared proxy subnets or staff SSO is the top linked-store ban vector in Vietnam/Indonesia ops hubs.
Golden rule
One Multilogin profile per marketplace login per country. Shopee ID and Shopee TH are different profiles. Link in CMDB by client_id + sku_family — sync inventory via API/queue, never via cookie export.
Matrix example (one brand, four stores)
client_id: acme_sea
stores:
- { platform: shopee, geo: vn, profile: uuid-1, proxy: vn_hcm_sticky_01 }
- { platform: lazada, geo: id, profile: uuid-2, proxy: id_jkt_sticky_01 }
- { platform: lazada, geo: th, profile: uuid-3, proxy: th_bkk_sticky_01 }
- { platform: tiktok_shop, geo: vn, profile: uuid-4, proxy: vn_hcm_sticky_02 }
Hybrid mobile layer
Each row may also have a mobile_device_id for seller app flows. Web profile UUID ≠ cloud phone device — see hybrid architecture and Lazada TH/ID guide.
Queue worker filter
{
"job_id": "uuid",
"client_id": "acme_sea",
"platform": "lazada",
"geo": "id",
"task": "export_orders"
}
Worker MUST filter profile pool on platform + geo — never pop any prod profile.
Regional CMDB comparison
| Region | Guide |
|---|---|
| SEA | This guide |
| US | US CMDB |
| EU | EU CMDB |
Ban isolation
Lazada ID burn does not pause Shopee VN unless audit shows shared warehouse staff login or identical proxy exit. Runbook: ban recovery.
Related
Disclosure: MLX-MMO affiliated with Multilogin.