Revenue Management System (RMS)
In hotel revenue management, a revenue management system (RMS) is software that reads demand signals for your future dates and produces a rate for each one, so that pricing responds to how the property is actually selling rather than to a spreadsheet set once a year.
Most products in the category were built for large branded hotels with a revenue manager to operate them, which is the single most useful thing to know before evaluating one for a 46-room independent.
See how ampliphi prices for independent hotels
Get a free revenue audit · Book a demo
What is a revenue management system?
Software that answers one question repeatedly: what should this room cost on this date.
It does that by reading signals and converting them into a rate. The signals vary by product, but the common ones are how a date is filling against its own history, current occupancy and remaining inventory, your own past performance for that date type, competitor rates, and known events. Different products weight those very differently, and what actually drives the number is the question worth asking hardest during an evaluation.
It is worth separating from the two systems it sits between. A property management system is the record of your business: reservations, rooms, guests, folios. A channel manager distributes rates and availability to the places people buy. An RMS does neither. It decides the number that the channel manager then delivers, using data the PMS holds.
Vendors bundle these in various combinations, which is where most of the confusion in the category comes from. The useful question is not what a product is called but which of the three jobs you are actually buying.
The other distinction that matters is between a recommendation engine and an automation engine. Some systems suggest a rate and wait for a human. Some publish automatically. Many do both, with the choice left to the property, and for an owner-operator that choice is not a detail.
Resources: Booking pace · Demand forecasting · Channel manager
How a revenue management system works in practice
The mechanism is a loop that runs without anyone starting it.
It reads your reservation data continuously, assesses each future date against how that date type has filled before, and adjusts the recommended rate as the picture changes. A Saturday running ahead of its curve gets a higher number while rooms remain to sell. A Tuesday tracking normally gets left alone.
Worked example. A 46-room inn sells about 11,400 room nights a year at a $164 average rate, which is roughly $1.87 million of room revenue. Work out what a modest ADR improvement would be worth before looking at any product: a 4 percent lift on the same volume is about $75,000 a year. That figure is the budget the software has to clear, and it is the right way round to run the comparison. It is an arithmetic exercise on your own numbers, not a result any vendor should be promising you.
Running that calculation first changes the conversation. It tells you what level of subscription is defensible and what improvement would have to be real for the purchase to make sense.
The everyday reality is less dramatic than the category's marketing. An RMS does not find demand that is not there, and it will not rescue a property in a weak market. What it does is stop the two recurring losses that come from pricing by hand: dates that fill early and get sold at a rate set months ago, and dates that fill late and get discounted in the final week when the remaining guests are the least price-sensitive of the year.
It also removes a time cost that independents underestimate. The manual alternative is a weekly export, a comparison against last year at equal days out, and a decision on each outlier. That is a real discipline and the first thing dropped when something breaks.
Resources: Dynamic pricing · RevPAR
Why a revenue management system matters for independent hotels
Because the discipline it automates is one almost no independent sustains by hand.
At a chain, somebody watches booking pace for a living. At an independent it is the owner, between a supplier call and a staffing problem, and the honest position at most properties is that rates were set from last year's rates with a seasonal adjustment and revisited when something went obviously wrong.
That approach leaves money in both directions and neither loss appears on a report. Nothing in an occupancy report says a sold-out Saturday should have been $40 higher, and nothing says a discount published three weeks early was unnecessary. The losses are invisible, continuous and only visible against a counterfactual nobody computes.
The caveat is that the category was not designed for you. Products built for 200-room branded properties assume a revenue manager, a segmentation structure and a data history that a small independent does not have, and they price accordingly. Fit for property size is a real evaluation criterion rather than a soft one, and a product that needs an operator you do not employ is not a cheaper version of a revenue manager, it is an additional job.
Resources: Revenue management for independent hotels
How to evaluate a revenue management system
- Confirm it integrates with your PMS by name. A product that does not connect to your specific system is not a candidate, whatever else it does.
- Ask what actually drives the rate. Demand signals, competitor rates, events. Get the weighting in plain language, not a category name.
- Ask whether you approve rates or whether it publishes. Then ask whether that choice is yours and whether it can be changed later.
- Check whether it prices room types, not just a base rate. The differential between categories is where a lot of independent revenue leaks.
- Separate the base product from the modules. Competitive data and event data are frequently priced separately, and the quoted figure often is not the whole figure.
- Run the arithmetic first. Work out what a few points of ADR is worth on your own volume, then judge the price against that rather than against another vendor's.
What a revenue management system will not do
It will not create demand. Pricing decides how well you monetise the demand that exists, and a property in a weak market with a visibility problem has a marketing problem that no rate engine addresses.
It will not fix your distribution cost. A better ADR sold through a channel taking 20 percent is still sold through a channel taking 20 percent, and an RMS has no view on your channel mix or your commission rates.
And it cannot outperform its inputs. A PMS with inconsistent source codes, provisional bookings counted as confirmed or a year of data distorted by a closure will produce a rate suggestion built on that, quietly and confidently. Data hygiene is a prerequisite rather than an optional improvement.
It also will not replace local knowledge. A road closure, a competitor refurbishing, a wedding at a venue nearby, a school calendar shift: those are facts you hold and the system does not.
How ampliphi works
Ampliphi is a revenue management system for independent hotels, and the specifics matter more than the category label.
The everyday rate suggestion is demand-based, built on booking pace and occupancy. It reads how each future date is filling against how that date has filled before, and the suggestion covers your base rate and the differential between room types, which is the part many products leave to the operator.
Two things are deliberately separate and worth stating clearly, because they are often bundled in this category. Competitive insight is a distinct view, where you choose up to five competitors to watch, and it does not feed the everyday demand-based suggestion. Event data is a separate module again, not part of the base product.
You approve every rate before it publishes. Auto-publish is available once you trust the suggestions and it stays optional. Ampliphi runs on top of the PMS you already use, so the history you have been accumulating stays where it is.
Key takeaways: revenue management system
- Software that reads demand signals for future dates and produces a rate for each one.
- Distinct from a PMS, which is the record of your business, and a channel manager, which distributes the rate.
- What drives the suggestion varies enormously by product, and it is the question to press hardest on.
- Most products in the category were built for large branded properties with a revenue manager to run them.
- Work out what a few points of ADR is worth on your own volume before comparing prices.
- It cannot create demand, fix distribution cost, or improve on bad PMS data.
Frequently asked questions about revenue management systems
What is the difference between an RMS, a PMS and a channel manager?
Three different jobs that are frequently sold together.
A PMS is your system of record. It holds reservations, room assignments, guest profiles and folios, and it is where your staff work day to day. A channel manager is distribution: it pushes rates and availability to your selling channels and writes reservations back. An RMS is pricing: it decides what the rate should be.
A property can run all three from one vendor or from three, and both arrangements are normal. What causes problems is assuming a product covers a job it does not. The most common version is a property that believes its channel manager is handling pricing, in which case nobody is.
Does a small independent hotel need a revenue management system?
It depends on whether the pricing discipline is currently happening, not on your room count.
If nobody is comparing future dates against their own history, rates are set from last year with a seasonal adjustment and revisited when something goes wrong. That leaves money on dates that fill early and on dates discounted late, and at $1.8 million of room revenue a few points of ADR is a meaningful number.
If you already run a weekly pace review and price from it, the question is different. You are buying back time and consistency rather than a capability you lack. Both are legitimate reasons, and a spreadsheet started this week beats software bought next quarter if you are currently doing neither.
How much does a hotel revenue management system cost?
Pricing models vary and many vendors do not publish figures, which makes comparison harder than it should be.
The common structures are a monthly fee per room, a flat monthly fee by property size band, and occasionally a share of incremental revenue. Setup or onboarding fees are frequently separate, and competitive data and event data are often priced as modules on top of a base subscription.
Ask for the total annual cost including setup and every module you would actually use, then compare it against the arithmetic on your own numbers. A quoted monthly figure that excludes the two modules you need is not the price.
Will an RMS change my rates without me approving them?
That depends on the product and usually on a setting you control, and it is worth resolving before you buy rather than after.
Some systems recommend and wait. Some publish automatically. Most offer both, and the sensible path for an owner-operator is to start with approval, watch the suggestions for a season, and move to automatic publishing only once the pattern makes sense.
Ask directly: what is the default, can I change it, and can I change it back. Ampliphi's position is that you approve every rate before it publishes, with auto-publish available and optional once you trust the suggestions.
What data does an RMS need to work properly?
Your own reservation history first, and clean enough to be believed.
The core requirement is booking data by date with booking dates attached, which is what makes booking pace and a booking curve possible. Rates, room types, availability and cancellation history come from the same source. Most systems want at least a year, and two is better, though a property with less can still start.
The quality matters more than the quantity. Inconsistent source codes, provisional bookings counted as confirmed and different reports using different conventions all distort the picture. Optional additions such as competitor rates and event calendars improve context, but nothing improves on a clean reservation history.
Related terms
Booking pace
How a future date is filling against the same date at the same point in a prior period. The main demand signal most systems read, and the one an independent can learn to read by hand.
Demand forecasting
Predicting how a future date will finish. Closely related to what an RMS does and not identical, since a rate suggestion and an occupancy forecast answer different questions.
Channel manager
Software that distributes rates and availability to your selling channels. It delivers the number an RMS decides, which is why the two are so often confused.
Rate shopping
Checking what competitors charge for future dates. Competitive data is a common RMS input and is frequently sold as a separate module.
Comp set
The properties you genuinely compete with for the same guest. It defines what competitive data means for your property, and a badly chosen set makes that input worse than none.