Property Management System (PMS)
In hotel revenue management, a property management system (PMS) is the software that holds the record of your business: reservations, room assignments, rates, guest profiles, folios and the nightly audit.
Everything else you buy reads from it or writes to it, which makes it the least interesting system in the building and the one whose data quality decides whether any of the others work.
See how ampliphi fits your existing systems
Get a free revenue audit · Book a demo
What is a property management system?
Your system of record, and the place your staff actually work.
The core functions are reservations, the room chart and assignment, rates and availability, guest profiles, folios and billing, the night audit, housekeeping status, and reporting. Beyond that the feature sets diverge enormously, and modern products often bundle a booking engine, a payment integration or a channel connection alongside.
It is worth being precise about what it is not, because the three-system confusion costs properties real money. A PMS is not a pricing system: it stores the rate you gave it and has no view on whether that rate is right. It is not a distribution system: it does not decide what appears on an OTA. A revenue management system does the first and a channel manager does the second.
Vendors bundle these in various combinations, so the question when evaluating anything is not what the product is called but which of the three jobs you are buying and which you still need to solve.
The other characteristic worth knowing is that the PMS is the system you change least often. Migrating one means moving reservation history, retraining staff and rebuilding every integration, so the choice tends to outlive several rounds of everything else. That makes its integration coverage a constraint on what you can buy later.
Resources: Channel manager · Revenue management system · Integrations
How a property management system works in practice
The operational side is familiar to anyone who has worked a front desk. The part that gets neglected is that the PMS is also your data source.
Worked example. A 46-room inn pulls a distribution report and reads direct bookings at 31 percent, which feels healthy. An audit of the source codes finds one OTA arriving under three separate codes, phone reservations logged as walk-in by one member of staff and as direct by another, and a legacy code nobody recognises carrying 4 percent of the year. Cleaned up, real direct share is 22 percent. Every decision built on the original figure, including a conclusion that the direct channel was fine and needed no attention, was built on a nine-point error.
Nothing in that example is unusual. Source-code drift is close to universal at properties where several people take bookings and nobody owns the configuration.
It matters because every forward-looking number you use is derived from PMS data. On the books is a PMS export. Booking pace is that export compared with itself over time. Cancellation rates, booking windows and channel mix all come from the same place. An RMS reading a PMS with inconsistent codes will produce confident suggestions built on a distorted picture.
The related discipline is how provisional and group-held rooms are treated. A block held for a wedding that may not happen is not the same as fifteen confirmed rooms, and different reports within the same system sometimes apply different conventions by default.
Resources: On the books · Distribution mix
Why a property management system matters for independent hotels
Because it is the one system you cannot work around, and the one that sets the boundaries of everything else.
A small property can price on a spreadsheet, update two channels by hand and market with an email list. It cannot run without a record of who is arriving, which room they are in and what they owe. That makes the PMS the foundational purchase rather than an optional layer.
It is also the integration gatekeeper. When you evaluate a revenue management system, a channel manager or a booking engine, the first question is whether it connects to your specific PMS, by name and version. A product that does not is not a candidate however good it is, and properties on older or regional systems find their options materially narrower than the market appears to offer.
The third reason is the least discussed. Your PMS data is an asset that compounds. Two years of clean reservation history with booking dates attached is what makes pace, forecasting and any pricing automation possible at all, and a property that has kept it tidy is in a genuinely better position than one that has not.
Resources: Revenue management for independent hotels
How to manage your property management system at your property
- Audit your source codes once a year. Consolidate duplicates, kill legacy codes, and write down what each one means.
- Agree how phone and walk-in bookings are logged, and make sure everyone taking reservations does it the same way.
- Decide how provisional and group-held rooms are counted, and check that your reports apply it consistently.
- Export on the books by date weekly and keep it. Today's snapshot is the pace history you cannot reconstruct later.
- Check integration coverage before buying anything else. Your PMS decides what is available to you.
- Keep your reservation history when you migrate. It is the input every forward-looking tool depends on.
What a property management system will not tell you
It has no opinion on your rate. It records $118 on a sold-out Saturday exactly as faithfully as $218, and no report in it will suggest the first was a mistake.
Its reports describe the past. Occupancy, ADR and revenue for periods that have finished are what a PMS is built to produce, and the forward-looking questions that actually change a decision need that data rearranged by days-out rather than by calendar date.
And it cannot fix its own inputs. Source codes, rate plan naming and booking conventions are configuration choices made by people, and a system will report a nine-point error in your channel mix with complete confidence if that is what it was told.
How ampliphi works with your PMS
Ampliphi runs on top of the PMS you already use. It does not replace it, it does not ask you to migrate, and it does not change how your front desk works.
The relationship is a read and a write. Ampliphi reads your reservation data to assess how each future date is filling, which is what the demand-based rate suggestion is built on, and approved rates go back out through your existing setup. The practical benefit for a small property is that pace history accumulates without anybody maintaining a spreadsheet, which is the step that stops most independents building one at all.
The corollary is the data hygiene point above. A clean PMS makes the suggestion better and a messy one makes it worse, which is why a source-code audit is worth doing regardless of what software you buy. The suggestion covers your base rate and the differential between room types, and you approve every rate before it publishes.
Key takeaways: property management system
- The system of record: reservations, rooms, rates, guests, folios and the night audit.
- Not a pricing system and not a distribution system. Those are an RMS and a channel manager.
- Every forward-looking number you use is derived from PMS data, so its quality sets the ceiling on everything.
- Source-code drift is close to universal and can distort your channel mix by several points.
- Its integration coverage decides what else you are able to buy.
- It is the system you change least often, so that constraint tends to last.
Frequently asked questions about property management systems
What is the difference between a PMS and a channel manager?
The PMS is the record of your business. The channel manager is the distribution layer that sends rates and availability out and writes reservations back.
Your staff work in the PMS. Nobody works in a channel manager day to day, because it runs unattended and you only visit it when something has gone wrong.
Some vendors sell both as one product, which is convenient and blurs the boundary. The useful test is which system is authoritative for a reservation. That one is your PMS, whatever the product is called.
What does a hotel PMS actually do?
It holds reservations and assigns rooms, stores rates and availability, keeps guest profiles, runs folios and billing, performs the night audit, tracks housekeeping status and produces reporting.
Around that core, products differ widely. Some include a booking engine, payment processing, a channel connection or a point of sale. Some are deliberately narrow and expect you to connect specialist tools.
For a small independent the practical question is not the feature count but whether the core works cleanly and what it connects to, since the second decides what you can add later.
Do I need a PMS if I only have 20 rooms?
Almost certainly yes, though the appropriate product is not the one a 200-room hotel buys.
The alternative at 20 rooms is a spreadsheet and a diary, which works until two people take a booking for the same night or somebody needs to find what a guest paid last year. It also produces none of the reservation history that pricing decisions depend on.
What matters at that size is cost, simplicity and integration coverage rather than depth of functionality. A product built for small properties that connects to the channel manager and booking engine you want will serve you better than an enterprise system operated at ten percent of its capability.
What should I check before changing PMS?
Integration coverage, data migration and the real total cost, in that order.
Confirm that every system you currently rely on connects to the new one, by name. Confirm what happens to your reservation history, because losing it costs you the pace and forecasting inputs that took years to accumulate. Then get the total cost including setup, migration, training and any module you actually need.
Migration is disruptive enough that most properties do it once a decade, so the decision is worth more diligence than its subscription price suggests.
Why does my PMS data quality matter for revenue management?
Because every number that informs a pricing decision is derived from it, and a distortion at the source propagates silently into all of them.
Inconsistent source codes misstate your distribution mix. Provisional bookings counted as confirmed flatter your on-the-books. Rate plans named inconsistently across years make historical comparison unreliable. None of these announce themselves, and all of them produce reports that look perfectly normal.
An annual source-code audit and a written convention for how bookings are logged is a few hours of work that improves every downstream decision, whether you are pricing by hand or running software over the top.
Related terms
Channel manager
Software that distributes your rates and availability to selling channels. It reads from the PMS and writes reservations back to it.
Revenue management system
Software that decides what the rate should be. It reads PMS reservation history to assess demand, and its output is only as good as that history.
Distribution mix
The share of room nights from each channel. Measured from PMS source codes, which is why code hygiene decides whether the figure is real.
On the books
The count of rooms reserved for a future date. A PMS export, and the foundation of pace, pickup and forecasting.
Direct booking
A reservation made without an intermediary. Widely under-reported because phone and walk-in bookings are logged inconsistently in the PMS.