Options for loading shopping pages with different currency?

[noahgitsham]

I've set up changedetection.io on a VPS in Germany, using WebDriver for shopping sites, however all my price watch attempts have been in Euros. I tried copying the request headers from my browser to see if the site would load with my currency instead, but it remains in Euros.
(Does this mean these sites are resolving location purely based on IP address?)

Here's the relevant header entries from my browser, which I expected would cause the currency to load in GBP rather than EUR:

Accept-Language: en-GB,en;q=0.9
Cookie: localization=GB; cart_currency=GBP; ...

Are there any options other than routing my traffic through a domestic proxy?

I was surprised to not find any information about this in the wiki, and the lack of similar posts about this - besides this one which only happened "sometimes" - makes me wonder if I'm misunderstanding something or doing something wrong.

[ORCHORDS]

Yes — currency is resolved from your IP's geolocation on most large shopping sites; headers alone rarely override it. Accept-Language shifts the language on some sites, but currency is usually keyed to server-IP country, a currency cookie set on first visit, the account's country, or a URL/cookie parameter the site uses.

What works in changedetection.io terms:

1. Per-watch proxy — the README lists "Configurable proxy per watch" as a feature: configure a proxy (or pool) located in the target country, then select it on the watch. The site sees that country's IP and renders the local currency. This is the reliable method for WebDriver-based watches too.
2. Currency cookie / URL parameter — many sites accept an explicit override, e.g. ?currency=USD or a currency cookie; you can send fixed headers/cookies per watch, so forcing the cookie can pin the currency without a proxy. Check what your browser's URL/cookie looks like when you switch currency manually and replicate exactly that.
3. Price extraction stays the same — once the page renders in the target currency, your existing css/json filter picks up the new numbers; if you track the numeric value, keep the price filter anchored to the same element/JSON key so currency switches don't silently change what you compare.

One caveat with option 1: make sure the proxy is consistently in the same country — a rotating pool spanning countries will make the currency flip between checks and can cause false "price changed" alerts. Pin a single exit or use a sticky session.

[noahgitsham]

Thanks a lot, I feel like this info should be added to the wiki!