Request a Meeting
TR EN
ORACLE SIMPHONY CLOUD · STSG2

Your guest's reservation. Their Simphony check. Connected.

When a guest is seated, Rezervem can create a linked Simphony check. Once that check closes, supported spend and payment details return to the reservation record. Menu sync and prepayment posting are separately configured capabilities.

Request a Meeting Oracle Partner
Works with your Oracle infrastructure. Rezervem's validated Oracle integration is with Simphony Cloud for supported POS workflows.
Oracle Simphony Cloud→ Oracle Partner Page→
TODAY

A reservation, a check and a guest record can become disconnected.

Finding the right check At peak service, the team must match the table and reservation to the right POS record.
Spend without context A closed check tells the POS what was sold, but not necessarily which guest visited.
Manual reconciliation Prepayments and POS balances need explicit matching rules.
CHECK OPENING

A linked check when the guest is seated.

With an enabled integration and the correct table and revenue-center mapping, a reservation check-in can create a Simphony check. A check-in without a mapped table does not create one until a supported assignment is made.

  • Reservation-linked check
  • Table and revenue-center mapping
  • Supported walk-in flow
QR Order Connect
SPEND AND HISTORY

A closed check becomes useful guest history.

After Simphony confirms that a check has closed, supported payment totals and item details are linked back to the Rezervem reservation. This supports guest and visit analysis without claiming real-time data for every open check.

  • Check closure confirmation
  • Spend and payment details
  • Visit record context
Manager QR Order
MENU SOURCE

Use Simphony as a managed menu source.

For a configured QR Order station, products and prices can be synchronized from its mapped Simphony revenue center. New items are not automatically offered for sale: staff reviews and enables them. QR orders are not automatically posted to a Simphony check by this catalog feature.

  • Station-specific mapping
  • Staff approval before sale
  • Catalog sync ≠ order posting
QR Order
PREPAYMENT

Record eligible prepayments against the check.

When the correct tender type is configured and the open check has sufficient unpaid balance, a Rezervem prepayment may be recorded in Simphony. If posting would close the check incorrectly, the integration holds the operation and alerts the team.

  • Tender configuration required
  • Balance and status checks
  • Exception handling instead of double-charge promises
Pay
RELATED PRODUCTS

Stronger together.

Manager Reservation, table plan and guest operations. Explore → Pay Prepayment, authorization and payment workflows. Explore → QR Order QR ordering, menu and service-station operations. Explore → Gift Eligible gifts and offers linked to guest visits. Explore →
FREQUENTLY ASKED QUESTIONS

Common questions.

No. Simphony remains the POS. Rezervem connects supported reservation, guest, catalog and payment workflows to it.

Only if the integration is enabled and the reservation has the required table and revenue-center mapping. Unsupported or incomplete mappings do not create a check.

No. Synchronizing the Simphony menu with QR Order does not, by itself, post QR orders to the Simphony check. Order-posting scope must be verified separately.

No. Prepayment tender configuration, check status and remaining balance determine when an eligible prepayment can be recorded. Exceptions require staff review.

An active Simphony Cloud environment with STSG2 access, appropriate API permissions and validated revenue center, workstation, employee, menu and tender mappings.

ARTICLES AND GUIDES

Understand each connected workflow.

Practical walkthroughs for reservations, checks, prepayments and setup.

01Reservation to Simphony checkWhat happens after seating and after the check closes.SERVICE → 02Prepayment and remaining balanceWhen a collected amount can be posted to an open check.PAYMENT → 03Simphony Cloud setup checklistValidate access, mappings, checks, catalog and tenders.SETUP → 04Simphony open API ecosystemHow third-party integration and licensing work.OPEN APIs → 05STS Gen2 vs BI and Configuration APIsSeparate transaction, reporting and configuration use cases.API TYPES → 06Version and licensing checklistConfirm subscriptions, releases and account permissions.READINESS → 07Integration information requestA written provider request and email template.VENUE GUIDE → 08Troubleshoot API accessIdentify entitlement, authentication and RVC blockers.TROUBLESHOOTING → 09Reservation-to-POS acceptance testsValidate checks, eligible payments and exceptions.TESTING →

Explore what works with your Simphony environment.

We review the mapping, check lifecycle, prepayment handling and menu source before go-live.

Request a Meeting