Protect a scarce model release the way you would protect any limited inventory: hold deposits per verified identity, confirm by phone before the order banks, and keep a waitlist you control. A first come form with no verification will be gamed when resale value is real.
A refundable deposit is a free option for a bot
Refundable deposits change the economics. A script that places fifty holds risks nothing if forty nine are refunded, and it gains first position on the one allocation that matters. Queue and bot management vendors document the same pattern in retail drops: inventory hoarding, where automated holds lock stock that human buyers then cannot reach, whether or not the holder ever completes the purchase.
Dealers feel a softer version of it. The deposit list looks like demand, the manufacturer sees interest, and then half the list evaporates when confirmation calls start. The harm is not just the fake holds. It is the real customer told the allocation was gone who bought a competing model that week.
Verification that respects a real buyer
Match the friction to the scarcity. For a normal order, a form and a callback are fine. For a limited run, require a card hold rather than a saved card number, one reservation per payment instrument and address, and a live confirmation call before the reservation converts to an order. Real buyers tolerate a two minute call for a car they have waited a year for.
Say the rules on the page before the release opens: one per household, non transferable, deposit refunded if the store cannot supply. Rules written after a release look invented, and in a dispute about who was first, the timestamped page is the document everyone reaches for.
The waitlist is the pressure valve
A controlled waitlist turns a failed reservation into a relationship instead of a dead end. When a hold fails confirmation, the next verified waitlist name gets a short, stated window, four business hours is workable, before the slot moves on. That order, published in advance, is what makes the process defensible when someone complains.
Keep the waitlist in the CRM with the same identity checks as the deposit list. A waitlist built from unverified form fills inherits the same bots, just one step later, and staff end up calling numbers that were never a person.
Read the release data before the next one
After the release, count holds by IP range, by time to complete the form, and by confirmation success. A cluster of sub ten second completions from one range is not a mystery to solve. It is a rule to write before the next allocation. Share the summary with the manufacturer rep if allocation politics are in play. Documented abuse travels better than a complaint about fairness.
Scarce models will keep drawing scripts as long as resale premiums exist. The goal is not a perfect gate. It is a gate where a human with a genuine order beats a script holding free options.
Keep reading
Related guides on this site: how inventory hoarding bots lock stock floorplan interest on aged units More from Bot Protection For Auto Marketplaces.
Frequently asked questions
Why would a bot place a car deposit it never completes?
A refundable deposit is a free option. Scripts can hold many slots at no risk, keep the one that gains value or finds a buyer, and let the rest refund. The holds still block real customers.
How many reservations should one buyer be allowed?
For a scarce allocation, one per verified household, payment instrument, and address is a defensible rule. Publish it before the release opens so it does not look invented afterwards.
What confirmation step stops most fake holds?
A live phone confirmation before the reservation converts to an order, combined with a card hold. Bots and bulk holders rarely survive a staffed callback step.
What should happen when a hold fails confirmation?
Offer the slot to the next verified waitlist name for a short stated window, then move on. A controlled waitlist keeps the order fair and documented.