Floors, areas and tables with QR codes and waiter sections — plus a shared-tablet terminal where each waiter signs in to their own tab.
SEE IT IN ACTION
One tablet, several waiters, and every order attributed to the person who actually took it.
OVERVIEW AND BENEFITS
A floor plan that bills
A table hosts the open party, and the party holds the bill. That means joining two tables, moving a party, or splitting one group across two tables never loses a charge.
Tables that join and split
Push two tables together for a party of eight and the bill follows the people, not the furniture.
Sections and assignment
Assign waiters to sections so the right person sees the right tables.
A QR on every table
Guests can browse, order or call a waiter from the code on the table.
WHY IT MATTERS
Shared devices lose accountability
When five waiters share two tablets under one login, nobody owns an order. Per-tab sign-in fixes that without giving everyone a device.
1waiter identity per browser tab
48hsign-in that survives a shift change
0orders attributed to the wrong steward
Illustrative figures — replace with measured results before publishing.
PRODUCT DETAILS
Built for a shared tablet in a busy room
The floor structure, the sign-in layer and the order actions a steward actually needs.
Floors, areas & tables
Model the room, with capacity, status and QR code per table.
Waiter sections
Group tables into sections and assign stewards to them.
PIN sign-in grid
Tap your face, enter a PIN, and the tab is yours until you sign out.
Per-tab sessions
Signing out of one tab leaves the others signed in — sessions are tab-local by design.
Cart conflict safety
Two stewards on one table cannot silently overwrite each other’s cart.
Table transfers
Move a party to another table, with the bill intact.
Deleting a line takes two taps, and never a modal
A dialog in the middle of service makes a waiter look away from the guest, and lands under a thumb. The affordance stays on the line itself.
Select, then remove:the delete control only appears once the line is selected, so one stray tap cannot remove anything.
Anchored to the row:the confirmation is where the mistake would be, not floating in the middle of the screen.
Learned from the floor:both a modal and a native confirm were trialled, and both caused wrong deletions.
COMPARISON
Vestibel vs. an order pad
Capability
Vestibel
Order pad
Standalone POS
Per-waiter identity on a shared tablet
Bill follows the party, not the table
Table join, split and transfer
QR code per table for guests
Concurrent-edit protection on a cart
CUSTOMER STORIES
“
Vestibel gave us one guest record across rooms, restaurant and spa — check-in time is down 40% and we stopped losing restaurant charges entirely.
Dinesh Weerakoon · General Manager, The Banyan House
Placeholder story — no customer-story content exists yet.
A 30-minute walkthrough with your rooms, rates and outlets — no slides.
FAQ
FAQ
Each browser tab holds its own waiter identity, established by POS PIN. Signing out in one tab leaves the others signed in, and every order and audit entry is attributed to the tab’s waiter.
The second one to save is told the cart changed underneath them and reloads, rather than silently overwriting the first steward’s lines.
Yes. Multiple tables attach to one party, so the group has a single bill regardless of how the furniture is arranged.
The lock is checked at the request gate, so a locked waiter cannot fire an order or change a cart until a manager unlocks them — even from a tab that was already open.
