Fake Reservation Holds: How Bots Tie Up Vehicle Inventory
How a hold becomes a weapon
Most reservation flows are built for trust: a name, an email, a small refundable deposit or sometimes no deposit at all, and the vehicle is marked reserved. That low friction is good for genuine buyers and easy to abuse at scale. A script can place holds across a whole lot in minutes, rotating emails and phone numbers so each request looks separate.
The damage is not just the hidden vehicles. Sales teams chase leads that will never answer, managers see false demand signals, and pricing tools read a shrinking available pool and push prices in the wrong direction. By the time the holds expire, the weekend shoppers who would have bought have gone elsewhere.
Signals that a hold is not real
Look for clusters: several holds placed seconds apart, contact details that fail basic validation, the same device or network placing holds under different names, and holds that always lapse at the maximum window without any reply to outreach. A single odd hold means little. A pattern across days means automation.
Deposit behavior is another signal. Fake holds favor no deposit paths, stolen or instantly declined payment methods, and refund requests routed to a different account than the one that paid. Tracking which holds convert to a conversation, not just which convert to a sale, gives a cleaner baseline.
Verification that does not punish real buyers
Add friction in proportion to risk. A verified phone code for a first hold, a modest deposit that is clearly refundable, and a short confirmation deadline with one reminder will stop most scripts while adding under a minute for a real buyer. Keep an assisted path: a shopper who fails an automated check should reach a person, not a dead end.
Expire and release promptly. When a hold lapses, return the vehicle to sale immediately and log the release. Slow manual releases extend the damage long after the attack itself has stopped, and they make inventory counts impossible to trust.
Cleaning up after a hold wave
Audit active holds against contact verification before canceling anything, and notify any genuine buyer affected. Then review the last thirty days of lapsed holds for the cluster signals above, so thresholds are set from your own data rather than a generic guess.
Share the pattern with neighboring stores in your group. Hold abuse often moves lot to lot once one store hardens its flow, and a shared early warning is cheaper than every store learning the same lesson separately.
Frequently asked questions
Why would anyone place a fake hold on a car?
Motives range from blocking a competitor inventory, testing whether stolen payment details work, scraping live pricing, to simply vandalizing a booking system. The dealer impact is the same regardless of motive: real vehicles disappear from sale and staff time is wasted.
Should every reservation require a deposit?
A small, clearly refundable deposit is one of the strongest filters, but it is not the only one. Verified contact details and short confirmation windows also work. The right mix depends on your market and how your genuine buyers already behave.
How long should a reservation hold last?
Long enough for a real buyer to arrange a visit or finance, short enough that abuse expires quickly. Many dealers use 24 to 48 hours with one extension on confirmed contact. Indefinite holds with no confirmation are the riskiest setting.
Can hold abuse affect advertised prices?
Yes, indirectly. Pricing and merchandising tools often react to available inventory. If fake holds shrink the visible pool, those tools may read scarcity that is not real and adjust prices or promotion placement on a false signal.
See your own numbers.
A free bot-traffic audit shows the human-automated split in your live traffic - no code changes, no commitment.
Get a free bot-traffic audit