Umi × IRECKONU
Ireckonu occupies an unusual and useful position in the hotel technology landscape. It is a CRM, a customer data platform and an enterprise middleware layer at the same time, which means the marketing data sitting on top is underpinned by a comprehensive set of APIs rather than the other way round.
In practice that gives hotels and developers one cohesive API to build against, with Ireckonu’s onward connections into the PMS and the rest of the stack doing the unifying underneath. The harder work happens before that: data arriving from multiple sources gets cleansed and merged inside the platform, which is the part most CDPs gloss over and the part that decides whether a single guest view is real or just a diagram. They also run their own identity server, handling logins against an Ireckonu profile and acting as a pass-through for Opera Cloud and other profile sources.
Guest portals and logged-in experiences
Account areas, booking history and self-service built against the Ireckonu profile, so the logged-in guest sees a genuinely unified record rather than whatever one system happens to hold.
Identity and single sign-on
Authentication through the Ireckonu identity server, including pass-through to Opera Cloud and other profile sources, so a guest has one login across the estate.
Cleansed, merged guest records
Profiles arriving from multiple systems deduplicated and resolved into one record before anything is built on top, which is what makes personalisation defensible rather than embarrassing.
Pass-through to the PMS
Reservation and operational data reached through the Ireckonu API rather than a separate direct integration, keeping the architecture simpler and the maintenance lower.
Data flowing into CRM and CDP
Website behaviour, preferences and engagement pushed back into the guest record, so the profile marketing works from reflects the whole relationship rather than just the stay.
One integration layer, many systems
Because Ireckonu already carries the onward connections, we build once against a single cohesive API instead of maintaining a separate integration per vendor.