AIO Bot Glossary: Every Sneaker Bot Term Explained

An AIO bot is an all-in-one bot: one piece of software that automates monitoring, carting, and checkout across many retailers instead of just one store. People use it on limited sneaker and collectible releases because one license, one set of profiles, and one task list work on Nike, Amazon, Pokémon Center, and more. This AIO bot glossary defines 59 terms in seven sections, from beginner basics to the settings you will see in the software.
- An AIO bot covers many stores with one license, while a single-site bot covers one, as the first comparison table shows.
- The four AIO tools in our retail bot cost comparison, including our own NikeShoeBot, cost $798 to $2,449 in year one, by our arithmetic on prices listed July 7, 2026.
- StockX says its Flex transaction fee runs from 9% at Level 1 to 7% at Level 5 from March 1, 2026, plus a 3% payment processing fee.
- On a $300 sale at Level 1, those fees take $36.00 and leave an $84.00 profit on a $180 pair, by our arithmetic in the resale section.
- Proxyway says reputable cook groups usually charge from $20 to $60 a month or more.
What Is an AIO Bot?
An AIO bot is all-in-one bot software: one tool that watches product pages, adds items to your cart, and checks out across many retailers, so you manage one license, one set of profiles, and one task list instead of a separate bot for every store.
A bot designed for one retailer or platform goes deep on a single checkout flow, while an AIO bot trades some of that focus for range. In practice, you set up tasks for each store inside the same app. Our full AIO bot guide covers setup and comparison, and this glossary covers the vocabulary.
Using one usually breaks a store’s terms of service, which our retail bot guide covers alongside the legal picture.
AIO Bot vs Single-site Bot: What Is the Difference?
An AIO bot differs from a single-site bot mainly in coverage, setup, and cost structure. A single-site bot is built around one retailer or platform, so it usually goes deeper on that checkout flow, while an AIO bot covers many stores at once and suits people who buy across categories.
Neither type guarantees a purchase, because stock, queues, and account health sit outside the software.
| Feature | AIO bot | Single-site bot |
|---|---|---|
| Store coverage | Many retailers in one tool | One retailer or platform |
| Setup | One app, profiles reused across stores | A separate setup per tool |
| Licensing | One license for the stack | One license per bot |
| Focus | Range across stores | Depth on one checkout flow |
| Best for | Buyers across several categories | Buyers who target a single store |
When comparing the two, check the supported-sites list and the total cost across every tool you would need. If you only buy from one store, a single-site tool can be enough. If you buy across three or more, one license may cost less than stacking separate bots, though the arithmetic depends on the listed prices.
Who Uses an AIO Bot, and Why?
AIO bot users fall into three groups: collectors, resellers, and people who run bots for others. EQL notes that some botters even sell a service where they run bots on a customer’s behalf.
Limited releases sell out in minutes at the shelf price, and speed, saved checkout details and monitoring are what a bot adds. An all-in-one tool lets one person cover a sneaker drop in the morning, and a trading-card restock in the afternoon without switching software.
CaptchaFox says brands have answered with raffles, app-exclusive releases and purchase limits, which moves the contest without ending it. That is why many users pair a bot with a cook group and a resale plan, as covered in how to become a sneaker reseller.
Sneaker Bot Basics: The First Terms You Will Meet
Sneaker bot basics are the ten terms that show up before anything else: what the software is, who sells the shoes, how releases work, and what a good result looks like.
Every row below gives a short definition, why it matters, a quick example, and a link to a deeper guide where we have one. Related terms link to other rows, so you can follow a thread.
If you already know the slang, skip to the proxies section. If you are new, read this table once from top to bottom, because the later sections assume these words.
| Term | Definition | Why it matters | Example | Related terms | Deeper guide |
|---|---|---|---|---|---|
| AIO Bot | All-in-one bot software that automates monitoring, carting, and checkout across many retailers. | One license and one setup can cover several stores. | One app holding tasks for a sneaker store and a card shop. | Sneaker bot, task, supported sites | AIO bot guide |
| Sneaker bot | Software that automates buying on sneaker releases. Some tools cover only sneaker stores. | It is the original use case that retail bots grew out of. | A bot built for Nike SNKRS or Footsites drops. | AIO bot, cop, drop/release | Best sneaker bots |
| Retailer | The store or platform selling the item, such as Nike, Amazon, or Pokémon Center. | Each retailer has its own checkout flow, limits, and rules. | Amazon, Walmart, and Pokémon Center run different checkouts. | Supported sites, rate limits, queue | Retail bots guide |
| Drop/release | The first time a product goes on sale. | Timing decides when your tasks must be ready. | A pair going on sale at 10:00 a.m. on a Saturday (hypothetical). | Restock, FCFS, raffle | – |
| Restock | When an item reappears after selling out. | Restocks are often unannounced, so monitoring is key. | A sold-out console returns to a store page overnight. | Release monitor, OOS, restock monitoring | Best Buy bot |
| Cop | Slang for buying something. | You will see it in every cook group and results channel. | “I copped the pair” means the order went through. | Checkout, W, L | – |
| Checkout | The step where you submit shipping, billing, and payment to place the order. | It is where most drop-day orders succeed or fail. | Pressing “place order” after the cart. | Cart, billing profile, session | How bots work |
| Retail price | The shelf price the retailer charges, often just called retail. | It is the cost basis for every profit calculation. | A pair priced at $180 at the store (hypothetical). | Resale value, break-even price, flipping | – |
| Resale | Selling an item after buying it, usually above retail. | It is where bot spending turns into profit or loss. | Listing that $180 pair on a marketplace for $200. | Market value, fees, net profit | Retail arbitrage |
| Success rate | The share of tasks or attempts that end in a successful checkout. | It is easy to quote and hard to compare fairly. | 3 checkouts from 40 tasks is a 7.5% rate. | Task, error state, proxy | – |
Does a Higher Success Rate Mean a Better Bot?
A success rate is the share of attempts that end in a checkout, and it says more about conditions than about the software.
Two users running the same bot on the same release can post very different rates, because stock, account health, proxies, task counts and the retailer’s defenses all differ. A rate quoted without the release, the store, and the number of tasks is a marketing number, not a measurement.
Compare like with like: the same retailer, a similar release type, and a stated task count. Treat any promise of a guaranteed rate with suspicion, since the retailer, not the bot, controls the stock.
Proxies and Networking Terms
Proxies are middle servers that pass your bot’s traffic to a store from a different IP address, and users reach for them to spread many tasks across many connections. Proxyway notes that your own IP address can be enough if you only want one pair.
Proxy types differ in cost, speed, and how easily a store flags them, and none of them guarantees a checkout. Retailers can still limit an account, an address, or a card, and using proxies may break a store’s terms. The table defines the nine terms you will see in a proxy tab.
Our residential proxies guide and sneaker proxies roundup go deeper on providers and setup.
| Term | Definition | Why it matters | Example | Related terms | Deeper guide |
|---|---|---|---|---|---|
| Proxy | A server that forwards your traffic so the store sees its IP address instead of yours. | It lets many tasks look like separate connections. | A task routed through a proxy in the store’s region. | IP address, proxy pool, proxy rotation | Sneaker proxies |
| Residential proxy | A proxy using a real consumer IP address assigned by an internet provider. | Stores trust these more, but they tend to cost more and run slower. | A task running through a home-network IP. | Datacenter proxy, ISP proxy, proxy rotation | Residential proxies |
| Datacenter proxy | A proxy hosted on cloud or server infrastructure instead of a home connection. | Fast and cheap, but flagged on most major sites by default. | A task running from a cloud-server IP. | Residential proxy, ISP proxy, rate limit | Datacenter proxies |
| ISP proxy | A static IP registered to an internet provider but hosted in a datacenter, also called static residential. | It sits between the other two on cost, speed, and detection risk. | One fixed IP assigned to one task for a whole release. | Residential proxy, datacenter proxy, proxy pool | – |
| Proxy pool | A set of proxies loaded into the bot for tasks to draw from. | Pool size and quality shape how many tasks can run at once. | 20 proxies assigned across 20 tasks. | Proxy, task, proxy rotation | – |
| IP address | The numeric address that identifies a connection to a website. | Stores watch it for volume, location, and reputation. | Dozens of requests from one address in a minute can look unusual. | Proxy, rate limit, session | – |
| Proxy rotation | Switching which proxy a connection uses, per request or at set intervals. | Sticky and rotating sessions are treated as separate choices. | Rotating mid-login can log an account out. | Proxy pool, session, IP address | – |
| Rate limit | A cap a store sets on how many requests it accepts from one source in a set time. | Hitting it can trigger errors, delays, or blocks. | A “too many requests” page after rapid refreshes. | Error state, task delays, IP address | – |
| CAPTCHA | A challenge that asks a visitor to prove they are human. | It can pause a task until someone solves it. | An “select all images with…” prompt at checkout. | Session, checkout, error state | – |
Residential vs Datacenter vs ISP Proxy: What to Know
Residential, datacenter, and ISP proxies sit on one spectrum of cost, speed, and how easily stores flag them. One technical overview puts datacenter at the cheap, fast, and often-flagged end, residential at the slower, pricier, and hardest-to-flag end, and ISP in the middle. Prices vary widely by provider, so we skip exact figures.
Pick by the store you target, not by the label. A security team that bought “sneaker proxies” found the term is not a real technical category, so ask what the IPs actually are. Use the table as a starting point and test any proxy before a release. You can read the full breakdown of the differences here.
| Proxy type | Cost | Speed | Detection risk | IP source |
|---|---|---|---|---|
| Datacenter | Lowest | Fastest | Highest | Cloud or hosting servers |
| ISP | Middle | Fast | Middle | Datacenter-hosted IPs registered to a provider |
| Residential | Highest | Slower | Lowest | Real home connections |
Does a Proxy Guarantee a Successful Checkout?
A proxy does not guarantee a checkout, because it only changes the connection and not the stock, the queue, or your account’s standing.
A clean proxy can still fail if the item sells out, the retailer limits the account, the payment is flagged, or the task hits a rate limit. Databay’s proxy guide warns that dead proxies waste task slots and says most bots include proxy testing. That is why many users test before a release.
Treat proxies as one input among several, along with account health and billing details, and never judge a bot by its proxies alone. Retailers can also act on terms-of-service grounds regardless of the connection.
Tasks, Accounts and Checkout Terms
Tasks, profiles, and accounts are the building blocks inside AIO bot software, and each one maps to a real step in a release.
The table walks through an imagined release: a pair going on sale at 10:00 a.m., a handful of tasks pointed at it, and a billing profile ready to pay. The examples are hypothetical, so adapt them to the store you target. After the table, we explain the pairs of terms beginners mix up most.
| Term | Definition | Why it matters | Example | Related terms | Deeper guide |
|---|---|---|---|---|---|
| Task | One automated run of the bot aimed at one product, size, or keyword on one store. | Tasks are the unit of attempts. More tasks mean more attempts, not more stock. | 5 tasks for size 10 on one store. | Task group, profile, proxy | How bots work |
| Task group | A saved set of tasks that start, stop, and edit together. | It saves setup time and keeps a release organized. | It saves setup time and keeps a release organized. | Task, account pool, task delays | – |
| Profile | Saved shipping, contact, and payment details the bot enters at checkout. | Wrong or mismatched details can get an order declined or cancelled. | A profile holding your real shipping address. | Billing profile, task, checkout flow | – |
| Billing profile | The card and billing-address part of a profile. | Stores and banks compare it, so it should match the card. | A billing address that matches the card statement. | Profile, checkout flow, error state | – |
| Account pool | A set of retailer logins the bot can use for its tasks. | Many stores want a login, and account health decides outcomes. | 3 aged logins loaded for one store. | Task group, session, profile | Amazon accounts |
| Queue | A virtual waiting room a store uses to order or slow shoppers during a release. | Your place in line, not raw speed, sets when you reach checkout. | A “you are in line” page at 10:00 a.m. | Queue drop, session, rate limit | – |
| Cart | The list of items held for purchase before payment. | A carted item is not always reserved. | Size 10 sits in the cart while payment loads. | Checkout flow, session, OOS | – |
| Checkout flow | The sequence of pages from cart to confirmation, which differs by store. | Bots need a module for each store’s flow, which is why coverage varies. | Cart, shipping, payment, review, confirm. | Checkout, one-click, profile | – |
| Session | The period your login and cart stay linked to a store. | Logging out or switching IPs mid-release can break it. | A cart that empties after a login timeout. | Account pool, proxy rotation, cart | – |
| One-click | A checkout shortcut that skips steps using saved details. | Fewer steps mean a faster order, where a store offers it. | An express-pay button on a product page. | Checkout flow, profile, cart | – |
| Error state | A failure such as a decline, timeout, block page, or rate limit message. | The message tells you whether to fix the profile, proxies, or timing. | “Payment declined” versus “Access denied”. | Rate limit, success rate, CAPTCHA | – |
What Is the Difference Between a Task and a Profile?
A task tells the bot what to buy and where, while a profile tells it who is buying and how to pay.
In a release, the task holds the product, size, and store, and the profile holds the name, address, and card. You can point many tasks at one profile, but CaptchaFox notes that stores enforce per-customer limits across accounts and addresses and deduplicate payment profiles, so reusing one profile everywhere has limits.
The same split applies to a task group and an account pool: the group organizes the attempts, and the pool supplies the logins. Get the profile right first, since a typo there fails every task that uses it. You can read more about the task-proxy ratio here.
What Does an Error State Mean on Drop Day?
An error state is any failure the bot reports, such as a decline, a timeout, a block page, or a rate limit message.
Read the message before changing anything. A decline points at the profile or the card, a timeout points at the connection or an overloaded store, and a block or rate limit message points at too many requests from one source. Changing three settings at once hides which one mattered.
Log the message and the time for each failure so you can compare releases. Over a few drops, the pattern tells you more than any single run.
Drop-day and Botting Terminology
Drop-day language is the slang people use in cook groups, release threads, and Discord channels, and most of it describes either the release format or the result.
The table covers the twelve terms you will see most often, with short examples. A few of them describe formats that a bot handles very differently, so we separate raffles from queue drops after the table.
Slang shifts between communities, so treat these as common usage and not official definitions.
| Term | Definition | Why it matters | Example | Related terms | Deeper guide |
|---|---|---|---|---|---|
| Cook group | A private community that shares drop alerts, early links, and insider information. | It is where many people hear about releases first. | A paid Discord server posting alerts before a release. | Early link, release monitor, shock drop | Cook groups |
| Early link | A product link shared before the official release goes live. | It can give tasks a head start where the link works. | A post with a link an hour before launch. | Cook group, release monitor, drop/release | – |
| Release Monitor | A tool or feed that alerts you when a new product or page appears. | It is how many users find out about a release. | An alert when a store creates a new product page. | Early link, restock monitoring, shock drop | Sneaker monitors |
| Shock drop | A release with no advance notice. | Monitoring and fast reactions matter more than calendars. | A product appears in a store with no warning. | Release monitor, FCFS, cook group | – |
| FCFS | First come, first served: the earliest successful orders get the stock. | EQL describes FCFS drops as a race between bots, so speed matters most. | A 10:00 a.m. release that sells out in minutes. | Drop/release, raffle, OOS | – |
| Raffle | A draw where you enter for a chance to buy instead of racing. | Speed stops mattering, and entry rules take over. | A 24-hour entry window with random winners. | Queue drop, FCFS, drop/release | – |
| Queue drop | A release that places shoppers in a virtual waiting room before checkout. | Your position, not raw speed, decides when you reach checkout. | A “you are in line” page at launch. | Queue, raffle, FCFS | – |
| OOS | Out of stock. | It ends a task or sends it back to monitoring. | A sold-out size on the product page. | Restock, restock monitoring, cart | – |
| L | A loss, meaning you failed to buy the item. | Losses are normal, which is why tracking results matters. | “Took an L on that release.” | W, cop, success rate | – |
| W | A win, meaning you bought the item. | It is the result everyone posts and the one that needs a resale plan. | “Took a W on size 10.” | L, cop, flipping | – |
| Flipping | Reselling an item soon after buying it for more than you paid. | It is the business behind most botting. | Buying at $180 and listing at $300. | Resale value, net profit, fees | How to become a reseller |
| Profit margin | Net profit as a share of the sale price. | It differs from ROI, which divides by your cost. | $84.00 profit on a $300 sale is a 28% margin | Net profit, ROI, fees | – |
Is a Raffle the Same as a Queue Drop?
A raffle and a queue drop both slow the rush, but a raffle picks winners at random and a queue lines shoppers up.
In a raffle, you enter during a window, and the store draws winners, so your entry is the only thing that counts. In a queue drop, you wait in a virtual line and then still check out against everyone else. CaptchaFox says raffle formats replace pure speed with time-windowed entry, which removes the advantage a bot cannot hide.
That is why raffle entry tools exist, and why stores add identity checks and limits to keep one entry per real person. Our Riot Games bot write-up shows how the store moved from first-come, first-served to a draw.
Reselling and Profit Terms
Resale terms describe what happens after the order lands, and they determine whether a successful checkout was a good one.
A pair that sells for more than retail can still lose money once fees, shipping, and bot costs come off. The table defines the eight terms, and the worked example below uses StockX’s published rates to show how much fees change the answer.
All prices in the examples are illustrative, so check each platform’s own fee page before you list.
| Term | Definition | Why it matters | Example | Related terms | Deeper guide |
|---|---|---|---|---|---|
| Resale value | What an item sells for on the secondary market. | It sets the top of your possible profit. | A $180 pair listing at $300. | Market value, fees, flipping | How to resell anything |
| Market value | The recent going price for an item, best read from completed sales. | Asking prices overstate what buyers actually pay. | The last several sold prices for one size. | Resale value, break-even price, retail price | – |
| Fees | Charges a platform takes from a sale, such as transaction and payment processing fees. | They are often the largest deduction. | StockX’s Flex rates run 9% to 7% plus 3% processing from March 1, 2026. | Net profit, resale value, marketplaces | – |
| Net profit | What you keep after costs, fees, and shipping. | It is the only profit figure that matters. | $264.00 payout minus $180.00 cost is $84.00. | ROI, profit margin, fees | – |
| ROI | Net profit divided by what you paid, as a percentage. | It compares flips of different sizes. | $84.00 ÷ $180.00 is 46.7%. | Net profit, profit margin, break-even price | – |
| Break-even price | The lowest sale price that returns your cost after fees. | It sets the floor before you buy or list. | $180 ÷ (1 – 0.12) is $204.55 at 12% total fees. | Fees, retail price, ROI | – |
| Deadstock (DS) | A pair as fresh as the day it left the factory: new, unworn, and unused. | Condition changes what buyers will pay. | A pair still in its sealed box. | Market value, resale value, flipping | – |
| StockX & other marketplaces | Platforms where buyers and sellers trade, each with its own fees and rules. | Different platforms pay different net amounts for the same sale. | Selling the same item on StockX versus a live-selling platform. | Fees, net profit, market value | – |
How Much Do Fees Change a Flip’s Profit?
Fees decide how much of the gap between retail and resale you keep, and at the rates below, they take 10% to 12% of the sale price.
StockX’s February 24, 2026 announcement lists Flex transaction fees from 9% at Level 1 down to 7% at Level 5, plus a 3% payment processing fee. The table applies them to a $300 sale of a $180 pair, using our own arithmetic.
| Line item | Level 1 | Level 5 |
|---|---|---|
| Resale price | $300.00 | $300.00 |
| Transaction fee (9%/7%) | -$27.00 | -$21.00 |
| Payment processing (3%) | -$9.00 | -$9.00 |
| Net payout | $264.00 | $270.00 |
| Retail cost | $180.00 | $180.00 |
| Net profit | $84.00 | $90.00 |
| ROI | 46.7% | 50.0% |
| Profit margin | 28.0% | 30.0% |
The gross gap here is $120. At Level 1, fees take $36.00, which is 30% of that gap. At Level 5, they take $30.00, so seller level moves the answer by $6.00 on this one sale.
Standard, non-Flex sales work differently. StockX says the US seller shipping fee for them rose from $4 to $5 on March 1, 2026, and that post does not cover the other non-Flex rates. Check StockX’s current fee page before you price a listing, and count bot, proxy, and account costs too.
AIO Bot Features and Technical Terms
AIO bot features are the settings and specs you compare when choosing software, and each term below describes what a listing means, not which tool is better.
We make NikeShoeBot, so this section sticks to definitions and to the pricing shapes vendors publish, and it lists vendors from highest to lowest first-year cost. Verify every spec on the vendor’s own page before you pay.
| Term | Definition | Why it matters | Example | Related terms | Deeper guide |
|---|---|---|---|---|---|
| Supported sites | The retailers a bot can run tasks on. | Coverage has to match where you actually buy. | A listing naming Amazon, Walmart, and Pokémon Center. | Retailer, checkout flow, task | – |
| Task automation | Features that start, stop, and repeat tasks without manual input. | It cuts setup time on busy release days. | A task group that starts at a set time. | Task group, monitoring, task delays | – |
| Monitoring | Watching a page, keyword, or feed for changes. | It triggers tasks the moment something appears. | A keyword monitor on a store’s new arrivals. | Release monitor, restock monitoring, task automation | – |
| Task delays | A wait between steps or retries, set in the bot. | Too short can trigger rate limits; too long can miss stock. | A retry delay after a failed add-to-cart. | Rate limit handling, error state, task | – |
| Restock monitoring | Watching a sold-out page for items to return. | Restocks are often unannounced. | A monitor on a sold-out console page. | Restock, OOS, monitoring | – |
| Rate limit handling | Bot settings that keep requests under a store’s caps. | Poor settings lead to errors and blocks. | A setting that slows requests after a block page. | Rate limit, task delays, error state | – |
| Updates | Software changes that adjust to retailers’ checkout changes. | Stores change often, so ask how quickly bot fixes ship. | A patch after a store redesigns its cart page. | Checkout flow, supported sites, licensing | – |
| Licensing | The terms for using the software, usually a subscription by period. | Renewal periods differ, so compare the first-year total. | A listing priced per 3 or 6 months. | Updates, supported sites, cloud vs local operation | Bot cost |
| Cloud vs local operation | Local runs on your own computer, while cloud runs on a remote server. | It affects hardware needs, connection reliance, and cost. | A laptop on home Wi-Fi versus a rented server. | Task automation, proxy, licensing | – |
Which AIO Bot Features Should You Compare First?
Supported sites, licensing, and updates are the three features to compare first, because they decide whether a tool fits your stores and budget.
Licensing shapes differ. On the prices in our July 7, 2026 comparison, Refract works out to $2,449 in year one ($1,999 plus 9 × $50), Stellar AIO to $1,196 (4 × $299), The Shit Bot to $798 (2 × $399), and NikeShoeBot at $499 every 6 months or $99 a month, all by our arithmetic. Confirm each on the vendor’s page.
After that, check updates and support, then task delays and monitoring options. Features that look identical on a listing can behave differently on a release, so read recent user reports and not just the spec sheet.
Is Cloud or Local Operation Better for an AIO Bot?
Cloud and local operation describe where the bot software runs: on a remote server or on your own computer.
Local operation uses your own hardware and connection, so a weak laptop or unstable Wi-Fi limits you. Cloud operation moves the work to a rented server, which can reduce that dependence but adds a monthly cost and means trusting the host with your setup.
Neither is better in general, and not every tool offers both. Compare the listed options, your hardware, and your budget, and test on a low-stakes release first. Where a tool lists cloud support, check whether it costs extra.





