What e-commerce teams monitor
- Competitor prices and promotions across regions.
- Product availability and shipping options by location.
- How your own listings appear to shoppers in target markets.
- Public catalog data, collected within site terms and applicable law.
These checks feed repricing, assortment and marketing decisions. They only help if the data matches what a local shopper really sees.
Why residential IPs help
Retail sites frequently personalize prices, currency and availability by location, and many treat server traffic differently from home visitors. A residential IP in the target region returns the same view a local shopper sees, so your monitoring reflects reality.
Because Nefo IPs come from real home connections, you can compare the same product in several countries or cities without your own network skewing the result.
A practical monitoring workflow
- Pick the product pages or search results to track and the markets they sell in.
- Create credentials and set the market with a targeting token such as
-country-gbor-city-newyork. - Fetch each page through the proxy with your scraper, recording price, currency, stock and shipping text with a timestamp.
- Repeat on a schedule and compare against the previous run to flag changes.
- Check a sample of pages in a browser to confirm your parser still matches what shoppers see.
Libraries such as Scrapy and Python Requests handle the fetch step. The guide on scraping Amazon product data in Python shows an end-to-end example.
Choosing proxy type and session mode
| Job | Proxy type | Session mode |
|---|---|---|
| Catalog and competitor sweeps | Rotating residential | Rotating |
| Cart, stock or shipping that depends on a location setting | Rotating residential | Sticky, up to 24 hours |
| High volume on sites that accept server traffic | Datacenter, from $0.66 per GB | Rotating |
| A seller account that needs one stable address | Static ISP IP | Fixed for the rental |
Try datacenter first on tolerant sites to save money, and switch to residential where prices change or pages block servers.
Targeting tips
Cost and compliance
Rotating residential bandwidth starts at $4.50 for 5 GB ($0.90/GB) and never expires, so a pilot on one marketplace and a few regions costs little. Respect each site's terms, robots directives and applicable law, keep request rates reasonable and avoid personal data you are not permitted to process. See the acceptable use policy.
For a fuller price-tracking setup, read price monitoring and how to monitor competitor prices in every country.
What to store from each product page
Consistent records make price changes easy to spot. For each product and market, save the same set of fields on every run.
- Product identifier and the page URL you requested.
- Market, which is the country, state or city you used, and the time of the request.
- Displayed price and currency, and any discount or coupon text next to it.
- Stock status and shipping or delivery message.
- The seller name, when the page lists more than one seller.
Keep the raw response as well. If a parser breaks when a store changes its layout, you can fix it and re-parse the saved pages without paying for the bandwidth twice.
Common mistakes to avoid
- Comparing prices captured from different places. Fix the market for each sample so differences come from the store, not from your vantage point.
- Rotating the IP in the middle of a cart. Use a sticky session when a price or shipping cost depends on a cart or location setting.
- Fetching every page through residential when it is not needed. Test whether a datacenter proxy returns the same page on tolerant sites to lower cost.
- Ignoring currency. Save the displayed currency with each price.
Cover both sides of the market. Check what competitors show to shoppers, and also check how your own listings appear in the regions you sell to, because a listing can be missing or mispriced in one market only.
Frequently asked questions
Yes. Target the country, state or city in the proxy username when you generate credentials, for example -country-us and -city-losangeles. See US city-targeted proxies and the US locations page.
Collecting publicly available pricing is a common practice, but you must comply with the target site's terms and applicable law. Review the acceptable use policy. For a deeper workflow see price monitoring.
Use rotating sessions for broad catalog and competitor sweeps where every product page is independent. Use sticky sessions, held 1 minute to 24 hours, when a price or stock level depends on a cart or a location setting that must stay constant.
Any HTTP client or browser tool that accepts a proxy, including Scrapy, Python Requests and Playwright. Residential proxies speak HTTP, HTTPS and SOCKS5.
Start with the 5 GB package at $4.50 and measure how much a sample run uses. Bandwidth never expires, and the price per GB drops as packages grow, down to $0.53/GB at 10 TB.