---
title: "Price Monitoring Proxies for E-commerce Data | Proxonym"
description: "Price monitoring proxies that return localized prices, stock and shipping from any market. Residential IPs in 195+ countries and datacenter IPs for scale."
url: https://proxonym.com/use-cases/price-monitoring
updated: 2026-10-01T21:01:06+00:00
---

# Price monitoring proxies for clean, local e-commerce data

Track competitor prices, stock and promotions exactly as shoppers in each market see them. Collect from local residential IPs on protected marketplaces and from fast datacenter IPs everywhere else.

- **$0.74** Per GB at 10 TB
- **40,000** Datacenter IPs
- **195+** Countries

Recommended for e-commerce & pricing

- [Residential proxies (Best fit)](https://proxonym.com/residential-proxies): from $0.74/GB
- [Datacenter proxies](https://proxonym.com/datacenter-proxies): from $0.013/IP
- [ISP proxies](https://proxonym.com/isp-proxies): from $1.15/IP

Pay as you go · Crypto accepted · Live in minutes

## What gets in the way.

The problems every team in e-commerce & pricing runs into sooner or later.

1. **Prices differ by market**: Retailers localize prices, currencies, taxes, shipping and promotions. Collect from a single location and you compare yourself against numbers that shoppers in your own market never see.
2. **Retailers defend their catalogs**: Large stores rate-limit and fingerprint visitors, then serve CAPTCHAs or decoy pages to suspicious traffic. A blocked request is a missing price point, and a wrong price is worse.
3. **Freshness at scale**: Prices in competitive categories move several times a day. Checking thousands of SKUs every few hours needs high concurrency and a predictable cost per check, not a pool that slows down at peak.

## How Proxonym solves it.

Settings you control from the username, with no extra tooling or separate endpoints.

### Local IPs in every market

Set the country with -country-de or narrow it to a city. Each request returns the localized price, currency and delivery promise that shoppers in that market actually get.

### Rotation that sidesteps rate limits

Spread catalog checks across 55M+ residential IPs. Every request can leave from a new address, so per-IP limits never pile up on one connection during a large run.

### Sticky sessions for location cookies

Some prices only appear after you choose a delivery location or open the cart. Hold one IP for up to 120 minutes so cookies and IP stay consistent through the whole check.

### Predictable cost per check

Run easy targets on shared datacenter IPs and protected ones on residential from $0.74/GB. Sub-users with their own traffic limits keep each client or category within budget.

## The right proxies for the job.

Start with the first one. Most teams add a second pool as their targets grow.

- [Residential proxies](https://proxonym.com/residential-proxies): For major marketplaces and retailers with strong bot protection. Country and city targeting returns localized prices, and rotation per request keeps large catalog checks moving. from **$0.74**/GB
- [Datacenter proxies](https://proxonym.com/datacenter-proxies): For smaller stores, brand sites and product feeds that accept datacenter traffic. 40,000 shared IPs in 9 countries keep the cost of each check low. from **$0.013**/IP
- [ISP proxies](https://proxonym.com/isp-proxies): For logged-in seller or distributor portals that expect one consistent address. Static ISP IPs in 17 locations with unlimited bandwidth, as low as $1.15 per IP. from **$1.15**/IP

## Up and running in three steps.

1. **Build your watchlist**: List product URLs or SKUs with the markets you compete in. Group them by retailer, because each target may need its own proxy pool and request rate.
2. **Collect through matching IPs**: Request each page with the country, and the city if needed, set in the username. Read the price from structured data where the page provides it, since it survives most redesigns.
3. **Alert on changes**: Store every observation with a timestamp, compare it with the last run and alert on price drops, stock-outs or new sellers. Keep the raw response for disputed cases.

Best practices for e-commerce & pricing

- Parse schema.org JSON-LD before falling back to CSS selectors, because structured data changes less often than layouts.
- Store currency, tax display and shipping cost next to each price so comparisons stay fair.
- Check fast-moving SKUs more often than the long tail instead of re-crawling the whole catalog every run.
- Detect CAPTCHA and empty pages before you store a result, then retry them on a new IP.
- Use a sticky session whenever a price depends on a delivery location saved in cookies.

**Read schema.org prices per market and log them to CSV**

```python
# pip install requests beautifulsoup4
import csv
import json
from datetime import datetime, timezone

import requests
from bs4 import BeautifulSoup

# Replace with the product pages you track, mapped to the shopper's country
WATCHLIST = {
    "https://shop.example.com/de/p/espresso-machine-x1": "de",
    "https://shop.example.com/us/p/espresso-machine-x1": "us",
}
HEADERS = {"User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) "
                         "AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0 Safari/537.36"}

def product_offer(html):
    """Return (name, price, currency) from the page's JSON-LD Product data."""
    soup = BeautifulSoup(html, "html.parser")
    for tag in soup.find_all("script", type="application/ld+json"):
        try:
            data = json.loads(tag.string or "")
        except json.JSONDecodeError:
            continue
        items = data.get("@graph", [data]) if isinstance(data, dict) else data
        for item in items:
            if isinstance(item, dict) and "Product" in str(item.get("@type")):
                offer = item.get("offers") or {}
                if isinstance(offer, list):
                    offer = offer[0] if offer else {}
                price = offer.get("price") or offer.get("lowPrice")
                return item.get("name"), price, offer.get("priceCurrency")
    return None, None, None

with open("prices.csv", "a", newline="", encoding="utf-8") as f:
    writer = csv.writer(f)
    for url, country in WATCHLIST.items():
        proxy = f"http://USERNAME-country-{country}:PASSWORD@gw.proxonym.com:8000"
        r = requests.get(url, headers=HEADERS, timeout=30,
                         proxies={"http": proxy, "https": proxy})
        name, price, currency = product_offer(r.text)
        writer.writerow([datetime.now(timezone.utc).isoformat(), country,
                         url, r.status_code, name, price, currency])
        print(country, r.status_code, price, currency, name)
```

### Which proxies work for price monitoring?

Residential proxies are the safe default for large marketplaces and retailers with bot protection. Shared datacenter proxies cost less per request and work well on smaller stores and brand sites. Many teams route each domain to the cheapest pool that still returns clean data and only escalate to residential where they have to.

### Can I see the price a shopper sees in a specific city?

Yes, where pricing depends on location. Add -city- or -state- to your username to exit from that area. Some retailers also price by a delivery ZIP code stored in cookies: set that location on the site inside a sticky session so the cookie and the IP stay together for the whole check.

### How often can I check prices?

As often as your plan and the target allow. We set no concurrency limit, and the burst limit is around 10,000 requests per second per account. In practice, set the frequency per category, hourly for fast movers and daily for the long tail, and keep request rates polite.

### How do I keep monitoring costs under control?

Fetch only the data you need: product APIs or JSON-LD instead of full renders, no images or fonts, compressed responses. Use datacenter IPs where they work and residential only where needed. Sub-users with traffic limits keep each client, category or environment inside a fixed GB budget.

### Is competitor price monitoring legal?

Prices on public product pages are generally treated as public information, and price monitoring is common practice in retail. Respect each site's terms, stay out of logged-in areas you are not entitled to, avoid overloading servers and consult a lawyer if you operate in a regulated market. Our acceptable use policy applies to all traffic.

## Proxies for the sites you collect from.

Platform guides with targeting tips, ready-to-run code and the proxy types that work best on each site.

- [Amazon proxies](https://proxonym.com/amazon-proxies): Prices and Buy Box winners
- [Walmart proxies](https://proxonym.com/walmart-proxies): Prices and rollbacks
- [eBay proxies](https://proxonym.com/ebay-proxies): Sold and completed prices
- [Google proxies](https://proxonym.com/google-proxies): Organic rankings by city

## Related use cases.

Teams often combine these with e-commerce & pricing on the same account.

### [Market research](https://proxonym.com/use-cases/market-research)

Gather localized content, reviews and trends in any market.

### [Brand protection](https://proxonym.com/use-cases/brand-protection)

Find counterfeits and phishing hidden behind geo-blocks.

### [Web scraping](https://proxonym.com/use-cases/web-scraping)

Collect public data at scale without bans, CAPTCHAs or rate limits.
