Take the booking wherever the guest already is: your site, Google, the phone. Hold the table against one floor plan, and know exactly who is walking in before they do. No diary, no double-booking, no argument at the door.
Reservations is in development, on the same platform that runs Scorto Delivery and Scorto Operations today. Everything below is the mechanism as it is being built.
Seven steps, in the order a real booking meets them. The floor plan, the hold and the deposit rule are one mechanism. This is how it is specified to run.
A guest books through your website widget, Google's Reserve a Table, or the phone. They pick a time, not a system. The floor plan behind it is the same one either way.
A table for four at a normal hour confirms itself against the live plan. A party of fourteen, a VIP note, or a fully booked slot holds instead and reaches a host directly. That decision is the product.
Nothing else can be sat there for that slot. Walk-ins, other channels, and the host stand all read the same floor plan, so no table is promised twice.
Above your party-size or peak-time threshold, a card is held or a deposit taken up front. A no-show is charged automatically, so the table was never held for free.
An automatic message goes out the day of, with a one-tap confirm or cancel. A guest who does not respond is flagged before service starts, rather than discovered as a gap at 8pm.
The guest is seated and the table's status changes everywhere at once: host stand, waitlist, kitchen pacing. The next walk-in sees real capacity, not a guess.
Completed, cancelled, or no-show, the booking closes clean and the deposit rule enforces itself without a call. Covers, revenue, and no-show rate all come from the record the floor plan already keeps.
A booking inside house rules confirms itself against the live plan the moment it arrives. One that needs judgement (an oversized party, a VIP, a slot that is already tight) holds instead and reaches a host before the guest ever sees “pending”. You are never caught by a table you did not know was gone, and a guest is never left waiting on a slot you would have said yes to anyway.
The panel here is that rule meeting two bookings on the same service. SC-R-2214-GB is the one this page has followed since the hero; SC-R-2219-GB is the party of fourteen the floor plan cannot seat on its own.
Standard hour, and the table is free on the live plan.
No single table free. Needs a combine, or a call to reset the guest's time.
Illustrative interface. Depicts the host stand, not a screenshot.
Delivery and Operations are running on this platform today, and Reservations is being built on the same rails: one floor plan, one record, one place the money settles. If you are weighing whether it will fit your room, the fastest way through is a conversation.