Hospitality workspaces combine guest-facing service with back-of-house operations. EDGE Sword ties bookings and rooms to POS, dining floors, and kitchen flow, while recipes and stock keep menus accurate and shifts align front desk, floor, and kitchen coverage. If you picked Hospitality at signup, a default module pack is already enabled — refine it anytime under Enable and manage modules or start from Choose your industry workspace experience.
Please note:
- Guest charges can span room folios and restaurant tabs — settle POS tickets before checkout so Rooms and housekeeping releases the room cleanly.
- Kitchen, cashier, and housekeeping actions depend on role permissions — review Roles in Settings before go-live.
- FMCG or property-heavy teams may prefer the FMCG or Real Estate workspace guides instead.
Guest journey
From reservation to departure, guest records stay linked across modules:
- Book — Create or confirm a stay in Manage bookings; attach room preferences and party size.
- Check in — Front desk assigns a room; status flows to housekeeping and can open a folio for incidentals.
- Dine and charge — Restaurant orders run through Run the point of sale; table holds use Dining floors and tables.
- Settle and depart — Close folios and POS tickets, then check out so the room returns to available inventory.
flowchart LR Book[Guest booking] --> CheckIn[Check-in and room assign] CheckIn --> POS[POS orders and folio charges] POS --> Settle[Settle folio and tickets] Settle --> Checkout[Checkout and room release]
POS, floors, and kitchen
POS is the service hub for waiters and cashiers. Floor plans mirror your physical layout; kitchen stations receive tickets from the same order stream. Unpublished menu items never appear on terminals — publish through Recipes and menu first.
| Area | Primary users | Key article |
|---|---|---|
| Terminals and tickets | Waiter, cashier | Run the point of sale |
| Table layout and holds | Host, floor manager | Dining floors and tables |
| Menu and kitchen items | Chef, kitchen lead | Recipes and menu |
Rooms and bookings
Bookings centralizes reservations; Rooms tracks occupancy, housekeeping status, and maintenance holds. Checked-in stays can charge restaurant or minibar spend to the same guest profile used at the front desk.
See Manage bookings for reservation lifecycle and Rooms and housekeeping for turnover workflows.
Recipes and stock
Recipes define sellable items, modifiers, and kitchen routing. Ingredient usage ties into inventory so depletion reflects actual service — configure products and levels in Track stock and products. Pair recipe costing with purchase workflows when you also run central kitchen or commissary supply.
Shifts and staffing
Hotels and restaurants rely on rotating coverage. Use Shift scheduling to publish rosters by location or department, then assign Start modules per role so front desk lands on Bookings, floor staff on POS, and kitchen on ticket views.
Roles at a glance
| Role | Typical focus | Modules to enable |
|---|---|---|
| Owner / GM | Full property P&L, module policy | Dashboard, Finance, Settings |
| Front desk | Bookings, check-in/out, folios | Bookings, Rooms, POS (folio) |
| Waiter / cashier | Orders, payments, table service | POS, Dining floors |
| Kitchen | Ticket prep, recipe execution | POS (kitchen), Recipes |
| Housekeeping | Room status, turnovers | Rooms |
| Accountant | Invoices, payments, reporting | Finance, Dashboard |
Related guides
- Choose your industry workspace experience — compare Hospitality with FMCG and Real Estate
- Configure your workspace — turn modules on or off after signup
- Hospitality deep dives: POS, Bookings, Rooms, Dining floors, Recipes