EU agencies running the same brand on Amazon DE, Allegro PL, eBay DE, and Shopify EU need a **CMDB pattern** — not one browser profile with four logins. Cross-contamination is the #1 cause of linked-account bans in EU ops.

Golden rule

One Multilogin profile = one marketplace account = one legal entity surface. Link by client_id + sku_family only. US/LATAM pattern: Etsy cross-listing CMDB.

Client-level CMDB (example)

client_id: acme_eu_2026
legal_entity: GmbH (DE)
sku_family: acme_home_goods

shops:
  - marketplace: amazon_de
    mlx_profile_id: uuid-a
    geo: DE
    web_proxy: de-isp-sticky-22
    tier: prod

  - marketplace: allegro_pl
    mlx_profile_id: uuid-b
    geo: PL
    web_proxy: pl-isp-sticky-18
    tier: prod

  - marketplace: ebay_de
    mlx_profile_id: uuid-c
    geo: DE
    web_proxy: de-isp-sticky-31
    tier: prod

  - marketplace: shopify_eu
    mlx_profile_id: uuid-d
    geo: DE
    web_proxy: de-res-sticky-09
    tier: prod

Proxy policy per country

MarketplaceRequired geoCommon mistake
Amazon.deDE stickyStaff UK VPN on DE account
Allegro.plPL stickyDE proxy on PL registration
eBay.deDE stickyShared proxy with Amazon profile
Shopify (DE entity)DE stickyRotating EU pool mid-session

Inventory sync job routing

# Queue worker — one job per marketplace profile
job = {
  "client_id": "acme_eu_2026",
  "task": "sync_inventory",
  "marketplace": "allegro_pl",
  "profile_id": "uuid-b",  # from CMDB lookup, not shared
  "geo": "PL"
}
# acquire_profile(tier="prod", geo=job["geo"])

Worker pattern: queue worker + profile pool.

Ban isolation

If Allegro PL burns — tag uuid-b burn tier only. **Do not** pause Amazon DE unless CMDB audit shows shared proxy or staff access bleed. Runbook: ban recovery.

Agency workspace

Related platform guides

Disclosure: MLX-MMO affiliated with Multilogin. Marketplace policies vary — compliance is your responsibility.