Reservations
Every booking, from enquiry to check-out.
Overview
The reservations list is the front desk’s main workspace. A reservation starts as a draft, becomes reserved when confirmed, a room is assigned, the guest checks in, and the stay can be extended or moved to another room. The system blocks overlapping bookings for the same room, bookings over a room’s capacity, blacklisted guests and rooms that housekeeping has not released. A deposit taken before a folio exists is held against the reservation and moved onto the folio at check-in.
The filters on the list open Arrivals, Departures and In-house views. Registration cards and reservation confirmations are printed from the reservation.
When to use reservations
- A guest books by phone, email or walk-in.
- You need to change, extend or cancel a stay.
Prerequisites
Step by step
Screenshot for this step has not been captured yet — run npm run docs:flow.
Lifecycle
Check-out closes the folio and creates the Accounting invoice. Night audit marks guests who never arrived as no-shows.
What you see on the screen
- The screen says: “Bookings, arrivals and in-house stays”
- Columns: RESERVATION, GUEST, STAY, ROOM, SOURCE, ESTIMATE, STATUS.
- Actions on the screen: Walk-in, New Reservation, All bookings, Arrivals today, Departures today, In-house.
- Form fields: FIND EXISTING GUEST, GUEST NAME (required), PHONE, EMAIL, ARRIVAL (required), DEPARTURE (required), ROOM TYPE (required), ROOM (required), ADULTS (required), CHILDREN, SOURCE, GROUP / COMPANY, PROMO CODE, RATE PLAN, MEAL PLAN, RATE / NIGHT, DISCOUNT %, DEPOSIT REQUIRED, SPECIAL REQUESTS (SHOWN TO GUEST), INTERNAL NOTES.
Permissions
These permission keys control access (granted to roles in Administration → Roles & Permissions):
- hospitality.reservation.cancel
- hospitality.reservation.checkin
- hospitality.reservation.create
- hospitality.reservation.read
- hospitality.reservation.update