Sneaker Proxies for Compliant Checkout Automation and Raffle Entries

Quick answer

For checkout automation on retailers that permit bots, and for raffle entries on accounts you own, you need two things: a static IP per account for the checkout itself and rotating residential IPs for watching stock and release pages. ISP proxies are the recommended product for checkout, from $1.25/IP; residential proxies handle the monitoring side.

Why checkout automation breaks without the right proxies

A drop compresses a day's traffic into minutes. Retailers respond with queues, per-IP rate limits, challenges and session checks that compare the IP at cart with the IP at payment. Several tasks from one home connection means the first gets through and the rest see HTTP 429 or a challenge page.

Datacenter ranges are the wrong fix: most drop pages serve them a CAPTCHA or an empty queue. Shared rotating IPs fail differently: the address changes between cart and payment, the session breaks and the order is dropped.

What works is a consumer-grade IP that stays fixed for the whole checkout, one per account, on retailers whose terms allow it. Raffles have the same shape: one entry per real person, from one consistent IP.

Which Geonode proxy type fits

For the checkout path, ISP proxies fit best. Each is a static IP from a real ISP with unlimited bandwidth and sessions, so a task keeps one address from product page to order confirmation with no session mismatch caused by the proxy. Price starts at $1.25/IP, which makes one IP per account affordable.

For monitoring, residential proxies are better. Watching a stock endpoint means many small requests over hours, and rotating through Geonode's 2.5M online residential IPs spreads that load across real consumer exits. Country and city targeting let you watch the regional store that matters. Residential is pay-as-you-go from $0.27/GB at volume, so monitoring does not eat into your static IP budget.

Datacenter proxies have one role here: polling your own servers or non-protected public APIs.

Residential — Best for: Stock and release monitoring, regional store checks, raffle status pages; IP source: Real consumer devices, 195+ countries; Session: Rotating or sticky up to 24 h; Price from: $0.27/GB at volume
ISP (static residential) — Best for: Checkout tasks and raffle entries, one fixed IP per account; IP source: Static IPs from real ISPs; Session: Unlimited, static; Price from: $1.25/IP
Datacenter — Best for: Polling your own services and non-protected endpoints; IP source: Rotating datacenter ranges; Session: Rotating; Price from: $0.14/GB

Recommendation: ISP for checkout, because the whole task depends on the IP not changing. Residential for monitoring, because that side depends on spreading load.

How to set it up

Confirm the retailer's terms permit automated checkout or raffle entries for the drop. If they do not, use the proxies for monitoring only and buy manually.
Buy one ISP proxy per account you will check out with. Record the mapping of account to IP and never reuse an IP across accounts in the same drop.
Create a residential username with country targeting for the store's region, rotating, for the monitor that polls product and stock pages before the release.
In your bot or script, assign the ISP proxy to the checkout task and the residential username to the monitor. Keep them on separate credentials and separate processes.

// verify endpoint against docs.geonode.com before publishing
// Node: residential monitor (rotating) + ISP checkout (static)
const { chromium } = require("playwright");

const MONITOR = "http://USERNAME-country-us:PASSWORD@premium-residential.geonode.com:9000";
const CHECKOUT = "http://USER:PASS@ISP_IP:PORT"; // your static ISP proxy from the dashboard

(async () => {
  const monitor = await chromium.launch({ proxy: { server: MONITOR } });
  const page = await monitor.newPage();
  await page.goto("https://store.example.com/product/release-123", { waitUntil: "domcontentloaded" });
  const inStock = await page.locator("button:has-text('Add to cart')").count();
  await monitor.close();

  if (inStock) {
    const buyer = await chromium.launch({ proxy: { server: CHECKOUT } });
    // run the checkout flow for ONE account on this static IP
    await buyer.close();
  }
})();

Get the exact snippet for your language from the API Code Generator in the dashboard.

Checkout automation-specific settings that matter

One static IP per account, never shared

The checkout session must see one address from cart to confirmation. Map each account to its own ISP proxy and keep that mapping across drops. Rotating during checkout is the most common cause of dropped orders, and sharing one IP across accounts is the most common cause of challenge pages.

Rotate the monitor, not the buyer

Release and stock monitors should rotate through residential exits so no single IP polls the page hundreds of times. The buyer never rotates. Keep the two on different credentials so a throttled monitor cannot affect checkout.

Target the store's country

Regional stores run separate inventories and release times. Set the residential username to the country of the store you are watching, and buy ISP proxies in the same country so the checkout address matches the shipping region.

Low concurrency, honest pacing

Concurrency is not a lever here. A handful of well-paced tasks on static IPs beats hundreds that trip the rate limit. Add short delays between steps and treat a 429 as a signal to slow that task, not to spawn more.

Log everything per task

Record IP, task id, step, status code and timing. The post-drop review shows which step failed and whether it was the retailer's queue, your pacing or a session issue.

What Geonode gives you for checkout automation

ISP proxies with static IPs from real ISPs, unlimited bandwidth and unlimited sessions
Residential monitoring exits in 195+ countries with country and city targeting
Sticky residential sessions up to 24 hours for raffle status pages and account dashboards
HTTP, HTTPS and SOCKS5 on ISP; HTTP, HTTPS, SOCKS5 and UDP on residential
24/7 support and card or crypto payment, no contract

Pricing for checkout automation

ISP proxies start at $1.25/IP with unlimited bandwidth and sessions, so one static address per account costs little. Residential monitoring is pay-as-you-go from $0.27/GB at volume, with an entry plan of 10 GB for $7.92 per month, a 3-day trial for $5 and no contract. Datacenter proxies for polling your own services start at $0.14/GB. See the pricing page for every tier.

FAQ

What sneaker proxies should I use for checkout?

ISP proxies. A checkout needs one consumer-grade IP that does not change between cart and payment, and ISP proxies are static IPs from real ISPs with unlimited sessions. Assign one per account and keep your monitors on separate residential credentials.

Are residential sneaker proxies good enough for checkout?

Residential sticky sessions can hold an IP for up to 24 hours, but the IP may change earlier if the underlying device goes offline. For a time-critical checkout that risk is not worth taking; use residential for monitoring and ISP for the purchase itself.

Can I run many tasks on one proxy?

You can, but you should not during a drop. Retailers rate limit per IP, so stacking tasks on one address produces 429 responses and challenge pages for all of them. The reliable pattern is one task, one account, one static IP.

Is using sneaker proxies for bots allowed?

Only on retailers whose terms permit automated purchasing or raffle entries, and only on accounts you own or manage with authorisation. Respect platform terms and rate limits. Geonode's acceptable use policy prohibits fraud, spam and credential abuse, and we do not support evading retailer restrictions.

Which country should my proxies be in?

The same country as the store and the shipping address. Regional stores run separate releases, and a checkout from an address far from the delivery region is a common reason for cancelled orders. Geonode offers residential exits in 195+ countries and ISP proxies by location.

How much residential bandwidth does monitoring use?

Monitoring is many small requests, so the 10 GB entry plan usually covers a season of release watching for a small operation. Polling full product pages in a headless browser uses more than hitting a stock endpoint, so prefer the lighter request where the retailer exposes one.

Start

Buy one ISP proxy per account, set up a rotating residential monitor for the store's country, and run a dry test before the next release. Get started or Contact sales for larger ISP allocations.