Start here: Residential · Static

E-commerce Seller Solution

Give each marketplace seller account its own dedicated residential IP. Platforms correlate stores that share an IP. Rotating traffic on a seller login is how accounts get reviewed.

Recommended: one static residential IP per store, in the store’s country. Custom ports if you operate many stores. Rotating is only for read-only price watches — never on Seller Central.

Sellers and agencies who log into marketplaces

Amazon / eBay sellers

One store, one static IP.

Multi-store operators

Stop sharing the office NAT across brands.

Marketplace agencies

Isolate client stores on custom ports.

DTC ops

Supplier portals that expect a stable login IP.

Rotating proxies are the wrong product here

Data Scraping uses rotating IPs on public pages. Seller accounts are logged-in identities. Do not copy that setup.

🔗

Account linkage

Two stores, one IP → reviews.

🔄

IP churn

Rotating during a seller session looks like a takeover.

🌍

Country mismatch

US store on a DE IP.

🚫

Datacenter seller logins

Hosting ASN is a red flag.

📦

3PL allowlists

Need a known address, not a pool.

💸

Cheap rotating 'savings'

One suspension costs more than a year of static.

Static per store — that is the product

Recommended: residential static, one IP per seller account. Alternative: residential custom for agencies that need many ports on one invoice. Price monitoring is a different job (rotating) on a different IP.

Product Billing Use it when…
Residential · Static Recommended Per IP / period Recommended — one dedicated residential IP per seller account.
Residential · Custom Per port / period Alternative — many stores, many ports, one bill (agencies).

How to start (one recommended path)

Path A — One static IP per store (recommended)

Map store → country → IP and never cross them.

  1. List every seller login.
  2. Lease static residential in that store’s country.
  3. Bind one browser profile to that port.
  4. Renew before expiry so the identity does not jump.
Static proxies →

Path B — Agency custom bundle

Ten-plus stores, strict isolation.

  1. Buy a custom residential port bundle.
  2. Assign ports in your ops sheet.
  3. Still one port per store — custom is packaging, not sharing.
  4. Keep monitor bots on a separate rotating pack, never these ports.
Custom proxies →

Pick one — do not mix these on the same job

Use static residential when

  • You type a seller password.
  • The platform cares about IP stability.
  • Suspension cost is high.

Use rotating residential when

  • You only read public product pages.
  • No seller credentials are on that traffic.
  • That work is price monitoring — not this login.

First-week checklist

Common questions

Rotating on Amazon seller?

Do not. Use static.

Business vs residential?

Consumer marketplaces: residential static. Wholesale B2B portals: see Cross-Border / business static.

Same as Social Media?

Same SKU type (static), different platforms. Do not share IPs across Amazon and Instagram.

One IP for all EU stores?

Risky. Prefer per-marketplace country.

API for listings?

Public competitor pages only — never for seller auth.

Go deeper

Lease one static IP for the next store

Do not buy rotating traffic for seller logins. Rotating is for public monitors on a separate IP.