Reservations, a waiting list and seating that opens the table's check
The customer asks: A restaurant's bookings and walk-ins kept by the host, a table never booked twice, a text when a table is ready, and seating that opens the table's order on the till
- Verdict: Ready, with limits (3)
- Door: Open check · area: Customers and loyalty › History and CRM
- Recipe: Front of house: reservations, a waiting list and seating
- Sample: S55 — Front of house (reservations, a waiting list, seating that opens a check)
- Checked: 2026-10-29 · bench
What you build
A reservation and a waiting-list entry as your manifest's own record types, the guest's name, phone, customer and notes limited to a host role your app's own user does not hold. Desk buttons answered by your service: Book holds the table against overlapping bookings, Seat opens the party's check at its table through the till's open-check door (check_open, a key written on the record first so a retry opens one check), Change booking, No-show and Cancel booking release it. Table ready is the retailer's own SMS Notification. A deposit is the till's customer advance, linked from the booking.
Limits
- The guard runs at Book and Seat; the form keeps a booked slot read-only, the list's Edit and the API do not.
- The app opens checks and reads the floor, nothing more: dishes, moves, payment and the close stay at the till.
- Before the app is removed, every check it opened is paid or closed: the uninstall removes its user.
Tell the customer
Your hosts keep the bookings and the waiting list in iVendNext, a table is never booked twice, guests get a text when their table is ready, and one press seats a party with its table open on every till.
What next
- Tell the customer the 3 limits above, and write them into the proposal.
- Follow the recipe: Front of house: reservations, a waiting list and seating.
- Copy the sample: S55 — Front of house (reservations, a waiting list, seating that opens a check), and change it.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
- Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.
Send every write twice with the same key: it is written once. Send that key again with other lines: it is refused.
Related needs
- Our reservations app seats a table and opens its order; guests order from a QR menu or a kiosk onto that order, and the till takes the payment — Ready, with limits (7)
- A customer's shopping history or trend on the till: recent visits, the store, who served and the discount on each — Ready, with limits (5)
- Find what a customer bought before by typing their phone number — Ready, with limits (3)
- Our CRM sees our customers and their sales — Ready, with limits (2)
Start a project shortlist with this need · Put it in your blueprint · Every need