Use case

Proxies for Retail Copping

Run add-to-cart and checkout tasks against a limited restock — GPUs, consoles, collectibles — without dying to the same anti-bot layer sneaker and ticket bots already have to clear. Private residential's continuously-screened pool survives a retailer that's started trust-gating checkout, mobile adds carrier-grade trust at the final step, and static ISP holds one dedicated identity per bot account for the whole restock window.

Retail Copping, from the inside

Three things worth knowing about how retail copping actually works on this network, and what each one looks like from the inside.

Match

The right identity for the restock

Private residential clears a retailer's anti-bot layer the moment checkout starts trust-gating — every address checked continuously and swapped the instant one fails. Mobile adds carrier-grade trust for the final checkout step, and static ISP holds one dedicated, never-rotating identity per bot account for the whole restock window.

Get restock proxiesSee which product fits
Scale

Cheaper per identity as the farm grows

A static ISP address is dedicated to one account and never rotates — a single bot or a thousand-account restock farm both draw from the same 1–1,000+ IP tier, with the per-IP rate falling automatically at volume.

Get restock proxiesSee which product fits
Health

Checked continuously, swapped before it fails twice

Private residential draws from the same 50M+ network as standard residential, but every address is checked continuously for blocks and bans — anything that fails is pulled and swapped for a clean one automatically, the tier to start on once a retailer's checkout starts trust-gating requests.

Get restock proxiesSee which product fits
How it works

Three steps, start to finish

1

Match the proxy to the restock

Private residential clears a retailer's anti-bot layer the moment checkout starts trust-gating — every address checked continuously and swapped on failure. Mobile adds carrier-grade trust for the final checkout step, and static ISP holds one dedicated identity per bot account for the whole restock window.

Restock matcher
Retailer trust-gates checkoutRecommendedPrivate Residential
Carrier-trust checkout stepRecommendedMobile
One identity per bot accountRecommendedStatic ISP
2

Target the market the drop is live in

Country, state, city and ASN targeting are included on every plan across 195+ countries, so a task farm can route through the same market a restock is actually selling in.

Targeting
United Statescountry-usLive
Germanycountry-deLive
Netherlandscountry-nlLive
3

Rotate or hold a session

A new IP per request for broad crawls, or a sticky session for anything that needs to stay logged in or paginate as one identity — the same toggle on every product.

Session
RotatingSticky 10mSticky 30m
Switch with -session
What's included

Built for retail copping

The product capabilities that actually matter for this job, line by line.

01Screening
Continuous
Private residential checks every address continuously for blocks and bans and swaps a failed one automatically — the tier to start on once checkout trust-gates.
02Identity
Never rotates
A static ISP address is virgin and dedicated to one bot account, holding its identity across the whole restock window.
03Carrier trust
Highest tier
Mobile IPs sit behind carrier-grade NAT shared with thousands of real subscribers — the highest trust score on the network, useful at checkout.
04Terms
1–180 days
Static ISP is rented by the term, from a single day up to 180 — hold an identity for exactly as long as the restock window needs it.
05Pool
50M+ IPs
The residential network private residential draws from, across 195+ countries — enough headroom that one drop doesn't burn through it.
06Uptime
99.9%, SLA-backed
The same SLA-backed uptime commitment covers private residential and mobile alike, measured per region.
On this network

Which product fits

Five products can carry retail copping traffic, each priced off the same live curve the dashboard charges from. Pick the one that fits the target.

Live

Private Residential

Start here once checkout starts trust-gating requests.

Built for thisContinuous screening, auto-swap
$2/GBat 1.5 TB · billed per gigabyte
Get Started
Live

Mobile

Adds carrier trust for the checkout step itself.

Built for thisCarrier-grade NAT, highest trust
$1.20/GBat 1.5 TB · billed per gigabyte
Get Started
Live

Static ISP

One dedicated identity per bot account for the whole restock window.

Built for thisVirgin IP, never rotates
$1.20/IPper IP at 1,000 IPs · 30-day term
Get Started
Live

Datacenter

Still the fastest, cheapest option while a retailer stays fully open.

Built for thisOwned subnets, edge DNS
$3.71/dayat 90 days · 50 Mbps · unmetered bandwidth
Get Started
Not sure which one? Start with Datacenter and move up as the target gets harder to pass.See full pricing

Questions, answered

Private residential — every address is checked continuously for blocks and bans, and anything that fails is pulled and swapped for a clean one automatically, which is what survives a restock checkout once it starts trust-gating requests.

Not necessarily — datacenter is still the fastest and cheapest option while a retailer doesn't aggressively block DC ranges. Most retailers move to trust-gating checkout after getting burned by bots at least once, which is when private residential, mobile and static ISP take over.

Yes — country, state, city and ASN targeting are included on every plan across 195+ countries, so results come back the way a real user in that market would see them.

Yes — a static ISP address is fixed for the length of the term you rent it, from a single day up to 180, so one account keeps the same identity from the first add-to-cart attempt through checkout.

Only for tasks that need to stay logged in or paginate as one identity — hold an IP for a session. For broad, stateless work, rotate a new IP per request instead; both are one setting on any product.

SerpProxies is for teams that move.Make your move.