These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Cloud Kitchen Management
- Features
- Outlet bookings
Outlet bookings
Keep restaurant and spa reservations linked to a guest stay.
OverviewOutlet bookings×
Cloud Kitchen Management · Outlet bookings
New
Outlet bookings
Kitchen brands
| Booking number | Outlet type | Outlet name | Starts at | Guest count | Reservation | |
|---|---|---|---|---|---|---|
| KB-53669 | Restaurant | Outlet 525 | 07 Oct | 27 | FB-83781 | |
| KB-70437 | Spa | Outlet 183 | 08 Oct | 14 | FB-83288 | |
| KB-14494 | Restaurant | Outlet 817 | 23 Oct | 15 | FB-34699 | |
| KB-65496 | Spa | Outlet 625 | 27 Oct | 24 | FB-31034 | |
| KB-71024 | Restaurant | Outlet 644 | 20 Oct | 1 | FB-56544 |
6 of 6 records
Outlet 525Kitchen brands · KB-53669
RestaurantStarts at07 Oct
Guest count27
ReservationFB-83781
What you can do
See the guest's outlet plans with the stay
A booking records the outlet type, outlet name, starting time, guest count and reservation. Front Desk Agent captures this activity against the selected stay so the property team can find it from the reservation detail. Restaurant and spa are the configured outlet types. The booking record does not itself establish a financial charge; that is tracked as a separate outlet charge tied to the same reservation.
How the work is organized
- Selection. Choose the guest’s existing reservation before adding outlet activity.
- Booking. Record the outlet, time and party size the team is arranging.
- Follow-up. Review linked outlet activity when preparing the stay’s departure account.
What to agree during setup
Agree who can capture a booking, how the team checks the requested outlet and time, and which person reviews the booking evidence. Keep the guest count on the booking distinct from the stay’s guest count; an outlet event may include a different party. Decide how the front desk checks a changed outlet request against the existing booking. A changed request should be investigated against the original booking reference instead of creating an unexplained second booking.
Check the handoff on an actual case
A checked-in guest asks for a restaurant booking for a different party size from the room occupancy. Front Desk Agent selects the stay, records the restaurant name, time and guest count, and confirms that the booking is visible with the reservation. If the guest later uses the outlet and a charge is raised, Finance Officer records that charge separately against the same stay. The reviewer can inspect the booking and the charge without assuming that each booking automatically incurred an amount.
If the guest changes the time, the front desk should identify the original booking and confirm which plan the outlet will honor. A second booking with the same guest and time can confuse the departure review, especially when a separate outlet charge arrives later. Keep the outlet name and reservation link visible during that review. The Finance Officer can then distinguish the guest’s plan from an actual posted amount and ask for source evidence when the two do not agree.
At shift change, Front Desk Agent can use the outlet booking list to identify plans that still need attention. Check the starting time against the guest’s stay and the outlet name against the request. If the guest has more than one stay, select the intended reservation before recording a new booking. Property Manager can compare the booking with the in-house stay while Finance Officer checks any later charge. This keeps the guest’s plan visible without treating a planned visit as money owed.
What your team sees
- Outlet bookings — Restaurant and spa plans with time, party size and linked reservation.
- In-house stays — Checked-in guests whose linked activity may need attention.
Follow the work through
See outlet activity and folio and payment review.
What it keeps track of
Data model- Kitchen brands
- Kitchen brand records for Cloud Kitchen Management.
- Food batches
- Food batch production records for Cloud Kitchen Management.
- Ingredients
- Ingredient master records for Cloud Kitchen Management.
- Kitchen tickets
- Kitchen ticket records for Cloud Kitchen Management.
Who uses it
Permissions- Front Desk Agent
- Captures bookings.
- Property Manager
- Supervises stay activity.
- Finance Officer
- Reviews any subsequent charge, and Operations Reviewer examines linked evidence.
Set up Cloud Kitchen Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.