A dropshipping store lives or dies on three things it does not control: what is selling, what the supplier charges and has in stock, and what competitors ask for the same product. All three are public, but they look different depending on where you browse from. A residential proxy lets you check them the way a shopper in each of your markets sees them, at a pace a single home connection could never handle.
This guide covers the three monitoring jobs most dropshippers run, what to collect in each, and how to set up the proxies for them.
Why location changes what you see
Marketplaces and stores localise almost everything:
- Price and currency. Supplier marketplaces show different prices per ship-to country, and Shopify stores using Shopify Markets convert prices and sometimes change them per country.
- Shipping. Delivery cost, delivery time and even the available shipping methods depend on the destination.
- Stock. A variant can be available from one warehouse and missing from another.
- Search results. Bestseller lists and search pages are ranked per market.
If you research from your own office, you see your own country. If you sell in the US, Germany and Australia, you need to look from all three. We cover this effect in detail for the big cross-border marketplaces in price monitoring across Temu, Shein and AliExpress.
The second reason is volume. Checking a few hundred supplier listings a day from one IP quickly runs into rate limits and challenge pages. Spreading requests over residential IPs keeps each one looking like an ordinary visit.
Job 1: product research
The aim is to spot products that are gaining demand before your competitors flood them.
What to collect:
- Bestseller and “trending” lists on marketplaces, per country and category.
- Search result pages for your niche keywords: position, price, number of reviews, review growth over time.
- New listings in a category and how fast they collect orders or reviews.
- Public ad libraries, such as Meta’s Ad Library, to see which products are being advertised and for how long.
Proxy setup: rotate the IP on every request and target the country you sell to. These are single-page checks, so there is no need to hold an IP.
Job 2: supplier monitoring
This is the job that protects your margin. A supplier who raises a price or runs out of a variant can turn every new order into a loss or a refund.
What to collect, per product and variant:
- Price for each destination country you ship to.
- Stock status per variant, and per warehouse when the supplier shows it.
- Shipping cost and estimated delivery time per destination.
- The listing’s status: still live, paused or removed.
How often: daily for most of the catalogue, and every few hours for your best sellers. Alert on any change above a threshold you set, such as a price rise of more than a few percent or a variant going out of stock, so you can update your store before the next order arrives.
Proxy setup: use a sticky session when reading shipping needs several steps, for example choosing a variant and a destination before the cost appears. Keep the same IP for the whole sequence, then let it rotate for the next product. Target the destination country, and use city targeting where delivery cost differs by region inside a country.
Job 3: competitor store monitoring
Competitors selling the same product are your real price ceiling.
What to collect:
- Their catalogue: new products added, products removed, variants and prices.
- Discounts and bundles, and how long sales last.
- Stock signals, such as “sold out” or low-stock badges.
- Shipping promises shown on the product page.
Many Shopify stores expose their public catalogue at /products.json, which is much lighter than the rendered product pages and gives you titles, variants and prices in one response. Where a store uses country pricing, request it through an IP in each market you compare, since the catalogue can be priced differently per country.
Proxy setup: rotate per request, target the country, and keep the request rate low per store. A daily snapshot of a competitor’s catalogue is usually enough.
Choosing the pool and targeting
| Job | Rotation | Targeting | Pool |
|---|---|---|---|
| Product research | Per request | Country | Country Geo |
| Supplier monitoring | Sticky for multi-step checks | Country, city where shipping varies | Full Geo |
| Competitor stores | Per request | Country | Country Geo |
| Sources that do not vary by location | Per request | None | Non-Geo |
Pick the pool by the finest targeting any of your jobs needs: Full Geo if one supplier prices shipping by city, Country Geo if country is always enough. All three pools share the same gateway, rotation and session options, and you can switch pools later without changing your setup. Our e-commerce use case page shows how teams combine them across stores and marketplaces.
Keeping bandwidth under control
Dropshipping checks run every day, so traffic adds up. A few habits keep it small:
- Prefer JSON endpoints and lightweight pages over fully rendered product pages.
- Block images, video and fonts unless you need them.
- Check only what changed: compare against yesterday’s snapshot and skip unchanged items on the next pass.
- Do not re-check slow-moving products as often as best sellers.
Our guide to cutting proxy bandwidth costs goes through each of these with examples.
Staying on the right side of the line
Collect facts, not content. Prices, stock and shipping times are facts you can compare; product photos and descriptions belong to whoever made them, so write your own. Respect each site’s terms and rate limits, only read public pages, and never log into accounts that are not yours. This is general information, not legal advice.
The bottom line
Dropshipping research is a monitoring problem: what sells, what the supplier charges, and what competitors ask, in every market you sell to. Residential proxies with country targeting show you those markets as local shoppers see them, sticky sessions handle multi-step supplier checks, and a daily rhythm with change alerts keeps your store priced right. For the wider picture of tracking prices at scale, see our price intelligence page.