Techbanq

Hospitality · Oracle OPERA

OPERA integration is a licensing question before it is an engineering one

The hard part of connecting Oracle OPERA is not the code that reads a reservation; it is establishing which interface your property is entitled to use, because OPERA Cloud publishes REST endpoints through OHIP while an on-premise estate speaks OXI and FIAS, and each carries its own licence, its own data and its own limits. Settle that first and the rest is mechanical.

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The version decides everything

OPERA Cloud and on-premise OPERA are not the same integration

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

A brief that says "integrate with OPERA" hides the one fact that changes the whole design: which OPERA. OPERA Cloud exposes a REST surface through the Oracle Hospitality Integration Platform, with a subscription and a scope of endpoints your property is provisioned for. On-premise OPERA, still common across established estates, speaks the older interfaces — OXI for exchanging reservations and profiles, FIAS for the connection between the property system and the point of sale or a call-accounting system. A connector written for one does not port to the other, and a proposal that does not name the version is estimating a project it has not seen.

This is why our first deliverable is never code. It is a written statement of the deployment, the interfaces the property is licensed for, and the endpoints or message types each one actually publishes — because in OPERA the constraint is rarely the engineering. It is what Oracle lets that particular contract read and write, and discovering that after the design is set is the most expensive way to learn it.

The interface map

Which OPERA interface you reach for depends on what you are moving

The mistake we most often inherit is one connection trying to carry everything. OPERA separates its surfaces on purpose, and matching each data flow to the interface built for it is what keeps the folio, the profile and the reservation from disagreeing.

Reservations and guest profiles

OHIP reservation and profile APIs on OPERA Cloud; OXI messages on-premise.

What breaks if you use the wrong surface: A profile duplicated on every stay because the match key was read from the booking system rather than OPERA, splitting one guest into a dozen.

The folio and charges

FIAS for posting point-of-sale and call charges to the room; the finance interface for export.

What breaks if you use the wrong surface: Charges posted to a checked-out folio, or a restaurant bill that never reaches the room and is settled twice.

Rate and availability

The channel and availability APIs, usually surfaced to distribution through a channel manager rather than read directly.

What breaks if you use the wrong surface: A booking engine reading rates straight from OPERA and drifting out of parity the moment revenue management changes a plan.

Reacting to a change in OPERA

Business events on OPERA Cloud, so a downstream system is told a reservation changed instead of polling.

What breaks if you use the wrong surface: A CRM that is always minutes behind because it re-reads OPERA on a timer, sending a pre-arrival message to a guest who already cancelled.

OPERA in practice

The OPERA-specific traps that show up after the demo

  1. 01

    The endpoint exists but your subscription does not include it

    OHIP documents a wide API; a given property is provisioned for a subset. Confirming your subscription scope in writing before design prevents a connector built around a call you are not entitled to make.

  2. 02

    Rate codes and room types are configured per property

    Two hotels on the same OPERA tenant will have named their rate codes and room types independently. The mapping table between OPERA and the booking or finance system is the deliverable everyone forgets and every integration needs.

  3. 03

    FIAS is a persistent connection, not a request

    The point-of-sale link expects a session that stays open and reconnects cleanly. Treating it like a REST call produces charges that silently fail to post and surface as a folio dispute at checkout.

Our role

What we own between OPERA and the systems around it

  1. 01

    Establish the deployment and the licence first

    Cloud or on-premise, the interfaces you hold, and the endpoints or messages each publishes — in writing, before a line is designed, because it is the cheapest way to find the ceiling.

  2. 02

    Map the record, then move it once

    Reservations, profiles and folio charges mapped so OPERA stays the authority for each and no downstream system quietly becomes a second copy that has to be reconciled by hand.

  3. 03

    React to events, do not poll for them

    Where the deployment supports business events, downstream systems are told when OPERA changes, so the CRM and finance are current rather than a scheduled read behind.

The Oracle contract, the subscription tier and any formal validation stay with you and Oracle; what we own is that the systems around OPERA read and write the right record through the interface each is entitled to use.

Common questions

What buyers ask

Are you an Oracle partner for OPERA?+

No, and we would not describe ourselves that way. We integrate with OPERA — we build and operate the connections between OPERA and your booking, CRM and finance systems using the interfaces Oracle publishes and your property is licensed for. Certification and any Oracle Validated Integration are Oracle programmes with their own process; where a project needs one, that is a conversation you have with Oracle, and we work within whatever your contract already permits.

We are moving from on-premise OPERA to OPERA Cloud. Does the integration survive?+

The intent survives; the connector is largely rebuilt. On-premise integrations that relied on OXI and FIAS have to move to the OHIP REST surface and business events, which is a different model — request-and-response and subscriptions rather than message exchange and open sessions. We treat the migration as its own project: map every existing connection to its OHIP equivalent, confirm your new subscription covers those endpoints, and cut over one flow at a time so the property never loses the folio or the reservation link mid-move.

Why not just read rates and availability straight from OPERA for our website?+

Because OPERA is authoritative for the reservation and the folio, but distribution rates and parity are managed above it, usually in a channel manager and a revenue system. A website that reads rates directly from OPERA drifts out of parity the moment a rate plan changes upstream, and it also shoulders availability caching that the channel layer already does. The reliable pattern is OPERA for the booking record, the channel and booking layer for what the guest is quoted — which is exactly the boundary the two related integration pages describe.

An integration map that names your OPERA deployment, the interface each connection is entitled to use, and where the current setup is reading or writing the wrong record.

Map your OPERA integration