Indonesia and Thailand are Lazada's highest-volume SEA markets. Agencies running Lazada ID + Lazada TH + Shopee + TikTok Shop need **country-specific Multilogin profiles** — not one "SEA profile" with country switcher. Lazada links stores at the Alibaba ecosystem level when payment, warehouse, or staff access bleeds across borders.

CMDB row (multi-country Lazada)

client_id: acme_sea_fashion
brand: Acme Apparel

marketplace_profiles:
  - marketplace: lazada_id
    profile_uuid: uuid-laz-id
    proxy: id_jakarta_sticky_01
    timezone: Asia/Jakarta
    tier: prod

  - marketplace: lazada_th
    profile_uuid: uuid-laz-th
    proxy: th_bangkok_sticky_01
    timezone: Asia/Bangkok
    tier: prod

  - marketplace: shopee_id
    profile_uuid: uuid-shopee-id
    proxy: id_jakarta_sticky_02   # different session, same metro OK
    tier: prod

SEA cross-listing pattern: SEA CMDB guide.

Proxy & geo alignment

StoreProxyTimezoneLanguage
Lazada IDID sticky residential/Jakarta metroAsia/Jakartaid-ID
Lazada THTH sticky/Bangkok metroAsia/Bangkokth-TH

Vietnam-based ops teams often leak VN IP into ID/TH panels — instant trust score drop. Align per proxy alignment guide.

Hybrid: Sellercenter web + Lazada Seller app

Bulk listing and finance reports run on Multilogin web. Pick-pack, chat, and campaign notifications often need the **mobile app** on cloud phone — same pattern as hybrid architecture. One CMDB row, two device layers per country store.

Automation boundaries

TaskAutomation
Order / finance CSV exportQueue worker post-login
Mass price updateRate-limited Playwright — max N SKUs/hour
Lazada Sponsored Solutions budgetManual or capped semi-auto
Payout / tax / KYCNever automate
Buyer chat (TH/ID)Cloud phone manual or Appium with human delays

Indonesia-specific notes

Thailand-specific notes

Ops stack

Queue → OpenTelemetry traces → Grafana → Slack alerts. On ban: ban recovery scoped to country UUID only.

Related

Disclosure: MLX-MMO affiliated with Multilogin. Lazada marketplace policies apply per country.