Start here: Residential · Static (per country)

Cross-Border Commerce Solution

Run amazon.de, amazon.co.jp, and amazon.com as separate identities — each on a static residential IP in that country. One 'EU IP' for every store is how reviews start.

Recommended: static residential per marketplace country. Use business static for freight, customs, and trade-finance portals. This extends E-commerce; it is not a scraping page.

Purchase static IPs Freight/customs: business IP →
Who it's for

Operators with more than one country storefront

Global marketplace sellers

Per-marketplace IP, per entity.

Payment ops

Acquiring dashboards that geo-lock.

Logistics

Domestic-only carrier portals.

Localization QA

Checkout as a local shopper — on a monitor IP, not the seller IP.

Pain Points

E-commerce vs cross-border

E-commerce is 'one store, one IP'. This page is 'many countries, many legal entities, many IPs' plus B2B trade portals.

🌍

One IP for all EU stores

Marketplaces still treat DE vs FR as different worlds.

💳

Payment risk

Foreign IP + foreign card = holds.

📦

Carrier geo pages

Rates hidden off-country.

🔐

Tax sites

Government portals reject foreign egress.

🚫

Sudden country change

Seller account in review.

🕷️

Monitor traffic on seller IP

Crawling from the store login IP is a self-inflicted review.

What to buy

Per-country static, plus business for trade

Recommended: residential static per marketplace country. Alternative: business static for freight/customs/banking. Public catalog monitors use rotating on a third IP.

Product Billing Use it when…
Residential · Static Recommended Per IP / period Recommended — each consumer marketplace login in its country.
Business / ISP · Static Per IP / period Alternative — freight, customs, trade finance, B2B allowlists.
Recommended path

How to start (one recommended path)

Path A — Per-marketplace static (recommended)

Map each store URL to one country IP.

  1. amazon.de → DE static, amazon.co.jp → JP static, and so on.
  2. Never reuse those IPs across marketplaces.
  3. Keep payment ops on the same port as that store.
  4. Renew on the same cycle as the store subscription.
Static proxies →

Path B — Business static for trade

Forwarders and customs.

  1. Lease business static in the import country.
  2. Submit IP to the forwarder allowlist.
  3. Do not run Seller Central on this port.
  4. Audit who in logistics still has the credential.
Business proxies →
Decision guide

Pick one — do not mix these on the same job

Use residential static when

  • Consumer marketplace seller accounts.
  • IP country must match the store entity.
  • Sessions are long-lived.

Use business static when

  • Freight, customs, or trade-finance B2B.
  • Vendor expects business ASN.
  • An allowlist form was emailed to you.
Getting started

First-week checklist

FAQ

Common questions

Same as E-commerce?

Same SKU family. This page is the multi-country operating model.

One IP for all .eu?

Avoid.

Rotating on seller login?

No.

Employees sharing an IP?

Same legal entity only, and document it.

Web Scraping API?

Fine for public localized product pages. Forbidden for seller auth.

Resources

Go deeper

E-commerce (single store) Static proxies Business proxies Pricing

Give the next country store its own IP

Per-country residential static for marketplaces. Business static for trade portals only.

Purchase static IPs Freight/customs: business IP →