Price Monitoring Across Markets: One Static IP per Country
Contents

- Why does the same product cost different amounts in different markets?
- Why keep one fixed address per market?
- Static residential proxy for price monitoring: what to check
- What does a simple monitoring routine look like?
- How do you stay within the site’s rules?
- How many addresses do you need?
- When is a proxy the wrong tool for price monitoring?
- Quick answers
In short: Price monitoring across markets means recording the public price a shop shows in each country, on a fixed schedule. One product can differ by currency, tax display, availability and local promotions. To compare runs, check each market from one static address in that country, record the price, currency, tax, stock, time and address used, and keep to the site’s terms, its robots.txt and a modest frequency.
Price monitoring across markets is the routine of recording what a product costs in each country where it is sold, run after run, so that a change in the record is a change at the shop. This guide covers checking public prices from inside each market, from one fixed address per country, at a pace the site allows. ProxyJam sells static residential (ISP) proxies, the kind of address the routine uses, and the wider job of checking pages country by country is on our region testing page. Our editorial policy explains how articles like this are sourced and corrected.
Why does the same product cost different amounts in different markets?
Because a shop sets its prices per market, and several things change at the border. E-commerce platforms build this in. Shopify’s help pages describe prices set by country or region, percentage adjustments per market and rounding after currency conversion, and catalogs that decide which products a market can buy at all. Four differences come up most often.
- Currency. The amount is converted or set per market, and rounding can move it to a local price ending. A dollar sign does not say which dollar: Australian, Canadian and US prices all use it. ISO 4217 gives every currency a three-letter code, such as USD or CAD, and that code belongs in the record.
- Tax in the shown price. In the EU, the price shown to consumers is the “final price for a unit of the product, or a given quantity of the product, including VAT and all other taxes”, under the Price Indication Directive. In the United States, sales tax is usually added at checkout. Google’s Merchant Center rules follow the same split: no tax in the submitted price for the US and Canada, VAT or GST included for most other countries. Set a German price beside a US one as shown, and you are comparing a figure with tax against a figure without it.
- Availability. A product, a size or a plan can be offered in one market and missing in another, or offered and out of stock. Those are different facts, so they need different values in the record.
- Promotions. Sales run per market and per date. In the EU, the Omnibus Directive requires an announced reduction to show the prior price, which it defines as the lowest the trader applied over a period of at least 30 days before the reduction. A crossed-out price on an EU page therefore carries information that a US page may lack.
The table Why one product carries different prices pairs each difference with the field that captures it. How a site decides which market a visitor is in, and which other signals it reads, is covered in viewing your website from another country.
Why keep one fixed address per market?
A comparison needs one thing to change at a time. If Monday’s run reached a shop from one network and Thursday’s from another, a new price may come from the shop or from how the shop treated the second address, and the record cannot say which. One static address per country keeps the vantage point constant, so a difference between two runs points to the shop. Holding one address and drawing from a pool are compared in ISP vs residential proxies.
The kind of network counts too. Some sites treat addresses on hosting networks differently from household connections, so a check from a hosting range can show a page no shopper in the market would see. An ISP proxy is an address announced by an internet provider’s network and served from a data centre, the same kind of network a local shopper is on.
A fixed address can still drift: geolocation databases are updated, and an address can be recorded under another country. Open What Is My IP through the proxy before each run. If the address no longer geolocates to the market you bought, the run made from it should not be filed. The address is not replaced during the period you paid for (section 2.5 of the Terms of Service).
Static residential proxy for price monitoring: what to check
A static residential proxy is the address this routine is built on, so test it on the first day. Payments are final, and the Refund Policy (section 1) refunds an IP to your balance only for a defect reported within 24 hours of payment. For a static address those defects are a speed under 2 Mbit/s, a refused connection and a Fraud Score of 75 or higher in our IP checker. Four checks fit into that day.
- The country. Open What Is My IP through the proxy and compare the country with the market you bought. We determine an address’s country by MaxMind. Another geolocation database can place the same address elsewhere, which the Refund Policy does not treat as a defect (section 2), so also note the country the shop itself shows on its first page.
- The network. The carrier named on the order is the network that announces the address. Compare the ASN with that carrier, as how to check if an IP is residential sets out step by step.
- The connection. Connect with the username and password the order shows, or from an allowlisted IP of your own; proxy authentication methods compares the two. Run a speed test through the proxy and keep a screenshot, which a speed claim needs.
- The shop’s first answer. Load one product page from the market’s setup. A block by the target site is not a refundable defect (section 2), and seeing one on the first day tells you to ask that shop for a feed before you build a schedule around it.
Once the address passes, it can carry the market’s record for as long as you keep it: renewing the order keeps the same address (Terms of Service, section 2.5).
What does a simple monitoring routine look like?
Pick the products, pick the markets, fix the schedule, and record every run the same way. The steps are listed under One monitoring run, market by market, and the fields under The fields of one record. Three habits keep the records comparable.
- Keep each market’s setup fixed. One browser profile or script setup per country, with that market’s language and no saved cookies, using that market’s address. A region or currency saved in a cookie can outweigh the address.
- Write values first, convert later. Record the price exactly as shown, with its currency code and whether tax is included. Conversion to one currency and the removal of tax go into separate columns, with the exchange rate and its date beside them, so the raw record never changes.
- Keep three states of availability. In stock, out of stock and not offered in the market are different findings. An empty cell hides which one it was.
Compare each record first with the same market’s previous run. A comparison between two markets comes later, once the converted columns exist.
How do you stay within the site’s rules?
Check public pages, at a modest pace, within the site’s terms and its robots.txt. Our Acceptable Use Policy names price and market intelligence among the uses that need no prior review (section 2), and permits business intelligence using information you are lawfully permitted to access (section 1). Section 3 sets the limit that matters most here: public availability of data does not by itself authorise scraping or automated access, and you must respect the site’s rules, contractual restrictions, rate limits and, where legally applicable, its robots.txt.
- Public pages only. A price any visitor in the market can see without signing in is a public price. A shop that shows its prices to visitors in a market has published them there. A shop that refuses visitors from your own country has set a restriction, and section 5 of the policy prohibits accessing a site in breach of its regional availability.
- The site’s terms. A site’s terms may forbid automated access or limit it. Read them before the first run and whenever they change. Where they forbid scripts, ask the shop for permission or for a feed it publishes.
- robots.txt. The rules are standardised in RFC 9309, which says “These rules are not a form of access authorization”, so a path robots.txt allows is still subject to the terms. A path it disallows stays out of a scripted run. The RFC also says a crawler should not use a cached copy for more than 24 hours, so a script should read the file again each day.
- Frequency. Match the schedule to the decision: a weekly price review needs a weekly run, and a daily repricing decision a daily one. Within a run, load one page at a time per site. A server that answers 429 Too Many Requests is limiting the rate, and RFC 6585 lets it add a Retry-After header saying how long to wait. Wait at least that long. Spreading requests over more addresses to keep going would be acting against the site’s rate limit, which section 5 prohibits.
How many addresses do you need?
One per market. No count fits every programme, but three questions settle it.
- How many markets? Each country needs its own address there, so three markets need three addresses. The countries we offer are listed on the proxy locations page, 76 today.
- How often? Frequency adds no addresses. A daily run and an hourly run use the same address per market; only the number of visits changes.
- How much runs at once? Several people or scripts checking the same market can share its address: each address carries up to 100 concurrent sessions, whatever the traffic (Terms of Service, section 2.4). A routine that loads one page at a time per site uses one session per site.
Addresses are priced per IP per period, as listed on the pricing page, and each one stays yours for the period you pay for, which keeps a market’s vantage point the same from the first run to the last.
When is a proxy the wrong tool for price monitoring?
- Prices by city. The catalogue is sold by country, so a difference between two cities is beyond what it can show.
- Prices tied to the shopper. A price that depends on a loyalty account, a basket or past orders is a personal price, and a signed-out check sees the public one.
- Many independent samples at once. Testing whether a site shows different prices to many different visitors needs many addresses in parallel, which is a rotating pool’s job, and we do not sell rotating addresses yet.
- A whole catalogue at speed. Collecting every price of a large retailer in a short time is a question for the retailer. Ask for a data feed or a licence; an address does not answer it.
For a market in the United States, the US ISP proxies page lists each named carrier, and the full catalogue is on the ISP proxies page. Start with one address per market you track, and add markets as the list grows.
