Price monitoring · Residential recommended
Retailers price by country, by region, sometimes by city, and serve different stock and shipping rules to different visitors. A checker running from one datacenter sees one version, often a defensive one. Residential exits in each market return the real shelf: the price a local pays, the stock a local can order, the promotion a local is shown.
01 — Which network
A recommendation is only useful with its trade-offs. The cards below say what each network does well for price monitoring, and where it stops being worth the money.
Country and city targeting on real households returns the localized price and stock. Rotation keeps daily sweeps of large catalogues undetected.
For a small set of retailers checked frequently from one consistent location, a static ISP IP per market is cheaper than per-GB traffic.
Retail sites are among the first to block hosting ranges or serve them different prices; use only for your own storefronts.
Useful only for app-only prices or mobile-specific promotions.
02 — The recipe
The settings that matter for price monitoring, and a working example on the right. Replace USER and PASS with the credentials issued at signup.
// One sticky Berlin exit for the whole basket flow (5 minutes)
const proxy = "http://USER-cc-de-city-berlin-sid-cart42-ttl-5m:[email protected]:9000";
const dispatcher = new ProxyAgent(proxy);
const product = await fetch(productUrl, { dispatcher });
const cart = await fetch(cartUrl, { dispatcher, method: "POST", body });
// same household for both requests: price, shipping and stock stay consistent03 — Budget
Per-GB pricing is predictable once you know your page size. Enter your monthly volume; the average size is pre-filled with a realistic figure for this job and can be changed.
average product page (HTML only)
Residential rate ladder, identical in every country. Buying the month's traffic in one purchase reaches the tier shown; smaller top-ups are priced at their own tier. Full ladder.
04 — Best practices
The pool is rarely the problem. These four habits decide the success rate and the bill.
Price, shipping and stock must come from the same session; mixing IPs mid-flow produces inconsistent rows.
Store exit country, city and time with every price; a discount is only meaningful with its audience.
App-only and mobile-web promotions are common; a mobile exit shows them.
Product metadata rarely moves; re-fetch prices, not descriptions, and save the GB.
05 — Questions
Because you are a different visitor: another country, another device class, another history. Residential exits in the market you monitor show the price that market actually pays.
A product page is 200 to 400 KB of HTML. Two hundred thousand checks a month at 300 KB is roughly 60 GB, about $105 on the residential ladder.
If you check a handful of retailers many times a day from fixed locations, a static ISP IP per market is cheaper and simpler. For wide catalogues across many countries, residential wins.
Yes, from the country of each marketplace. Large marketplaces score visitors aggressively, so residential rotation with polite per-domain rates is the reliable setup.
Ready when you are
Create your account, top up $10 and try the recipe above on your real target. What you do not use stays on your balance.