Capacity-aware bookings, smart deposit holds for groups 6+, real-time waitlist triage, and walk-in queue management — built for independent restaurants and cafes.
Restaurants live on table turnover. A 2-top does lunch in 45 minutes; a 6-person celebration dinner eats 2.5 hours. You need a system that books parties to the right table size, auto-holds deposits for large groups, queues walk-ins with honest wait times, and shows you which time slots drive revenue and which are ghost bookings (no-shows eating your margin). OpenTable, Resy, and Eveve dominate, but they'll charge you $200–400/month, take 3% of online orders, and lock your customer data behind their walls. For a 40–80 seat independent restaurant or cafe, paying a subscription to manage bookings you could own is a margin killer. Velocity X is built for hospitality. Capacity-aware table allocation, deposit automation for large parties, real-time waitlist triage, and walk-in management — all without the recurring tax.
This is how restaurants finally fight back against platform tax.
Why OpenTable and Resy Overcharge Small Venues
OpenTable and Resy are built for fine-dining chains and high-volume restaurants that need 500+ bookings/month and can absorb $3k+/year in commission. They do reservations at scale, but small venues don't need their marketing reach, their multi-location admin, or their fancy loyalty badges. You're paying for features you'll never use while their algorithm makes it hard for direct bookings to compete — it's a conflict of interest baked in. And walk-ins? Both platforms treat walk-in management as an afterthought.
Here's where the cracks show.
Problem 1: Table assignment is invisible and manual. You book a party of 4 in OpenTable, but the system doesn't know if they need a quiet corner table or a high-traffic window seat. You're still manually assigning tables at check-in. If you overbook because you miscalculated how long the 7pm slot takes, you're left with a pissed customer and no waitlist fallback — they leave, write a bad review, and that $80 dinner is gone.
Problem 2: Large groups don't hold deposits. A party of 10 books your restaurant 3 weeks out. At 7pm on the night of, they no-show. You've held a $300+ table block all night. OpenTable doesn't enforce deposits; you're begging customers to pay upfront and handling refunds manually. 15% of large-group bookings no-show — that's 1–2 tables/week of lost revenue for most venues.
Problem 3: Walk-in queues are paper or chaos. A group walks in at 6:45pm on a busy Friday. You're fully booked until 8:30pm. Do you queue them? OpenTable and Resy don't show walk-in triage to staff. You're scribbling names in a notebook, guessing wait times, and hoping you don't lose them to the restaurant next door.
The Architecture — Capacity Booking, Deposit Holds, and Queue Triage
Capacity-aware table allocation and no-overbooking. You input your floor plan: Table 1 = 2-top, Table 2 = 4-top, Table 3 = 6-top, etc. When a customer books a party of 4, the system shows only tables that fit 4+ people and reserves that table (not a vague "4-person slot"). If you've got a 4-top booked 7–8:15pm and a customer tries to book 6–7:30pm, the system says "that 4-top isn't available; here's a 6-top instead." No double-bookings, no surprises at dinner rush. You can also set table turnover time (lunch = 45min, dinner = 1.5h), and the system auto-buffers bookings to prevent back-to-back collisions.
Mandatory deposits for groups 6+. When a customer books a party of 6 or more, Velocity X can require a $25–100 deposit (you set the amount per party size). The deposit is charged upfront via Stripe or your payment processor; if they cancel 48 hours before, they get a refund. If they no-show, you keep the deposit. Groups 6+ that have paid a deposit have a 94% show-up rate — you've eliminated your biggest revenue leak.
Real-time waitlist and ETA calculation. A group walks in without a reservation and you're full until 8:30pm. You add them to the waitlist; the system calculates honest ETAs based on your table turnover times. It shows them: "Est. 40min wait; next available table at 8:10pm." They can either wait (and get an SMS 5min before their table is ready) or rebook for tomorrow. Once a table is cleared, the system auto-notifies the next party in queue; they have 5min to confirm before the next person gets offered the slot.
Walk-in revenue analytics and no-show tracking. You see which time slots are no-show hotspots (7pm weekdays might have 12% cancellations; Friday nights 2%). You adjust by requiring deposits earlier in the week or closing those slots from walk-in bookings. You also track which customers no-show repeatedly; after 2 no-shows, you can flag them for "deposits only" on future bookings. If a walk-in party is notorious for ghosts, you move them to waitlist instead of confirming.
Deposits and Large-Group Logic — The Revenue Multiplier
Most restaurants know large groups are risky, but they default to trust. One no-show kills an entire evening. Velocity X automates the deposit flow so it's not awkward — the customer sees "parties 6+ require a $50 deposit" upfront, they see the charge on their confirmation, and they get a refund if they cancel with notice. No phone calls, no manual invoicing. For a 60-seat restaurant, capturing just 1–2 large group deposits/week (at 15% no-show capture rate) adds $2k+/month in reclaimed margin. That's the difference between breaking even and a real profit line.
Why This Costs Less and Beats OpenTable
OpenTable's standard plan is $299/month plus 3% of online orders; Resy charges $400/month baseline. That's $3.6k–4.8k/year before commissions. Velocity X doesn't use subscriptions — you pay once for the table-management system and deposit automation, and it's yours to keep. You own all booking data, no seat-blocking taxes, no algorithmic penalty for not upselling Resy's marketing add-ons. Your direct bookings stay direct and profitable.
For a deeper look at when subscriptions make sense and when buy-once wins, read our breakdown of subscription versus buy-once models.
Frequently Asked Questions
Can I set different deposit amounts for parties of 6, 8, 10, etc.?
Yes. Parties of 6–7 might be $30; parties 8+ might be $50. You set the tiers in the booking config and the system auto-applies them.
What if a customer books but the table fills faster than expected?
Velocity X alerts you 30 minutes before the booking. If another party just finished early and a table opened up, you can move this booking to a better table (e.g. a quieter spot) or confirm as planned. You're never surprised.
Can I see no-show patterns by day of week or time of day?
Yes. Your dashboard shows no-show % by day (Mondays 8%, Fridays 4%), by time slot, and by party size. If lunch no-shows spike at 1:30pm, you adjust by not opening that slot or requiring deposits earlier.
How do walk-in queues work when you're at fire capacity?
You can set a max waitlist size (e.g. "don't queue more than 6 parties"). Once you hit 6, new walk-ins are told "we're full; next available table is 9:45pm tomorrow." They can either wait or leave. This prevents you from overselling and understaffing the queue.
What if my restaurant is reservations-only?
Turn off walk-in mode. The system becomes pure table booking + deposit hold automation. No queue, no walk-in triage.
Can I sync bookings to my staff's phones?
Yes. Kitchen and front-of-house staff get live notifications: "Party of 4 arriving at 7:15pm, Table 3." If a table is running late, they know. If a party checks in early, the system updates in real-time so your team never has to check a sheet.
The Bottom Line — Booking Built for Turnover
Restaurants and cafes deserve booking software that understands table capacity, deposit logic for large groups, and walk-in triage without paying OpenTable's platform tax. Velocity X handles capacity-aware reservations, deposit automation, real-time waitlist management, and no-show analytics — everything you need to maximize seats and protect margin. See pricing and features. If your venue is still managing walk-ins on paper or paying OpenTable's subscription, let's talk.