This release brings continued momentum for the Evo platform, a scheduled maintenance window for the Voice Application (CRO), and a set of Opera OHIP integration enhancements covering booking source tracking, profile synchronisation, and processing efficiency.

Review the OHIP items relevant to your integration setup. If you manage this area, you can perform the updates yourself. Otherwise, please open a case with support for assistance, or request the full OHIP playbook from your Customer Success Manager. Several items are configurable per property, so whether and how each one applies depends on your business practices.

If you would like to learn more about these topics or any of our solutions, please reach out to your Customer Success Manager.

Evo is the intelligence layer connecting your operation. It surfaces what needs attention before you have to go looking, answers any question about your business in natural language, and puts real hospitality intelligence behind every product you use.

The Evo early adopter initiative for CRS continues to grow, and multi-product customers are now beginning to experience that connected way of working across CRS, CRM and RMS as onboarding continues. This month brought real momentum, with user feedback helping us keep adding value to the platform.

Evo Standard: Live Now

Looking Ahead

The next phase of the platform brings Navigator, Researcher and other pillars into your Evo experience.

If you would like to see where things are heading, we are happy to arrange a walkthrough of the platform, outline the early adopter initiative, and answer questions.

We will be carrying out scheduled maintenance on the Voice Application (CRO). Any agents logged in during the window below will need to log back in:

September 10, 2026, 02:00–07:30 UTC / September 9, 21:00 – September 10, 02:30 CDT

We have added support for sending an Origin Code on bookings made through the CRS. A new configurable field in PMS Interface Setup, similar to the existing ID Context field, lets you define a default Origin Code value that is automatically applied to all reservations posted from the CRS to the PMS, including bookings modified in the CRS.

For example, setting the Origin Code to CRS ensures that every booking originating from the CRS is clearly identified in the PMS, improving reporting accuracy and booking source tracking.

Guest and corporate profiles created or updated in the PMS will now automatically sync to the CRS, even when those profiles are not associated with an active booking, provided the hotel subscribes to Profile business events with OHIP.

Previously, profile data was only transferred when tied to a reservation. With this enhancement, guest profiles created standalone in the PMS (without a booking) and corporate profiles created in the PMS are pushed to and maintained in the CRS automatically, keeping your CRS profile database current and aligned with the PMS at all times.

We have implemented a caching mechanism for Corporate and Travel Agent (TA) profile IDs retrieved from Oracle. When a reservation includes a corporate or TA profile, the system previously performed a live Oracle lookup on every booking to retrieve the required profile ID. The profile ID is now stored after the first successful lookup, so subsequent bookings using the same profile reference the stored value directly.

For example, all reservations from a high-volume channel that share the same corporate profile, such as Booking.com, will now only require a single Oracle lookup, significantly reducing processing overhead and associated costs.

For more information on the OHIP integration, please request the latest playbook from your Customer Success Manager.

Updates are automatically available in the CRS and are scheduled for production deployment in September 2026. No action is required to receive these changes.