Temu and Shein seller workflows split across **mobile app** (device trust, push notifications, warehouse scans) and **web seller portal** (bulk listing, finance, dispute panels). Agencies running 5+ stores need the same **hybrid CMDB** pattern as TikTok Shop — Multilogin for browser, cloud phone for app, linked by client_id only.

Two-layer CMDB row

client_id: acme_cn_us_brand
legal_entity: Acme Trading Ltd

layers:
  - platform: temu
    web_profile_uuid: uuid-temu-web      # Multilogin Mimic
    mobile_device_id: geelark-8842       # Cloud phone
    proxy_web: isp_us_ca_sticky_01
    proxy_mobile: mobile_us_ca_sticky_01
    tier: prod

  - platform: shein
    web_profile_uuid: uuid-shein-web
    mobile_device_id: geelark-8843
    proxy_web: isp_us_ny_sticky_02
    proxy_mobile: mobile_us_ny_sticky_02
    tier: prod

Architecture reference: hybrid cloud phone + anti-detect.

Profile setup (Multilogin web)

Cloud phone layer (mobile app)

Temu/Shein mobile apps check device integrity more aggressively than web panels. Use GeeLark/DuoPlus or Appium with:

Automation boundaries

TaskLayerAutomation
Seller portal login + 2FAWebHuman on prod accounts
Order export / inventory syncWebQueue worker with lease
Bulk SKU uploadWebPlaywright post-login, rate-limited
Warehouse scan / pick-packMobileAppium with human pacing
Payout / banking / KYCBothNever automate
Appeals / policy disputesBothManual only

Cross-listing with Amazon/TikTok Shop

Same brand on Temu + Amazon + TikTok Shop = **three web profiles minimum** plus mobile devices where required. US agencies: US CMDB guide. Route jobs via profile pool with platform filter.

Ban recovery

On restriction: pause queue for affected UUID only — tag tier=burn, clone for forensics, audit proxy vs warehouse address. Runbook: ban recovery. Alert routing: Alertmanager → Slack.

Related

Disclosure: MLX-MMO affiliated with Multilogin. Temu and Shein seller policies apply — technical isolation does not replace compliance review.