← Guides RESTAURANT

STS Gen2 or BI API for Simphony Reporting Data?

Distinguish supported check operations from bulk sales analytics when choosing a Simphony API.

SIMPHONY CLOUD · PRACTICAL GUIDE · Rezervem

Editorial concept illustration about Simphony reporting

Reporting and transaction processing are different

Querying a particular check associated with a reservation is not the same as analysing all menu sales across a month. One is an operational transaction use case; the other is a historical or aggregate reporting requirement.

Oracle's STS Gen2 introduction explicitly excludes pricing analytics, bulk check extraction and general reporting from intended use.

Choose by expected output

Use the relevant STS Gen2 Checks API for supported digital transaction and check operations. For broad transactional and operational analytics, evaluate the Business Intelligence API and the venue's subscription.

Configuration management may call for a separate C&C API assessment.

A guest-visit example

Associating a confirmed closed-check spend amount with a particular reservation differs from building a business-wide dashboard of revenue by product and month. Write down whether the required output is visit-specific, transaction-level, historical or aggregated before choosing an API.

Validate the resulting data

Compare period, outlet, revenue centre, void/refund treatment, time zone and totals against trusted POS reports. An API response alone is not proof of matching financial definitions.

Make the reporting requirement measurable

'We need sales data' does not identify the correct API. Define the time period, outlets, inclusion of tax and service charges, treatment of voids and refunds, refresh interval and the trusted report used for reconciliation. These details prevent a bulk analytics requirement from being forced through a transaction API.

For example, a chain comparing daily revenue across outlets needs a different data design and entitlement assessment from a venue checking the status of one reservation-linked POS check. Evaluate BI/reporting options for the first and supported STS Gen2 transaction workflows for the second.

Rezervem's verified boundary

Rezervem's existing STS Gen2 integration supports validated reservation-to-check and eligible payment workflows. It should not be taken as evidence that a venue holds a separate BI subscription or receives every bulk analytics capability. See the integration overview.