Fixed IPs for the stores, rotating IPs for the data
Residential proxies for e-commerce
E-commerce runs two opposite proxy requirements at once: store back-ends need one fixed, dedicated broadband address, while catalogue and competitor scraping needs thousands of exits that rotate on demand. ZapIP serves both from the same network and the same console — static ISP IPs for the accounts, rotating residential for the data.
- One dedicated IP per store
- 90M+ residential pool
- City, state and ASN targeting
- From $0.8/GB
How it works
Multiple storefronts, one dedicated IP each
Platforms cluster accounts by looking at shared exits, shared device fingerprints and near-identical behaviour. A long-term static IP gives each storefront its own native-broadband address, dedicated and never shared, and renewal keeps that address rather than issuing a new one.
- Native ISP ASN — WHOIS resolves to a residential carrier
- Dedicated to one customer, never shared
- City and state targeting to match store registration
- Drops straight into AdsPower, BitBrowser or Multilogin
How it works
Catalogue and competitor scraping that survives volume
Category pages, listings, Q&A and reviews all sit behind tight request limits — hold one exit through a few minutes of pagination and the challenge pages start. Rotating residential proxies switch per request or on a 1–360 minute schedule, and with no concurrency cap you widen the crawl instead of slowing it down.
- Rotate per request or on any 1–360 minute interval
- No concurrency cap — scale wide instead of slow
- 99.9% request success, so retry budgets stay predictable
- Move always-on jobs to unmetered bandwidth plans
How it works
Price and availability are local facts
The same listing carries different prices, taxes, delivery promises and availability from one state to the next, so a price collected through the wrong region cannot drive a pricing decision. Thirty-three priority markets add city-level and ASN targeting, so the page your crawler renders is the page a local buyer sees.
- City targeting in 33 priority markets, plus US state level
- ASN targeting to pin a specific local carrier
- Run many countries in parallel from one account
- Sticky sessions up to 90 minutes for cart-to-checkout flows
Coverage
One network behind all four products — changing the billing model does not change how you connect or how you target.
All 33 markets- 195 countries & regions
- Available
- All 50 US states
- Available
- City-level targeting
- Precise
- ISP & ASN targeting
- Supported
4 billing models
How this is billed
All four billing models share one network. Short bursts go per GB, pipelines that run continuously go per Mbps, and anything tied to an account identity goes per IP-day or per IP-month.
FAQ
Questions about this solution
What proxies do I need to run multiple Amazon accounts?
Long-term static native-ISP addresses — one dedicated IP per storefront, unchanged for the life of the lease. Marketplaces group accounts that share an exit, so this is the wrong line item to economise on. Be clear-eyed about scope, though: IP is one signal among several, and it has to be paired with isolated browser profiles and separate registration and payment details. No proxy provider can guarantee how a platform treats an account.
Should I scrape marketplaces with rotating or static proxies?
Rotating, for anything read-only. A scraper is not being asked who it is — the platform only watches how often one exit asks — so rotation is both safer and far cheaper than paying per fixed IP, starting at $0.8/GB. Anything you log into, though, belongs on a long-term static IP: seller back-ends, buyer messages, ad accounts. Both live in the same account, so there is no separate purchase to make.
What does an e-commerce proxy setup actually cost?
It splits in two. The account side is priced per IP: long-term static from $3.8 per IP per month, so ten storefronts land under forty dollars. The data side is priced by usage: rotating traffic from $0.8/GB, and routine competitor and price monitoring rarely needs more than a few dozen GB a month. Full-catalogue crawls that never stop are cheaper on a bandwidth plan — 100Mbps from $32/day, with traffic unmetered.
Does the store's proxy location have to match where the business is registered?
Same country as the operating address you gave the platform, at minimum; matching the city is better. The thing that actually causes trouble is inconsistency — logging in from Los Angeles this week and Frankfurt the next draws far more attention than an imperfect city choice. ZapIP's long-term static IPs are selectable by city and state, and once assigned the address stays put through renewals.
Get one request working. Scale after that.
Test before you commit, with an engineer on your integration.