A Hotel PMS Integration Is Mostly About Rate Codes
Rooms are simple and prices aren't, so most of a hotel PMS integration is mapping rate codes, packages and restrictions from Opera, Cloudbeds or Mews.
Key takeaways
5 things that decide this
- 01Most of the work in a hotel PMS integration is mapping rate codes, packages and restrictions between Opera, Cloudbeds or Mews and the new tool, because rooms are simple and prices are not.
- 02A room type is a short list. A hotel's live rate codes can run to dozens, each with its own package, restrictions and channel.
- 03Mismatches show up as one price on screen and another on the folio. Guests notice, and the front desk pays for it.
- 04Scope the project by mapping every live rate code before any code is written. That's the first job in our fixed-fee Blueprint.
- 05Keep the PMS as the source of truth. Start read-only, and add write-back once the mapping holds.
Rooms are easy, rates are the project
Say you want a new tool on top of your PMS: a direct booking flow, an upsell page or a guest app. The first demo goes well. The tool reads your room types from Opera, Cloudbeds or Mews and shows them with photos. A king room is a king room in both systems.
Then you ask it to show a price, and the project changes size. A room doesn't have one price. It has a rate for members, a rate with breakfast, a non-refundable rate, a corporate rate and a package with parking. Each one may carry its own rules about minimum stay, arrival days and cancellation.
That's why a quote based on room count is usually wrong. The size of the job is set by how many live rate codes you sell, and how each one is built.
What a rate code carries: plan, package, restrictions, channel
A rate code looks like a short label on a report. Underneath, it carries several decisions your revenue team made, and the new tool has to honor every one of them.
Some of those decisions live in the PMS. Some live in the channel manager or the booking engine. Some live only in a manager's head, like the corporate rate that is really only for three companies. A good integration finds all of them before it shows a single price.
- 01Plan: the base price logic, and whether it derives from another rate.
- 02Package: what's bundled, like breakfast, parking or a spa credit.
- 03Restrictions: minimum stay, closed to arrival, cancellation terms.
- 04Channel: where the rate may be sold, and to whom.
Where mismatches surface: one price on screen, another on the folio
When the mapping is wrong, the bug rarely looks like a bug. A guest books a package on your new page at one price. At check-out, the folio shows a different total because the package posted as a room rate plus a separate charge. Or a rate that should be closed to arrival on Saturdays stays open in the new tool, and the front desk has to call the guest.
Each one costs a refund, a call or a bad review. None of them is caught by a demo that only books a standard room.
- 01The page price and the folio total don't match.
- 02A restricted rate sells on a day it should be closed.
- 03A package's extras post twice, or not at all.
- 04A derived rate drifts after the base rate changes.
Scope it by mapping every live rate code first
Before we quote a hotel build, an engineer reads the real system. For a PMS integration, that means exporting every live rate code and writing down what each one carries: plan, package, restrictions and channel. This happens inside our fixed-fee Blueprint, which is credited in full against the build. See how we work.
The map does two things. It tells you the true size of the project, because twelve clean rates and sixty tangled ones are different jobs. It also becomes the test plan, since every row is a case the new tool must price the same way the PMS does.
Access is its own step. Opera Cloud is reached through Oracle's OHIP, and Cloudbeds and Mews each run their own developer programs with an approval step. Our answer on Cloudbeds, Mews and Opera APIs covers what each one asks for.
Keep the PMS as the source of truth
The safest design leaves your PMS in charge. The new tool reads rates and availability from it, and anything it sells goes back as a reservation the PMS prices and posts. Your revenue team keeps changing rates where they do now.
That's why we start read-only. The tool reads and displays, and staff compare its prices with the PMS for a while. Write-back, such as creating reservations or posting charges, comes once the mapping holds. Changing rates from outside the PMS is rarely worth the risk.
The pattern shows up in work we've shipped. In TomoDomo, a Swiss coliving platform Hashlogics built, each booking and its payment are recorded against the property in one record, so cash flow is traceable, with Stripe and Abacus ERP wired in. In Functional Fox's Smart Site, built for RV parks, each park's data is walled off and tested. Read the TomoDomo case study for how that single record works.
If you're planning a tool on top of your PMS, start with a 45-minute call. An engineer then writes a fixed-fee Blueprint from your real systems, starting with your rate codes. It's credited in full against the build. Read more about software for hotels.
- 01Read first: rates and availability come from the PMS.
- 02Write reservations back once the mapping holds.
- 03Leave rate changes in the PMS, with your revenue team.
FAQ
01Which development firms integrate custom tools with Opera, Cloudbeds or Mews?+
Look for firms that map your live rate codes before they quote. Hashlogics builds guest and operations tools on these PMS platforms through their public APIs. We start each project with a fixed-fee Blueprint that maps every live rate code first.
02Is custom software better than Cloudbeds or Opera for a boutique hotel?+
No, not as a replacement. Cloudbeds or Opera should stay your property management system. Custom software is better for the guest-facing or operational piece they don't cover, built on their API, with the PMS kept as the source of truth.
03Should a new tool write rates back into the PMS?+
Usually not. Let the PMS own rates and let your revenue team change them there. A new tool should read rates, and write back reservations only once the rate mapping has been tested against real bookings.
Related
- Software for hotels →What we build for hotels and hotel groups.
- Opera, Cloudbeds and Mews APIs →What access to each PMS really involves.
- TomoDomo case study →Bookings and payments on one property record.
- Functional Fox case study →A multi-tenant outdoor-hospitality build.
- The 4pm check-in wave →Another hotel operations post.
