Amazon Seller Central is one of the strictest web identity surfaces — IP reputation, cookie history, and browser fingerprint all feed risk models. Multilogin gives each seller entity an isolated Mimic profile with sticky ISP/residential proxy. Mobile Seller app flows can sit on cloud phone separately — same hybrid pattern as Shopee/Lazada.

Marketplace → profile defaults

MarketplaceTimezoneProxy typeNotes
Amazon.com (US)America/Los_Angeles or seller stateUS sticky ISP/residentialAvoid rotating DC pools
Amazon.co.ukEurope/LondonUK stickyPost-Brexit entity separation
Amazon.de / .fr / .itLocal EU TZCountry-matched stickyOne profile per legal entity
Amazon.co.jpAsia/TokyoJP mobile or ISPStrict device signals

CMDB row (one seller account)

seller_id: amz_us_brand_x
mlx_profile_id: uuid-...
marketplace: US
legal_entity: LLC name
web_proxy: us-isp-sticky-44
cloud_device_id: optional (Seller app)
tier: prod
2fa_method: authenticator (human-held)

Profile hardening checklist

  1. Mimic engine, Windows or macOS preset consistent with registration history
  2. Sticky proxy — never rotate mid-session (proxy strategy)
  3. WebRTC off or proxy-aligned; DNS via proxy
  4. Warm profile: browse Amazon as shopper before Seller Central login
  5. Fingerprint audit before automation

2FA and automation boundaries

TaskAutomation
Login + 2FAHuman only on prod accounts
Inventory CSV uploadPlaywright post-login, low frequency
Order reports downloadQueue worker OK with lease
Account health appealsManual — no scripted submissions
Bank / tax / identityNever automate

Queue pattern: queue worker + CDP reconnect for long report pulls.

Cross-border agency ops

Separate Multilogin profiles per legal entity and marketplace — US stack: US CMDB guide; EU stack: EU CMDB guide. Link by client_id only — never share cookies between US and EU profiles if entities differ.

Related

Disclosure: MLX-MMO affiliated with Multilogin. Amazon Terms of Service and seller policies apply — technical isolation does not replace compliance review.