P PROXYDECK
Home / Use-cases / Amazon scraping — full guide + top-5 proxies
Home / Use-cases / Amazon scraping — full guide + top-5 proxies

Amazon scraping — full guide + top-5 proxies

Amazon has one of the strictest rate-limit and bot-detection setups in e-commerce. Here's how to pick a proxy stack for the typical scenarios: price monitoring, dropshipping research, ASIN tracking.

e-commerce price-monitoring dropshipping ASIN-tracking
what the task needs
Proxy type
Residential rotating
Geo
US, UK, DE (where Amazon operates)
Sticky session
not critical
Pool size
50M+
Budget
$50-300/mo
iGaming tolerance
not relevant

Top-5 providers for this task

PROXYDECK editorial estimate based on tests over the past 6 months. We weighed success rate on this exact target, price, use-case tolerance, and compliance.

ⓘ Connect buttons may be affiliate links: your price does not change, and commission does not affect our scores. How we earn

#1
Formerly Smartproxy
9.2score
$2.00 / GBprice
#2
SOAX EDITOR PICK
Best balance of price, quality and tolerance for arbitrage and scraping
9.1score
$1.99 trialprice
#3
Strong value pick for irregular workloads — purchased traffic doesn't expire and can be used for months
8.7score
$1.75 / GBprice
#4
Bright Data EDITOR PICK
Industry standard for enterprise
9.4score
$5.04 / GBprice
#5
Cheap and cheerful for budget use-cases
8.0score
$1.00 / GBprice
EDITOR'S PICK
Decodo is the optimal pick for Amazon scraping. 99.5% success rate on e-commerce targets, 30-minute sticky (enough for product pages), 14-day trial for testing. Bright Data is more expensive but ships the largest IP pool — worth a look for projects above 200 GB/month.

How to set up — step by step

Baseline configuration to get started right after the proxy purchase.

1. Set up rotation per request

Amazon rate-limits aggressively per IP — 50–100 requests / hour is the typical ceiling from a single address. Rotate every request:

import requests, random

PROXIES = [...] # your residential pool
def fetch_amazon(asin):
    proxy = random.choice(PROXIES)
    headers = {
        'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64)',
        'Accept-Language': 'en-US,en;q=0.9'
    }
    return requests.get(
        f'https://amazon.com/dp/{asin}',
        proxies={'http': proxy, 'https': proxy},
        headers=headers,
        timeout=15
    )

2. Block images / CSS — saves 70–80% bandwidth

An Amazon product page weighs ~300–500 KB. Without images and CSS — 50–80 KB. A 4–6× bandwidth saving is the difference between $200/mo and $50/mo on residential.

3. Add retry logic for 503 / 429

Take a fresh IP on retry. Five consecutive 503s from different IPs means your fingerprint is detected — widen the User-Agent rotation pool.

4. Respect robots.txt and the ToS

Amazon's ToS forbids scraping, but it's a contractual breach, not a crime (see hiQ vs LinkedIn). Don't scrape authenticated pages and don't resell raw data directly.

Frequently asked questions

Questions that come up for teams working on this task.
Q.01Can I use datacenter proxies for Amazon?
+
Technically yes, but the success rate will be 30–50%. Amazon detects AWS / Hetzner / OVH ASNs and blocks them on sight. Residential pays off — the retry savings outrun the price difference.
Q.02How many IPs do I need to scrape 10K products / day?
+
In rotating mode a 1M+ pool is plenty (i.e. any top-tier provider). Each product = 1–2 requests, 10K × 2 / 86400 seconds = 0.23 req/sec — that's a light load.
Q.03Do I need a sticky session for Amazon?
+
No — for unauthenticated scraping, sticky is actually harmful. The same IP across all requests = quick ban. Rotating is the right mode.
Q.04Is the Amazon API a better option?
+
If you have MWS / SP-API access — definitely yes. But that access is only granted to sellers. For third-party monitoring, scraping is the only option.