Proxies for Pokémon Center: beating the hardest restock in retail

Trading card hype turned Pokémon Center from a merch store into one of the most contested checkouts on the internet. Elite trainer boxes, Pokémon Center exclusives and new set launches sell out in minutes, restocks arrive without a countdown, and the store answers with bot protection that runners rank alongside the hardest Shopify drops. The proxy setup that survives it is specific, and this guide lays it out.

What makes Pokémon Center different

Three layers, where most retail sites run one. First, a network check: datacenter ASNs are rejected outright and consumer ranges are scored on subnet reputation, the mechanism explained in why proxies get banned on release day. Second, a session check: scheduled launches run through a queue, and the fingerprint and IP that enter the queue are expected to be the ones that reach payment. Third, and unusual in retail, a review after the order: confirmation emails are not final, and orders that share an address, a payment method or a suspicious pattern across accounts have a habit of being cancelled days later. A proxy setup has to pass all three, and the third one is what trips runners who beat the first two.

The IP side: dedicated static ISP, pinned per account

Dedicated ISP proxies clear the network check twice over: a consumer carrier ASN, so the hosting filter passes, and dedicated allocation, so the subnet history is only yours. Porter ranges are US carrier ranges, which matches the US store. Then pin one IP to one account and leave it there. The account that browses, queues and checks out from the same address every time reads as one customer; an account that appears from a different IP each visit reads as a shared login, which feeds the post-order review. Static through the whole flow, queue to payment.

Sizing: count accounts, not tasks

Pokémon Center limits quantity per order and polices duplicates per account and address, so throwing fifty tasks at one account gains nothing and raises the cancellation odds. The unit of scale is the account, each with its own shipping profile, payment and dedicated IP. A setup of 5 to 10 accounts wants 5 to 10 ISP IPs, and grows one IP per account from there. That is the retail version of the one-IP-per-task rule from the sizing guide.

Monitors go on residential, always

Restocks are the stakeout problem: nobody announces the 3am reappearance of a sold-out box, so monitors have to run for days. A checkout IP that spent those days polling product pages arrives at the moment of purchase with a request history that looks nothing like a shopper. Keep monitors on rotating residential proxies, where per-request rotation means no address builds a pattern and per-GB billing means a quiet week costs almost nothing. Budgeting that side is covered in how many GB of residential proxies do you need. Checkout IPs stay quiet until stock flips.

Launch day versus restock hunting

Scheduled launches reward preparation: accounts warmed on their pinned IPs, monitors already running, and nothing rotated once the queue opens. If the tool runs the queue on residential for any reason, use a sticky session that holds one household IP from entry to checkout; Porter sticky sessions hold up to 60 hours. Restock hunting rewards persistence instead, and it is where the term choice matters. Monthly ISP terms keep account identities warm across weeks of waiting, from $2.50 per IP. Daily plans fit a single scheduled launch for a runner who does not hunt restocks in between.

When a range cools

Pokémon Center scores subnets, and a range that carted heavily on a launch can arrive at the next one pre-flagged even when every address in it is yours. Swap subnets from the dashboard before the next launch rather than riding a tired range into it, and re-pin accounts to the new IPs so each identity moves once, cleanly, instead of wobbling between addresses.

The mistakes that get carts cancelled

• Datacenter or shared ISP ranges. Fail the network check or carry other people’s cart history. Dedicated allocation or nothing.
• Several accounts on one IP. Links the accounts for the post-order review and takes all of them down together.
• Rotating during the queue or checkout. The session that reaches payment must be the one that entered.
• Identical shipping details across accounts. Not a proxy problem, but the proxy cannot save a setup that fails it.
• Monitoring from checkout IPs. Pre-flags the cleanest identities before the restock even appears.
• Buying tasks instead of accounts. Order limits make the extra tasks pure risk.

The wider restock picture, including Target, Walmart and Best Buy, lives on the retail proxies page. For Pokémon Center specifically: consumer IPs, dedicated, one per account, static from queue to payment, monitors elsewhere, and details that would survive a human review.