E-commerce data is a long tail plus a few giants
Most e-commerce projects touch hundreds or thousands of smaller stores (many on platforms like Shopify, WooCommerce or Magento) and a handful of big retailers and marketplaces. Those two groups need different proxies. Provider guides: Webshare for e-commerce scraping and Geonode for e-commerce marketplaces.
| Webshare | Geonode | |
|---|---|---|
| Long tail of small stores | Datacenter lists, cheapest per request | Rotating datacenter per GB |
| Big retailers and marketplaces | Rotating residential | Rotating residential, cheaper per GB |
| Stock by store or delivery area | ZIP and city targeting, sessions | City targeting, sticky up to 24 hours |
| Product data without parsing | Not offered | Scraper API returning HTML or Markdown |
The long tail
Small stores rarely block datacenter IPs at reasonable rates. Webshare's per-IP lists make crawling thousands of them cheap and predictable. Many platforms expose product data as JSON-LD or JSON endpoints, which cuts bandwidth further.
The giants
Big retailers and marketplaces deploy commercial bot protection. Residential traffic is required on either provider, and Geonode's lower per-GB list price usually makes it cheaper at volume. Test both, since success rates vary by site.
Stock by location
Stock and delivery options often depend on a selected store or postcode. Use sticky sessions and set location explicitly. Webshare's ZIP targeting helps when the site also checks IP location; Geonode's long sticky sessions help when checking many products per location.
Reviews
Review pages are paginated and often loaded through APIs. Use sessions per product, keep rates low and minimise personal data.
Proxy tip: To test the Geonode side of this comparison, a small residential balance from Geonode is enough, and it doesn't expire if you pause. See Geonode for price monitoring for its full product range.
A hybrid that works
- Classify stores by testing: datacenter-friendly or not.
- Send datacenter-friendly stores through a Webshare list.
- Send protected stores through Geonode residential.
- Use Geonode's Scraper API for the few pages neither handles well.
- Re-test monthly and move stores between groups.
See using both together.
Verdict
- Long tail of stores: Webshare.
- Big retailers and marketplaces: Geonode, after testing both.
- Whole market coverage: use both.
Cost model for a market-wide program
| Segment | Stores | Pages per month | Route | Approximate cost driver |
|---|---|---|---|---|
| Long tail | 2,000 | 3 million | Webshare datacenter | Fixed list plan |
| Mid-size retailers | 50 | 500,000 | Mixed | List plan plus some residential GB |
| Giants | 5 | 300,000 | Geonode residential | Per-GB traffic |
Most of the pages run on cheap lists, while most of the cost goes to the giants. Optimising page size on those few sites has the biggest effect on the budget.
Discovering store platforms
Identify each store's platform from its HTML or headers. Platform-specific parsers (and known JSON endpoints) make the long tail fast and cheap to collect.
Budget tip: The cheapest way to settle this comparison is to test both: Webshare has a free datacenter plan, and Geonode offers a low-cost residential trial. Run the same targets through each. See Webshare for e-commerce scraping.
Reviews and UGC
Review collection is paginated and can be heavy. Collect review text and ratings, skip reviewer profiles unless needed, and use sessions per product on either provider.
A real-world example
A retail analytics platform covers 5,000 stores. It detects each store's platform, uses platform-specific JSON endpoints where available, and fetches through Webshare datacenter lists. Twenty large retailers need residential traffic and go through Geonode. Monthly, the platform re-tests 100 random long-tail stores on datacenter and every residential store on datacenter too, moving any that now pass back to the cheaper route.
Before you commit to any provider, it helps to see the wider market: our guide to the best proxies in 2026 compares proxy types by job, and cheap proxies explains how to keep costs down without buying IPs that get blocked.
Key takeaways
- The long tail of small stores runs cheaply on Webshare datacenter lists.
- Big retailers and marketplaces need residential traffic, usually cheaper on Geonode.
- Geonode's Scraper API covers the hardest pages.
- Platform detection and JSON endpoints make long-tail collection efficient.
- Re-test routes monthly and move stores as defences change.
FAQ
Do Shopify stores block datacenter proxies?
Most accept moderate datacenter traffic, but some add bot protection. Test each.
Which provider is cheaper for marketplace data?
At list prices, Geonode's residential traffic.
Can I get product data as Markdown?
Geonode's Scraper API can return Markdown. With Webshare proxies, you'd convert pages yourself.
How do I find a store's product JSON?
Check the page source for JSON-LD and the browser's network panel for API calls.
Which provider is better for marketplaces?
Test both; Geonode is usually cheaper per GB at list prices.
Can I scrape product images?
Only if needed and permitted; images greatly increase bandwidth.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.