The Opera Cloud integration is a rich two-way integration, but there are a few things to know before you rely on it. This article lists the current limitations and the operational points worth planning around.

Only a defined set of profile fields can be written back to Opera Cloud: name, date of birth, email, phone, address, gender, nationality, identity documents, and marketing and operational email consent. Other fields are read into Bookboost but not written back. More fields may be added over time.

Consent updates follow Bookboost's consent code mapping. For consent to write back correctly, the property's consent names and codes need to match that mapping.

The integration uses regular polling rather than live webhooks, so there is usually a short delay, typically a few minutes, between something happening in Opera Cloud and it appearing in Bookboost. During very busy periods there can be a slightly longer delay, but events are queued and processed in order, so nothing is lost.

If you use IHG, reservations created through IHG only reach Bookboost when IHG creation events are forwarded into the Opera Cloud business events feed. This forwarding has been known to stop silently, so it is worth checking if IHG reservations stop appearing.

These points apply once the Opera Cloud integration is active. To connect a property, see Setting up the Opera Cloud integration; for what the integration does, see What the Opera Cloud integration does.

Please contact us through the 'Talk to Us' option on the left menu in the platform, or through the Bookboost Support email at support@bookboost.io if you have questions or need additional support.