Retail sites localize prices by visitor location and quietly throttle repeat checkers. Clean rotating residential IPs return what real shoppers see -- in every market you track, at 99.2% measured success.
Use rotating residential proxies for price monitoring. Retail targets serve localized prices per region and rate-limit repeat visitors -- residential rotation gives you a fresh local identity per check. Expect ~99% success on major retail targets.
| Expected success | 99.2% on major retail (Jun 2026) |
| Rotation | Per request -- no session reuse across SKUs |
| Geo strategy | One country per pricing market; city for local stock |
| Cost fit | ~2.4 GB = 10K product pages = $5.04 PAYG |
# One localized price check per marketimport requests
proxy = "http://USER:PASS@gw.knoxproxy.com:7000"for cc in ["de", "fr", "us"]: r = requests.get("https://retailer.example/p/8842", proxies={"https": proxy}, headers={"x-kx-country": cc}) print(cc, parse_price(r.text))Price monitoring collects public product pages -- standard market research. Respect robots.txt, keep request rates reasonable, and never collect personal data.
Region, currency, delivery cost, local competition, even device class feed the number on the page. A Chicago IP asking a German shop gets the export storefront -- at worst a geo-block. The only way to see the German price is to ask as a German household.
The only reliable way to see what a real user sees is to become one.
Scheduler, proxy fetch, parser, store -- the proxy is one line in the fetch step. Everything else is pipeline you already run.
Price checks are independent events; identity reuse across SKUs is what targets learn to flag. Keep sticky only for cart-step pricing.
Hourly on fast electronics, daily on stable categories. If two checks agree 95%+ of the time, halve the frequency -- cadence is your main cost lever.
City pins only where retailers regionalize within a country. Five EU markets = five country headers on one gateway, not five providers.
Failed fetches are never billed, so your effective cost tracks the success rate you actually observe.
Rotating residential proxies -- they return localized prices and give each check a fresh local identity. Add mobile only for app-exclusive prices; use datacenter for permissive targets to cut cost.
Match cadence to volatility: hourly for fast-moving hero SKUs, daily for stable categories. If consecutive checks agree 95%+ of the time, halve the frequency -- cadence is your main cost lever.
Not if you use rotating residential IPs with polite pacing and realistic headers -- each check looks like an ordinary local shopper. Expect ~99% success on major retail targets.
Yes -- collecting public product prices is standard market research. Stay on public pages, respect robots.txt, avoid personal data, and keep request rates reasonable.
Free trial on rotating residential -- city targeting included, no credit card.