What Amazon varies by location
Each Amazon marketplace has its own catalog, currency and sellers, and within a marketplace the price, Buy Box winner and delivery estimate can change with the delivery location. A request that comes from a data center range is often treated differently from a home visitor, and bursts from a single IP commonly trigger challenge pages. Either problem quietly distorts a price feed, because you store a page no real customer sees.
A residential IP belongs to a consumer internet subscription, so the page you retrieve is much closer to the one a local buyer gets. That is the practical reason to use residential proxies for price work.
Which proxy type and session mode fit
Rotating residential proxies suit wide sweeps: one request per ASIN, a new IP each time, nothing to keep alive. Use a sticky session of a few minutes when you page through search results or a category, so the whole flow looks like one visitor. Sticky sessions can be held from 1 minute up to 24 hours; see rotating vs sticky proxies.
Datacenter proxies cost less per GB, but test them on a small sample first: compare their prices against a residential run before you trust the feed. Product pages are mostly text and images, so bandwidth per page is modest; block image requests in your scraper to stretch a package further.
Match the exit country to the marketplace
Pick the exit that matches the store domain: Germany for amazon.de, the UK for amazon.co.uk, Japan for amazon.co.jp. Pages for US, UK, German and Japanese proxies list what is available. For delivery-zone checks inside the US, add a state or city token and set the same ZIP or delivery location in your request, since Amazon bases many offers on it.
- Same country as the marketplace you are measuring.
- Same language header and currency as a local shopper.
- One city per run when you compare regional delivery promises.
Staying within Amazon's rules
Collect only publicly available pages, in line with Amazon's Conditions of Use and applicable law. Do not access logged-in or private account data, do not try to get around bans, and keep request rates reasonable. Our acceptable use policy applies to every account. Related reading: scraping Amazon product data with Python and price monitoring.
How to set up the proxies
Buy a package from 5 GB ($4.50, bandwidth never expires), open the proxy generator and copy the host, port, username and password into your tool. The gateway is gw.nefo.net:9000, and targeting lives in the username: -country-de for Germany, -session-abc123 to hold one IP. Integration examples are in the docs, and prices are on the pricing page.
Frequently asked questions
Residential proxies are the usual choice, because Amazon pages load for them as they do for a home shopper. Rotating sessions suit large sweeps, sticky sessions suit paging through results. Test datacenter proxies on a sample if cost matters.
Yes. Choose the exit country that matches each store, for example -country-de for amazon.de. Nefo covers 227 countries, so every marketplace has a local exit. See locations.
Rotating for one-request-per-page sweeps of product detail pages. Sticky, from 1 minute up to 24 hours, when you page through search results or need a consistent delivery location across several requests.
Collecting public data is generally permissible, but you must follow Amazon's Conditions of Use and applicable law. Avoid private or logged-in data and ask a lawyer about your specific project.
Residential bandwidth starts at $4.50 for 5 GB ($0.90/GB) and falls to $0.53/GB at 10 TB. You pay per gigabyte used, and unused bandwidth never expires. See pricing.