StayFn gives your team the reservation, rate, restriction and block data from every hotel the moment it changes, and lets you turn your own rules into automated checks and actions. It works next to your RMS, not instead of it.
The RMS, booking engine, channel manager and PMS each update on their own schedule. Decisions wait for the slowest one, and every new tool is another integration project.
Pickup, pace and group reports still start as exports and spreadsheets, a day behind what is happening in OPERA Cloud.
Portfolio policies, group-specific rules and checks across properties end up as manual routines that depend on one person remembering them.
“What did we pick up for next month since this morning, by property?”
New and changed reservations arrive from the OHIP Streaming API as they happen. Your BI tool or dashboard reads pickup per hotel and stay date from a StayFn API instead of yesterday's export.
Data OPERA Cloud reservation events (created and changed), reservation search
“Who closed that rate, when, and at which hotels?”
A scheduled report lists every restriction change across the portfolio, so a decision made at one property never surprises the group the next morning.
Data Restrictions and restriction history (OHIP par)
“When group pickup on a date passes our threshold, close the discounted rate.”
Your rule runs on a schedule or on each reservation change, writes the restriction back to OPERA Cloud and leaves an audit record of what it did and why. The rules your RMS cannot express stop depending on someone remembering them.
Data Block statistics (OHIP blk), restrictions (OHIP par)
“Which blocks are behind on pickup, and which cut-off dates are close?”
A daily view of pickup against allocation and projected block revenue across every hotel. Alerts to email or chat follow with connections (below).
Data Block daily statistics, block revenue and revenue changes (OHIP blk)
“Do all our hotels sell the group rate plans the way we defined them?”
Compare each property's rate plans with the group standard and list the differences, instead of opening each hotel's configuration.
Data Rate plans and schedules (OHIP rtp)
“Can our website and app quote OPERA Cloud availability and recognise returning guests?”
Serve live availability and rates to your own booking flows through one governed API, and recognise returning direct guests for member offers, without each project building its own OPERA Cloud integration.
Data Availability and rate information (OHIP par), guest profiles (OHIP crm)
“Which of this month's arrivals have stayed with us before, at any of our hotels?”
See returning guests and their stay history across every property, measure the repeat share per hotel, and give your direct channels and loyalty offers the guests most likely to book again.
Data Stay history, profile statistics and future reservations (OHIP crm, rsv)
“When a date tightens, raise the floor and protect the last rooms for the right business.”
Compression and congestion dates follow your playbook automatically: hurdle rates, rate schedules and sell limits change when availability crosses the thresholds you set, at every hotel, with a record of each change. For properties without an RMS, or for rules on top of it.
Data Availability (OHIP par), hurdle rates (OHIP par, multi-property), daily rate schedules and yield adjustments (OHIP rtp), sell limits (OHIP inv)
“Can our pre-arrival app offer the upgrades and packages OPERA Cloud says are available?”
Your guest app or website offers room upgrades, packages and add-ons from live OPERA Cloud data and books them on the reservation, so ancillary revenue does not depend on the front desk remembering to ask.
Data Available upsells (OHIP par), upsell and package bookings, inventory items (OHIP rsv)
“A large event was announced for our city: which dates and hotels are affected?”
With connections, a function reads the event calendar or demand feed you subscribe to and applies your high-demand rules to the affected dates before the market moves.
Data Your event or demand data source, availability (OHIP par)
“Are we cheaper on an OTA than on our own site right now?”
With connections, a function compares your OPERA Cloud rates with the rate-shopping service you already use and alerts the team when a channel undercuts your direct rate.
Data Your rate-shopping or channel data, availability (OHIP par)
“Tell me in Teams when a block misses its pickup target.”
Connections let checks send messages to email, Slack, Teams or your own systems, with the same retries and audit as every other call.
Data Any of the checks above
Available now works with today's release. Coming needs connections to external systems, in development (see the product page).
Your developers describe the report or rule in plain language. Claude Code, connected to StayFn, finds the right OPERA Cloud operations, writes the function and checks it compiles, without inventing API calls.
An AI assistant connected to StayFn's MCP endpoint answers questions such as "which checks failed overnight, and why?" from the invocation history, without seeing guest data.
With connections, a function sends pickup, restriction or block figures to the AI model you choose to flag unusual patterns, such as a sudden pace drop at one hotel, and explain them.
An assistant that answers from your OPERA Cloud data and your own documents, such as group contracts, rate agreements and revenue playbooks, with the sources it used: "Which blocks next quarter have attrition clauses, and how is their pickup?" It sees only the hotels each user may see.
StayFn does not set prices. Your revenue management system keeps forecasting and pricing; StayFn gives you the data and the custom rules around it, across every property, through one platform your IT team controls.
See also StayFn for finance teams and the integration use cases.
A 30-minute walkthrough on the OHIP sandbox: a reservation changes, the pickup check runs, and you see every call it made.