Contents
Every few weeks, a pair of sneakers drops and sells out in under a minute. The retail price is £180. By the following morning, the same pair was listed on StockX for £450. A week later, it was £600.
If you have ever tried to buy a hyped release manually — refreshing the page, filling in your details as fast as humanly possible, watching the size you wanted disappear before you reach the payment screen — you already understand the problem. The people walking away with multiple pairs are not faster than you. They are running different infrastructure.
This guide explains what that infrastructure looks like, how it fits together, and what actually determines whether it works.
The Basic Picture
The sneaker resale ecosystem runs on automation. Sneaker bots — software that completes the checkout process faster than any human can — have been part of high-demand releases for well over a decade. The retailers know this. They have built increasingly sophisticated countermeasures. The bot developers have responded. The countermeasures have evolved further.
What exists in 2026 is an arms race that has been running long enough to produce a fairly stable set of tools on both sides. Retailers use bot detection systems that flag suspicious traffic patterns, block known IP addresses, and impose rate limits on requests that arrive too quickly or from the same source too many times. Both users counter with software designed to mimic human behaviour and proxy networks that distribute requests across thousands of different IP addresses.
Understanding this dynamic is the starting point for understanding why the setup matters as much as the software.
What a Sneaker Bot Actually Does
A sneaker bot automates the steps between a product page loading and a checkout completing. At its most basic, it monitors a product URL, adds the item to cart the moment it becomes available, fills in payment and shipping details, and submits the order — all in the time it takes a human to read the page title.
The better bots do considerably more than this. They handle queue systems, solve certain types of CAPTCHA challenges, manage multiple tasks simultaneously across different sizes or colourways, and adapt their behaviour to the specific checkout flow of each retailer. Nike’s SNKRS app works differently from Footlocker’s website, which works differently from a Shopify-based boutique. A bot that handles one well may struggle with another.
For beginners, the key things to understand about bots are: they are not magic, they require configuration, and the bot itself is only one part of the setup. Many people buy an expensive bot, run it without the right supporting infrastructure, and wonder why it does not work. The bot is the engine. Proxies are the wheels. Without both, you are not going anywhere.
Why Proxies Are Non-Negotiable
When a bot runs multiple tasks simultaneously — attempting to secure several pairs at once, or running the same task repeatedly to improve the odds — all of those requests originate from your IP address. From the retailer’s perspective, this looks exactly like what it is: automated traffic from a single source. The response is a ban. Your IP gets blocked, your tasks fail, and the release is over before you have secured anything.
Proxies solve this by routing each task through a different IP address. Instead of hundreds of requests coming from one location, the retailer sees what looks like hundreds of different shoppers. Each request carries a different IP, a different digital fingerprint, a different apparent location.
The quality of those proxies determines a great deal. Sneaker proxies — proxy networks built specifically for high-demand retail environments — use residential or ISP-assigned IP addresses rather than data centre IPs. The distinction matters because retailers’ bot detection systems have become very good at identifying data centre IP ranges and treating traffic from them with heightened suspicion. A residential IP looks like a home broadband user. A data centre IP looks like a server. On a hyped Nike drop, that difference can be the gap between a successful checkout and an instant ban.
Proxy location also matters. For region-locked releases or retailers that vary their inventory by market, running proxies in the right country — or even the right city — affects both access and detection risk.
The Main Components of a Working Setup
The bot. The market has consolidated around a relatively small number of well-regarded options. Nike Shoe Bot, Cybersole, Kodai, and Wrath are among the names that come up consistently for UK and European releases. Each has strengths on particular sites. Research which bot has the strongest track record on the specific retailers you are targeting rather than assuming the most expensive option is the best overall.
Proxies. Covered above, but worth repeating: residential or ISP proxies from a provider with a clean pool and genuine geographic coverage in your target market. Avoid free proxies entirely — they are either dead, shared with too many other users, or already banned.
Accounts. Many releases, particularly on Nike SNKRS and Adidas, require authenticated accounts to enter draws or complete purchases. Having multiple aged accounts — accounts that have been created and used over time rather than generated in bulk immediately before a drop — improves your odds on platforms that factor account history into draw entries. Account generation and management is its own discipline, but for beginners, the key point is that a bot without accounts is limited on the platforms that matter most.
Billing and shipping profiles. Your bot needs complete, accurate checkout profiles — payment details, shipping addresses, contact information — ready to go before a drop. Incomplete profiles cause checkout failures at the worst possible moment. Some bot users maintain multiple profiles across different cards and addresses to reduce the risk of payment flags.
What the Preparation Actually Looks Like
Success on a hyped drop is mostly determined before the drop starts. The checklist that serious bot users work through in the days before a release covers: confirming the drop time and format (immediate purchase, draw, or queue), checking which retailers are carrying the release and in what quantities, loading and testing tasks in the bot, verifying that proxies are working and not banned on target sites, and confirming that accounts are in good standing.
The testing step is frequently skipped by beginners and frequently cited by experienced users as one of the most important parts of the process. Running a test task against the retailer’s site — not during the drop, but in the days before — confirms that your proxy and account combination can reach the site cleanly and complete the checkout flow without triggering detection. A proxy that works fine on one retailer may be flagged on another. Finding this out before the drop costs nothing. Finding it out during the drop costs the cop.
Honest Expectations
None of this guarantees success. The retailers are not standing still, and neither are their bot detection systems. A setup that works well on one release may need adjusting for the next. Proxy pools that are clean today accumulate bans over time and need refreshing. Bot updates arrive regularly and sometimes break existing task configurations.
The people who consistently cop at scale treat this as an ongoing technical practice rather than a one-time setup. They monitor bot developer Discord servers for site-specific advice before drops, maintain relationships with proxy providers who communicate about pool quality, and review what worked and what did not after each release.
For a beginner, the realistic goal is not to match that level of operation immediately. It is to build a working setup, understand why each component matters, and develop enough familiarity with the process to improve it over time. The floor for entry has come down considerably as bot and proxy providers have made their tools more accessible.
The ceiling, as anyone watching the resale market already knows, remains very high.
