Use Case
Use Case: Price Monitoring with Proxies (Amazon, eBay, Retail Sites)
A real workflow for stable price monitoring: rotation, retries, concurrency limits, and data freshness planning.
PT
Technical Team
Author
January 25, 2026
Published
8 min read
Reading time
#price-monitoring#retail#scraping#rotation
Overview
Price monitoring needs stability more than speed. This guide shows a safe architecture using rotation + retries + throttling to avoid bans and keep data fresh.
Examples
Recommended defaults
Concurrency: 5–20 per domain
Rotate: every 5–20 requests
Retry: 2–4 with exponential backoff
User-agent: realistic list
Cache: short TTL (5–30 minutes)Simple retry logic idea
Retry only on:
- 429
- 403 (sometimes)
- timeouts
Use backoff: 1s → 3s → 7sTroubleshooting
- If you see 403 quickly: rotate more often and reduce concurrency
- If 429: you are too fast; add delays and caching
- If HTML changes: use robust selectors and fallback extraction
Pro Tip
Do not scrape the same SKU every 10 seconds. Cache results and schedule re-checks intelligently.