Denial of inventory is the automated threat behind seat spinning, and it affects any business that lets a customer reserve something before paying for it. The OWASP Automated Threats to Web Applications project catalogs it as OAT-021 and defines it as depleting “goods or services stock without ever completing the purchase or committing to the transaction.” OWASP lists seat spinning as one of its alternate names, alongside inventory hoarding and inventory exhaustion.
Airlines are the best-known target because their pricing responds so quickly to availability. The same mechanics apply to hotel rooms, event tickets, restaurant tables, and retail carts, wherever a temporary reservation exists to give a customer time to decide.
How OWASP automated threats classify inventory abuse
The taxonomy separates denial of inventory from two related threats. Scalping (OAT-005) also reduces availability, but the attacker acquires the goods to resell them. Denial of service (OAT-015) applies when an attack exhausts server resources rather than stock. In a denial of inventory attack, the attacker doesn’t buy anything; the goal is to keep other customers from buying the inventory long enough to profit from the shortage or harm the seller.
Scalping defenses often concentrate on checkout and payment, where the scalper eventually has to transact, but a denial of inventory campaign never reaches payment, so controls that wait for checkout never engage. A shared taxonomy also helps teams in different industries compare findings, since a hotel security team and an airline fraud team that both cite OAT-021 mean the same behavior.
Inventory hoarding across industries
Hotels face room holds that block availability during peak events, often from operators who resell rooms through their own channels or want to push travelers toward a competing property. Event ticketing platforms see automated clients place tickets in carts during an on-sale, keeping seats away from fans while the operator decides which ones to buy. Restaurants and reservation platforms see prime-time tables booked in bulk, either to resell the reservations or to deny them to a rival. Retailers see inventory hoarding in carts and click-and-collect orders during limited releases, when buyers who find nothing in stock turn to secondary markets.
Each case follows the seat spinning pattern: find a scarce item, reserve it with a valid request, let the reservation lapse or cancel it, and repeat. The economics are the same as well: it costs the attacker nothing to hold the inventory, but the holds can still raise prices, divert customers, or damage the seller's reputation.
The OWASP definition also covers less obvious inventory, including availability slots, queue positions, service allocations, and product rations. Appointment booking systems, waitlists, and limited-quantity allocations have the same exposure whenever a slot can be claimed before it's paid for or confirmed.
Denial of inventory is business logic abuse
Every request in a denial of inventory campaign uses a feature the application provides on purpose. Nothing in the payload is malformed, so WAF signatures have nothing to match. CAPTCHA usually triggers at login or payment, after the reservation exists. Rate limits miss automation that spreads across residential proxies and throttles itself. The abuse becomes visible only when a defense evaluates an entity's behavior across the whole reservation flow and compares it with how real customers behave, which is the defining trait of business logic abuse.
Across industries, the same detection signals point to the same intent: reservations that rarely or never convert to payment, reservation attempts that occur faster than a person could fill in a form, sessions that skip the comparison shopping real customers do, and a small cluster of sources responsible for most reservations, whether the inventory is a seat, a room, or a pair of limited-release sneakers.
Seat spinning detection applies to any reservation flow
Cequence built its approach to seat spinning on the same principle it applies to business logic abuse in retail, financial services, and telecommunications: model how legitimate users move through an application, then flag the journeys that don't fit. Cequence Bot Management correlates search, reservation, and payment activity across sessions and rotating IPs. It flags “impossible journeys” that no human could complete, and it also catches bots whose journeys look plausible but whose reservations rarely turn into purchases. It stops the shopping bots behind cart-based inventory hoarding with the same behavioral models it uses for seat holds.
In two airline engagements, a small cluster of automated sources was behind most flagged holds, and the same detection applies to a hotel's room holds or a retailer's carts. Operators that find a website protected often move to partner and aggregator APIs, where protection tends to be weaker. Cequence deploys at the network level without JavaScript or mobile SDKs, and it runs bot management and API security on one platform, so the same protection covers the website and every API that can create a reservation.
The seat spinning series
This post is part of a series on seat spinning:
- Airline Seat Spinning: An Illustration of Sophisticated Fraud
- Airline Inventory Fraud: The Economics of Seat Spinning
- Seat Spinning Bots: Anatomy of a Spin Campaign
- Seat Spinning Mitigation: Detection to Enforcement at Two Airlines
- AI Booking Agents: The Next Phase of Seat Spinning
- Denial of Inventory: Seat Spinning Beyond Airlines




