Hospitality tenants use POS together with Dining floors and tables, Rooms and housekeeping, and Manage bookings.
Please note:
- Menu items come from Recipes and menu — unpublished recipes never appear on terminals.
- Kitchen, cashier, and manager actions are gated by Roles, permissions, and RBAC; ask an admin if a button is missing.
Open a ticket
- Select a table or walk-in from the floor plan
- Add menu items from Recipes and menu
- Send to kitchen when ready
- Settle payment when the guest is done
POS roles
| Role | Typical actions | Restricted |
|---|---|---|
| Cashier | Open ticket, payment | Void without manager |
| Server | Add items, send kitchen | Price override |
| Kitchen | Mark prepared | Change payments |
| Manager | Voids, discounts, close shift | — |
flowchart LR T[Table / walk-in] --> TK[POS ticket] TK --> ADD[Add menu items] ADD --> KIT[Send to kitchen] KIT --> PAY[Payment] PAY --> CLS[Close ticket] CLS --> FL[Floor status: dirty]
Bookings and rooms
Reservations from Manage bookings and room status from Rooms and housekeeping stay in sync with the same guest profile used across the workspace.
Permissions
Kitchen vs cashier vs manager actions are gated by POS permissions. Ask an admin if a button is missing.