The guest arrives. Two separate records should not become two separate stories.
On a busy evening, the host seats a reservation while the service team opens a POS check. When these records are managed separately, linking spend to the right guest becomes a manual task. The goal of the integration is not to replace the POS. It is to connect the reservation and the resulting check.
Rezervem Manager manages reservations and tables; Oracle Simphony Cloud remains the point-of-sale system. The verified integration connects them through supported STSG2 workflows.
What happens after check-in?
With the integration enabled, Rezervem checks the mapping between the reserved table and the Simphony revenue center. When the required references are available, seating the guest can trigger a linked Simphony check. A check-in without a suitable table or revenue-center mapping must not be assumed to open one.
Walk-ins follow the corresponding reservation and table-assignment workflow. Setup should confirm the same guest visit is not linked to a second check through duplicate events.
When does spend return to the guest record?
After service, the check is closed in Simphony. The integration verifies its closing status and can associate supported payment totals, ordered items and tender details with the matching Rezervem reservation. This enables the team to review visits with confirmed spending context.
Confirmed closing details are different from the current status of an open check. Avoid assuming that every open-check item is continuously synchronized to the guest profile.
What if check-in is reversed?
A mistaken check-in can be reversed. Before voiding the linked Simphony check, the integration assesses whether the check is still empty. A check with actual items or payments is not automatically deleted; the team may need to resolve it in the POS.
This distinction protects operational and financial records. It also gives managers a clearer boundary between an incorrect reservation action and a real POS transaction.
Start with one real service journey
Validate organization and revenue-center access, assign an actual test table, open a reservation-linked check, add items in Simphony and close it. Confirm that the final spend is associated with the correct guest visit. Then test missing mappings and a cancelled or reversed check-in.
For validated capabilities and setup requirements, visit the Oracle Simphony Cloud integration page. Restaurant operations remain in Rezervem Manager.
