Quick answer
Manage hotel à la carte restaurants and outlets by keeping room-stay information separate from dining availability. Rezervem Manager handles restaurant bookings by service date, meal, area and party size. Rezervem PMS is in development and must not be presented as an active shared-profile or folio-payment solution. The OPERA connection here is limited to FIAS check-in, check-out and change events, not writing charges to a guest folio.
A moment during service
A family staying at the hotel requests dinner on the terrace, while outside guests seek tables for the same meal. A room entitlement does not automatically reserve a table. The host must make the restaurant capacity decision and check any hotel guest rules separately. Room information should be available only to staff whose duties require it, not copied into every outlet note.
1. Map restaurants and outlets individually
Inventory the à la carte restaurant, lobby bar, special dining areas and any other reservable outlet. Establish each venue’s opening hours, meals, dining areas, party limits and host responsibilities. One hotel stay record does not imply a single shared table inventory across all the hotel’s restaurants.
2. Separate dining capacity from room rights
Verify the restaurant’s actual free tables whether the guest stays at the property or visits from outside. Access entitlement, meal-plan conditions and paid dining policies are different from a specific seating confirmation. Explain the terms before confirming the table, especially for special menus or restricted-capacity services.
3. Manage service changes in the booking record
Have the host team record time, party-size and seating-area changes in the restaurant reservation. A room move or hotel checkout should not be assumed to cancel a dining booking automatically. Establish which accommodation events are communicated to the restaurant, which staff may see them and what manual follow-up is needed.
4. Keep the OPERA FIAS scope precise
The OPERA connection for this workflow concerns FIAS check-in, check-out and change events. It does not establish writing charges to room folios or automatically collecting restaurant bills. Test the real hotel connection and its authorized data fields; the presence of an integration name does not prove every hospitality process is covered.
5. Assign clear roles and integration boundaries
Manager owns the restaurant booking and floor decision; the hotel accommodation system owns the room stay. Guest experience and department requests involve different workflows. Rezervem PMS remains in development, so do not depend on it as a live solution. Limit personal and room information to the tasks staff actually need.
How we do it
We use Rezervem Manager to establish dining capacity and operational responsibilities for hotel outlets. Host teams review confirmed, changed and canceled reservations during service. Any OPERA FIAS relationship is discussed only within the check-in, check-out and change-event scope. We do not promise folio posting, payment transfers or an active Rezervem PMS product.
Important limitations
- A hotel room booking does not automatically create a restaurant table booking or guarantee space.
- FIAS events do not prove folio posting, and a shared PMS–CRM guest profile cannot be assumed at every hotel.
Frequently asked questions
- Does a room entitlement guarantee a table? — No. Restaurant capacity and access conditions are checked independently.
- Can OPERA post dining charges to the folio here? — No. The OPERA connection is limited to FIAS check-in, check-out and change events, with no folio posting.
- Is Rezervem PMS a live product for this workflow? — No. It is in development.
