Tokopedia and Lazada ID — same Multilogin profile?

No. Even after Tokopedia–TikTok Shop integration, each platform login boundary needs its own profile. Link by client_id in CMDB only.

Tokopedia seller web or mobile app?

Use Multilogin for Seller Center web (catalog, orders, analytics). Use cloud phone for Tokopedia mobile app flows and push notifications — hybrid CMDB row.

Tokopedia Seller Multilogin Guide

Indonesia agencies often run **Tokopedia**, Lazada ID, and Shopee ID for the same brand. Post-merger with TikTok Shop, device and payment linkage got stricter — **three separate Multilogin profiles** minimum, plus mobile devices where app-only flows exist. Pattern fits the SEA CMDB guide.

CMDB row (Indonesia stack)

client_id: acme_id_fashion
brand: Acme Jakarta

marketplace_profiles:
  - marketplace: tokopedia_id
    profile_uuid: uuid-tokopedia
    proxy: id_jakarta_sticky_03
    mobile_device_id: geelark-id-9912
    tier: prod

  - marketplace: lazada_id
    profile_uuid: uuid-lazada-id
    proxy: id_jakarta_sticky_01
    tier: prod

  - marketplace: shopee_id
    profile_uuid: uuid-shopee-id
    proxy: id_jakarta_sticky_02
    tier: prod

Same metro proxy provider OK — **different sticky sessions**, never shared browser cookies.

Multilogin profile setup

Engine: Mimic, Windows or macOS preset common in ID seller ops
Proxy: Jakarta metro sticky residential — align timezone Asia/Jakarta, language id-ID
Warm-up: 5–7 days local browse before bulk catalog upload
WebRTC: disabled; DNS matches proxy geo

Hybrid mobile (Tokopedia app)

Order notifications, chat, and some promo tools push mobile-first. Bind cloud phone with ID mobile proxy — not the same IP as web session simultaneously. See hybrid architecture and GeeLark API.

Automation boundaries

Task	Layer	Automation
Order export / report download	Web	Queue worker with lease
Bulk product upload	Web	Playwright post-login, strict rate cap
Buyer chat	Mobile	Manual or Appium with human pacing
Power Merchant / official store verification	Both	Never scripted
Payout / bank / NPWP tax	Both	Never automate

TikTok Shop Indonesia overlap

Integrated seller flows may share backend identity — still use **separate Multilogin profiles** for Tokopedia web vs TikTok Shop seller center unless legal entity and login are literally unified. When in doubt, isolate and link via CMDB audit only.

Ops & recovery

Long report pulls: wrap CDP with CDP reconnect + OpenTelemetry traces. Ban on one ID marketplace — scope tier=burn to that UUID: ban recovery.

Lazada TH & ID SEA CMDB Shopee & Lazada Shopee/Lazada (VI) Cloud phone hub

Disclosure: MLX-MMO affiliated with Multilogin. Tokopedia and GoTo marketplace policies apply.

Tokopedia Seller Ops