Proxies for Competitor Price Monitoring

Check retailer prices from US, Spanish or Italian IPs, with the rest of each session set up for that market.

What price monitoring needs from a proxy

Retailers can vary prices by country, currency, shipping region, login state, visit history and other signals. The price you see from your office is not necessarily what a visitor in another market sees. An IP in the market is one of those inputs, not all of them: keep country, currency, shipping region, cookies and login state consistent between runs so comparisons are like for like. Where a retailer or marketplace offers a product feed or API, that is often the more reliable source.

IPs in each target market
An IP in the market is one location input. Currency and shipping region can also come from cookies, account settings or the site’s own choice, so set them explicitly and keep them the same between runs.
IP reputation
Retailer anti-bot systems weigh IP reputation. Dedicated IPs separate your usage from other customers, but past reputation and site rules still apply.
A fast network
Catalog monitoring means many requests per minute. Slow proxies hold up the whole pipeline.
Enough IPs for concurrency
Large catalogs need parallel requests. More IPs let you go wider without tripping per-IP limits.
IP whitelist or password auth
IP whitelist for fixed crawler machines, username and password for cloud runners.

A working starting point

Node.js (undici), a fresh session per product page. Replace the placeholder login and IP with your own from the control panel, or whitelist your machine's IP and drop the login.

New to proxy setup? Start with the HTTP proxy setup guide.

Node.js
import { ProxyAgent, fetch } from "undici";

const agent = new ProxyAgent("http://USER:PASS@198.51.100.24:8080");
const res = await fetch("https://shop.example/product/123", {
  dispatcher: agent,
  headers: { "Accept-Language": "it-IT,it;q=0.9" },
});
console.log(res.status, (await res.text()).match(/"price":\s*"([^"]+)"/)?.[1]);
Placeholder login and a documentation IP. Use your own from the control panel.

Price Monitoring questions

Why not use a price-monitoring SaaS?

You can, and many teams do. Running your own scraper through proxies can cost less per SKU on a large catalog, depending on your own engineering time, and you control exactly what you collect.

Do retailers detect price-monitoring scrapers?

Many do, and each sets its own rules. Some accept datacenter traffic and others reject it, whichever provider you use. Check each retailer’s terms, and ask us about specific targets before a large order.

How fresh does each IP need to be?

It depends on what you are measuring. Returning-visitor and basket offers depend mostly on cookies, login state and the retailer’s own records, so start each check from a fresh browser session with no stored cookies. A different IP alone does not make you a new customer. For base prices, one IP can serve many requests over time.

Can I monitor mobile prices too?

Often. Many retailers serve their mobile site to a mobile user agent, and some price it differently, so it can be worth tracking separately. Prices shown only inside a retailer’s app need the app itself.

Not sure which plan fits your workload? Tell us about it and we will recommend one.