This release continues the growth of the Evo platform, brings the modernized Activity Logs experience to more external booking channels with new filtering capabilities, and delivers a set of OHIP PMS integration updates covering OPI Token Exchange, deprecated API migration, OTA reservation modifications, and DerbySoft confirmation numbers.

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 require action on your part, so please read the call-to-action notes carefully.

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 platform is in early adopters' hands now, and we're actively refining it based on what they tell us. Whether on CRS alone or also using CRM and/or RMS, early adopters are already experiencing the Evo platform. We're growing this group. If you're interested in learning more or gaining early access, contact your Customer Success Manager.

More of your channels have been switching over to the modernized Activity Logs experience, with that progress continuing throughout October. Each switch gives you faster, clearer visibility into how your availability, rates and inventory move to the channels that keep you competitive, and this month adds new capabilities to the activity logs. As more channels go live for longer, we'll be able to share specific stats on the impact you're seeing.

The following channels have been or are in the process of being migrated so far:

You can now quickly search and filter activity log entries by room type or rate code, reducing the time spent manually reviewing large volumes of log data and making troubleshooting more efficient.

The Activity Logs in the modernized version now include the ability to filter by Room Code and Rate Code. Previously, you could not narrow activity log results by these values, making it difficult to isolate specific room or rate-related events.

Activity log entries now display the CRS Rate Code in the appropriate column, making logs easier to read and reconcile without needing to cross-reference internal system IDs.

Oracle has announced that OPI Cloud APIs are being separated to a dedicated Oracle Payment Interface Cloud Gateway endpoint. Consumers calling the OPI APIs, including the OPI Token Exchange Service and Cloud OPI Tokenization ECommerce, should no longer send them to the OHIP Gateway Endpoint, but to the dedicated OPERA Payment Interface (OPI Cloud) Gateway Endpoint. This is a change for integrations consuming OPI API calls. Once the new OPI Gateway Endpoint is available, OPI API calls should no longer be sent to the OHIP Gateway Endpoint.

The transition to the new OPI Gateway Endpoint is covered by a six-month deprecation period from the time OHIP 26.4.0 is released, during which the existing OHIP Gateway will still allow OPI calls.

A new configurable endpoint field has been added to support the OPI Token Exchange process within the OHIP integration. This provides greater flexibility in how the token exchange endpoint is defined and managed at the property level. If this endpoint is entered in the PMS setup within the CRS, it will be used; if the field is left blank, the existing APIs will continue to be used.

Oracle is deprecating several OHIP API GET-based operations and replacing them with POST-based equivalents. Our integration will be updated accordingly with this October CRS release. Oracle's deadline for adopting the new APIs is now prior to your upgrade to v27.3 , the previous cutoff of November 1, 2026 no longer applies.

Whether this affects you depends on your current version:

If you are not yet on v26.2, you must enable the following setting in the CRS before your upgrade to v26.2, and remove it again before your upgrade to v27.3:

This setting is found on the PMS Setup page in the CRS. If you do not have access, please contact support as soon as possible to avoid any disruption to API communications.

When an OTA, such as Expedia or Booking.com, sent a reservation modification for a guest who was already checked in or checked out in Opera, the integration was returning errors (RSV01159 and RSV01636) and failing to apply the update. This occurred because the system was sending a Reserved status to Opera even when the reservation was already In House or Checked Out, causing Opera to reject the status as invalid. The system was also sending the CRS-mapped guarantee code, which Opera does not allow to be changed once a reservation is in-house.

The fix:

Benefit to you: OTA modification requests, including stay extensions and guest detail updates, for in-house or checked-out reservations will now be processed successfully and applied to Opera, reducing failed modification alerts and improving the guest experience.

For reservations received through the DerbySoft channel and integrated with Opera via OHIP, the system previously sent the DerbySoft booking reference number to Opera's idContext field. This has been updated to send the SubChannel Confirmation Number instead, the more meaningful guest-facing reference number.

Benefit to you: The SubChannel Confirmation Number is more recognisable to guests and reservation teams. This change supports use cases such as displaying the correct reference number on guest folios and simplifies reservation management for bookings made through DerbySoft sub-channels (e.g. Jonview).

For more information on the OHIP integration, please reach out to your Customer Success Manager for the latest playbook for this connection.

Updates are automatically available in the CRS and are scheduled for production deployment in October 2026. No action is required to receive these platform changes; however, please review the call-to-action notes above for the OHIP items that do require action on your part.