Price Monitoring Proxies: Track Competitor Prices in 170+ Locations

Use case · Last reviewed 28 September 2026 · 12 min read

Price monitoring means tracking what competitors, resellers and marketplaces charge for the products you care about, and how those prices change over time. Done well, it shows you when to cut a price, when you can raise one, which sellers break your pricing policy and where you are losing the buy box. The hard part is not the spreadsheet; it is collecting accurate prices from hundreds of sites, every day, as real shoppers in each city see them. This guide covers what to monitor, why the price you see is often not the price your customers see, which proxies to use, how to build a reliable price monitoring workflow and what it costs to run.

What Is Price Monitoring?

Price monitoring is the regular, automated collection of prices for a defined set of products from a defined set of sellers. A small shop might check twenty rival listings once a day; a large retailer might track millions of offers across marketplaces, brand stores and comparison sites several times a day. Each check records the price, but useful programmes also record everything that changes what a customer actually pays: shipping, discounts, stock status, the seller’s name and the location the price was seen from.

Price intelligence is what you do with that history. Competitor price tracking tells you where you stand today; trends show how quickly rivals react to your changes, which products they use as loss leaders and when seasonal discounts start. Pricing teams use it to set rules (“stay within 2% of the lowest authorised seller”), brands use it to enforce minimum advertised price (MAP) policies, and category managers use it to spot gaps in the range. None of it works if the collected data is wrong, which is where most of the effort, and the proxies, go.

What to Monitor: Prices, Sellers, Stock and More

Start with the products that drive most of your revenue and the five to ten competitors your customers compare you with. Monitoring everything from day one creates noise; a focused list you trust beats a huge one full of mismatched products.

Why the Price You See Is Not the Price Your Customers See

Online prices are rarely one number. The same product page can show different prices, fees and availability depending on who asks:

• Country and currency. Stores localise prices, taxes and currencies by country, and many redirect foreign visitors to a different store entirely.
• City and ZIP code. Grocery, pharmacy, electronics and delivery platforms price by store, warehouse or delivery zone. A price checked from one city says little about another.
• Device and app. Some retailers and travel sites show app-only deals or different mobile prices.
• Traffic volume. Sites that see hundreds of requests from one IP slow them down, show a CAPTCHA, or quietly serve cached or incomplete pages.
• Your own company’s IP. Checking a competitor from your office network tells them exactly who is watching.

Every one of these is solved the same way: collect each price from an IP that looks like a normal shopper in the right place. That is the job of the proxy layer.

Best Proxies for Price Monitoring

For almost every team, rotating residential proxies are the backbone. Rotation spreads thousands of daily checks over thousands of addresses, so no single IP stands out, and ZIP-level targeting lets you record the price a shopper in a specific delivery area sees. Use per-request rotation for independent product pages and a sticky session when a price only appears after steps, for example after entering a postcode or adding an item to the basket. There is no limit on concurrent sessions, so you can check a full catalogue in parallel. Our datacenter vs residential comparison shows how to mix the cheapest proxy that works with residential fallback.

How to Build a Price Monitoring Workflow

1. Build the product list and match it. Map each of your products to the competitor listings for the same item, using GTIN or EAN codes, manufacturer part numbers or model names. Bad matching is the most common reason price monitoring data gets ignored.
2. Set the schedule per product. Fast-moving categories and marketplaces may need several checks a day; stable ranges once a day or weekly. Check more often around promotions and seasonal peaks.
3. Choose locations. Decide which countries, cities or ZIP codes matter and set the proxy targeting to match, one location per job.
4. Fetch the price at the lightest source. Many product pages include the price in structured data (schema.org Product and Offer markup) or load it from a JSON endpoint. Reading that is faster and far smaller than rendering the whole page.
5. Validate every response. Check that the product name matches, the price is a number in the expected range, and the page is not a CAPTCHA or an error. Retry with a new IP when it is.
6. Store the history. Save price, currency, shipping, stock, seller, location and timestamp for every check. Trends are worth more than the latest value.
7. Alert on what matters. Notify the team when a competitor undercuts you by more than a threshold, a reseller breaks MAP or a key product goes out of stock.

import json, requests
from bs4 import BeautifulSoup

PROXY = "http://USERNAME:[email protected]:5000"  # city-targeted username

def get_price(url):
    r = requests.get(url, proxies={"http": PROXY, "https": PROXY},
                     headers={"User-Agent": "Mozilla/5.0"}, timeout=30)
    r.raise_for_status()
    soup = BeautifulSoup(r.text, "html.parser")
    for tag in soup.find_all("script", type="application/ld+json"):
        try:
            data = json.loads(tag.string or "")
        except ValueError:
            continue
        items = data if isinstance(data, list) else [data]
        for item in items:
            offers = item.get("offers") if isinstance(item, dict) else None
            if isinstance(offers, list):
                offers = offers[0] if offers else None
            if isinstance(offers, dict) and "price" in offers:
                return float(offers["price"]), offers.get("priceCurrency")
    return None, None

When a site has no structured data, fall back to CSS selectors, and when prices only appear after JavaScript runs, look for the JSON request the page makes before reaching for a headless browser. Our guides to JSON scraping and Python web scraping cover both in detail.

Price Monitoring Bandwidth and Cost

Residential proxies are priced per GB, so the size of what you download matters more than the number of products. A worked example: 5,000 products, checked four times a day, for 30 days, is 600,000 requests a month.

The same programme costs fifteen times less when it reads the price from a lightweight source. Blocking images, fonts and video in headless browsers has a similar effect. For catalogues large enough that even efficient collection uses a lot of traffic, unlimited residential proxies remove the per-GB meter. And because unused ProxyEmpire bandwidth rolls over, quiet months fund the extra checks you need during sales seasons. Current plan rates are on the pricing page.

Price Monitoring Tools: Build, Buy or Both

• Price monitoring software. Subscription tools handle matching, dashboards and alerts for you. They are the fastest start for small catalogues, but coverage of niche sites and local prices varies, and costs rise with the number of products.
• In-house collection. Your own scrapers, proxies and database give full control over sources, locations and frequency, and the cost per check falls as you scale. It needs developer time to build and maintain.
• Both. Many teams use a tool for the main competitors and their own scrapers for the long tail, local prices or marketplaces the tool does not cover.

Whichever route you take, the proxy layer is often the difference between complete and patchy data. Tools that let you bring your own proxies work with ProxyEmpire through the standard host, port, username and password, and our web scraping proxies page covers larger in-house setups. Related use cases run on the same infrastructure: SEO rank tracking, ad verification and brand protection.

ProxyEmpire’s support team is available 24/7, staffed by real people, and can help you choose locations, rotation settings and a plan size for your catalogue. Collect public pricing data only, and keep request rates reasonable; ProxyEmpire is not for spam or illegal activity.

Price Monitoring FAQ

References

1. Schema.org: OfferThe price, currency and availability properties on product pages
2. Google Search Central: Product structured dataHow retailers publish prices in markup
3. Schema.org: gtinGS1 product identifiers for matching listings
4. MDN: 429 Too Many RequestsHow sites signal rate limits