← Blog GASTRONOMY

What Oracle Simphony Integration Partner Validation Means

Understand Oracle's integration partner programme, STS Gen2 validation and the steps needed at each venue.

Abstract editorial diagram of Simphony validation integration topic

Development, validation and deployment are distinct

Building an API connector, validating a solution through an Oracle programme and enabling it for a particular customer are different stages. Product validation does not automatically establish a venue's release compatibility, subscriptions or outlet mapping.

Oracle's integration programme

Oracle's Simphony integration programme describes APIs, partner participation, testing, validation and marketplace publication. The programme provides a documented route for independent solution providers to connect to the POS ecosystem.

Each venue still needs to confirm subscriptions, authorised accounts, revenue centres and operational acceptance tests.

What should a restaurant ask an integrator?

Ask which API is used, the validated operations, minimum technical conditions, account scope, support responsibilities and exception handling. Turn a broad 'integrated with Oracle' claim into testable steps.

What international integration guides show

ResDiary's Simphony onboarding guide dated 17 September 2026 sets out concrete prerequisites: Simphony 19.2 or later, STS Gen2 access, outlet and revenue-centre information. It separately tests opening a linked check from a seated booking and matching POS spend with that reservation.

Apicbase's Simphony integration documentation distinguishes the STS 2 add-on, Reporting and Analytics releases and BI API requirements across its connection methods. These guides show that independent providers document real Simphony integrations. Their particular features and commercial terms should not be assumed to apply to Rezervem or to every customer subscription.

What evidence matters for the individual venue?

Partnership and product validation are useful indications that an independent integration has been developed and tested. A venue still needs its own acceptance test: opening the check at the right table, avoiding transactions in the wrong revenue centre, validating the eligible prepayment workflow and training staff for exceptions.

An integration proposal should therefore document the tested operations, required API entitlements, pilot environment and support owner, not merely display a partner logo. Product validation and venue go-live approval are separate decisions.

Rezervem's integration scope

Rezervem is an Oracle partner with an existing STS Gen2 integration for Simphony Cloud and completed validation. Supported workflows include appropriate reservation-linked check operations and configured eligible prepayment flows. Venue-specific enablement is verified during setup.

See the integration page and go-live checklist for operational boundaries.

Official Oracle references

Oracle Simphony integrations · STS Gen2 API · API Accounts.

REZERVEM · ORACLE SIMPHONY CLOUD Manager

Connect the visit to the POS check.

Connect validated Simphony transaction workflows with guest and reservation operations.

Assess your integration readiness.

Review your Simphony Cloud environment, API entitlements and supported Rezervem integration workflows.