Why does maintaining two menus create problems?
To connect an Oracle Simphony menu to QR ordering, map the appropriate Revenue Center (RVC) to a Rezervem QR Order service station and select Simphony as its catalogue source. Supported product names and prices can then be synchronized to the local QR catalogue.
A hotel with room service, pool and beach outlets should not assume all three use one identical catalogue. Menu synchronization and financial check posting are separate decisions.
How do the RVC and the service station match?
The RVC represents a Simphony operating context. Rezervem QR Order uses service stations for room service, pool bars and other outlets. Configure and validate the exact station-to-RVC relationship before synchronizing products.
Check incoming item identities, available prices and category mappings; new items are not automatically orderable until an authorized operator enables them. Missing prices or unavailable products require review.
Catalogue synchronization depends on how your station is configured and can report failures. A successful prior sync does not guarantee that every product remains available on today's menu.
Menu synchronization is not POS check posting
A product displayed in a QR menu does not mean the guest's QR order has been added to an Oracle Simphony check. Rezervem QR Order's catalogue integration does not perform that posting automatically; the separate POS integration covers different check operations.
Before making a commercial promise, test catalogue source, staff order routing, kitchen output, payment capture and Oracle check records individually, using a known test item and amount.
How Rezervem QR Order uses a configured catalogue
Rezervem QR Order supports a hotel QR ordering flow in which guests choose products in their browser and staff manage orders in a separate mobile app. With a compatible Simphony integration, the station catalogue may receive mapped menu items.
Start with one RVC and station, inspect product and price differences, then place a controlled test order that stays separate from the external check-posting test.
For reservation and Oracle-check scenarios, refer to the Simphony integration acceptance checklist. Validate your actual vendor contract and enabled API scope before rollout.
