--- title: What is Scalping bots source_page: https://www.sardine.ai/learn/scalping-bots canonical: https://www.sardine.ai/learn/scalping-bots format: text/markdown description: For an e-commerce team, scalping bots are the automation that clears limited inventory in seconds, and the tell is checkout latency dropping below human speed. --- **Quick links:** [Human page](https://www.sardine.ai/learn/scalping-bots) · [Home](https://www.sardine.ai) · [Customers](https://www.sardine.ai/customers) · [Blog](https://www.sardine.ai/blog) · [Demo](https://www.sardine.ai/demo) --- # What is Scalping bots **Read time:** 4 For an e-commerce team, scalping bots are the automation that clears limited inventory in seconds, and the tell is checkout latency dropping below human speed. Scalping bots are automated scripts that buy up limited-stock items the instant they drop, faster than any human could, so the operator can resell them at a markup. Known as Grinch bots around big product launches, they turn scarcity into profit by clearing inventory before genuine shoppers ever load the page. What are scalping bots? Scalping bots are software that automates the entire buying flow for scarce, high-demand goods: sneaker drops, concert tickets, game consoles, graphics cards, collectibles. The bot monitors for a release, adds to cart, and checks out in milliseconds, repeating across many accounts at once so it sweeps up far more units than the per-customer limit is meant to allow. They are also called Grinch bots, especially during holiday launches, because they strip shelves bare before real buyers get a chance. The goal is not to use the item; it is to corner the supply and flip it on a resale market at a premium, sometimes many times the retail price. For a fraud team, scalping sits in the wider family of automated abuse, next to credential stuffing and bulk account creation. The purchases themselves may be paid with valid cards, so this is often less about payment fraud and more about a bot army defeating fairness controls and inventory limits. How a scalping run unfolds A launch-day scalping operation generally follows this arc, from prep to resale: Prep — Stockpile accounts and proxies. The operator lines up hundreds of accounts, payment methods, addresses, and rotating proxies ahead of the drop. Watch — Monitor for the release. Bots poll the product page or API constantly, ready to fire the instant stock flips to available. Grab — Add to cart and check out. Automated checkout completes in milliseconds across many accounts, clearing units before humans can react. Flip — Resell at a markup. The hoarded inventory is listed on secondary marketplaces at a premium, turning artificial scarcity into profit. Who is involved? What it looks like in practice A retailer launches a limited console at ten in the morning. In the first ninety seconds, checkout volume spikes to many times a normal peak, and inventory sells out. Looking closer, most orders came from newly created accounts, hundreds of them share a handful of shipping addresses, and the time from page load to purchase averages under a second. Genuine customers flood support saying the item vanished before they could add it to a cart. Within the hour, dozens of listings for the same console appear on a resale site at double the price. The order pattern, thousands of near-instant checkouts from fresh accounts behind rotating IPs, is the unmistakable fingerprint of a scalping run. Why it is dangerous for operators Scalping is dangerous partly because the payments can be legitimate, so it slips past payment-fraud controls and shows up instead as a fairness and inventory problem. Real customers walk away angry, the brand takes the blame for a launch they did not botch, and the value that should have reached fans flows to resellers instead. It also degrades the platform in the moment. A launch-day flood of bot traffic can spike infrastructure load, distort demand signals, and crowd out humans entirely, and the same account and proxy stockpiles that power scalping often overlap with credential stuffing and account farming, so a scalping spike can be the visible edge of a broader automation problem. What to watch in the data Impossible speed. Time from page load to checkout measured in milliseconds, far faster than any human could add to cart and pay. Fresh account surge. A burst of newly created or long-dormant accounts all buying the same SKU the instant it drops. Shared endpoints. Many orders funneling to a small set of shipping addresses, emails, or payment methods behind rotating proxies. Traffic spikes on drop. Request volume to the product page or API jumping to many multiples of baseline right at release time. Uniform behavior. Identical navigation paths, headers, or timing across sessions, the signature of scripted rather than human buyers. Quick questions ### Are scalping bots illegal? It depends on the item and the jurisdiction. Bots that bypass ticket-purchasing controls are banned in some places, while sneaker and console scalping is often a terms-of-service violation rather than a crime. Either way, retailers treat it as abuse worth blocking. ### Why are they called Grinch bots? The nickname comes from holiday shopping, when these bots snap up the season's hottest toys and gifts before families can buy them, leaving shelves empty. It is the same scalping behavior, just named for its impact around the holidays. ### How is scalping different from payment fraud? Scalpers usually pay with valid cards and complete real purchases, so there is often no chargeback or stolen credential involved. The harm is in defeating purchase limits and fairness controls to hoard supply, not in the payment itself. ### How do bots beat per-customer limits? They spread purchases across hundreds of accounts, each with different emails, addresses, and payment methods, and route through rotating proxies so the traffic looks like many separate shoppers. That way a limit of one or two per customer becomes hundreds per operator. ### What defenses actually work? Layered controls: bot detection on the drop, rate limiting, waiting rooms and queues, device and behavioral fingerprinting, CAPTCHA challenges, and tighter account-age and verification rules. No single control is enough, since operators adapt quickly to any one measure. ### What should a team do on launch day? Monitor checkout speed, account age, and address concentration in real time, throttle or queue suspicious traffic, and cancel orders that show clear automation fingerprints. Linking shared accounts, devices, and endpoints after the fact helps claw back hoarded inventory.