We are currently onboarding a select group of early adopters to the Evo standard platform for CRS prior to the general release later this year. The initial feature set includes single sign-on and alerts surfacing missing content and interface action items, with co-pilot and additional analytics to follow shortly. Thank you to those already participating. Your feedback directly shapes how we improve the CRS for all users.

Evo standard is also coming to our other solutions soon. If you would like to see where things are heading, we are happy to arrange a walkthrough of the platform, outline the early adopter program, and answer your questions.

The enhancements, improvements, and fixes listed below are included in the June 2026 release. These changes are currently in UAT validation and are scheduled for production deployment in June 2026.

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

Two improvements to how guest profiles are identified and managed when sending reservations to Opera Cloud. Profile lookup now uses Membership ID and Membership Type as the primary search criteria, reducing the risk of incorrect matches when a loyalty ID is present. A new enable profile create setting gives operators control over whether the CRS automatically creates a new guest profile when no match is found, preventing unintended profile generation where a CRM or another system manages profile creation. When a profile is matched, only the Profile ID is included in the reservation payload, preventing duplicate contact records in the PMS.

Shiji Group is introducing API rate limits across their Daylight PMS platform from 30 of June 2026. The integration has been updated to automatically pace requests within Shiji’s recommended limits and handle rate-limit responses gracefully, requests are queued and retried automatically with no manual intervention required. Rate limits are enforced per property, so activity at one property does not affect another. No configuration changes are needed; these updates are fully transparent during normal operations.

The OHIP integration now supports retrieving inventory at the hotel (house) level in addition to room type, enabling oversell counts and available room figures to be calculated across the entire property. A new Enable Hotel Level Oversell setting in PMS Setup activates this capability and is disabled by default. Note: enabling this feature increases OHIP message requests, which may impact your PMS interface costs.

A fix for non-member profile lookups that could incorrectly match and update an existing PMS profile on a partial name match. The system now validates exact matches on first name, last name, and email address (case-insensitive) before linking a profile to a reservation. If no exact match is found, the system proceeds without linking a profile, preventing accidental updates to another guest’s record. Membership ID-based lookups are not affected by this change.

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