Revenue Management Basics for Small Hotel Chains

What Revenue Management Means for a Small Hotel Chain

Hotel revenue management uses demand forecasts, pricing and inventory controls to improve the revenue earned from available room nights. For a group of three to twenty properties, the starting point is a repeatable decision process: understand each hotel’s demand, decide which business to accept, distribute approved offers and review the results.

You can begin with reliable reports and a spreadsheet. A revenue management system (RMS) can add forecasting and price recommendations, but software does not replace clear ownership or sound data. This guide focuses on a working routine for a small portfolio rather than a universal pricing formula.

Start with Consistent Metrics

Use the same stay dates and reporting definitions throughout. For a period longer than one day, count room nights rather than distinct rooms or reservations.

• ADR: room revenue ÷ room nights sold. It measures revenue per sold room night, not per available room.
• Occupancy: room nights sold ÷ room nights available × 100.
• RevPAR: room revenue ÷ room nights available, or ADR × occupancy expressed as a decimal.
• Channel mix: each channel’s share of bookings, room nights or room revenue. Name the denominator; these shares are not interchangeable.
• Cancellations and no-shows: track separately using defined booking cohorts and consistent cutoffs, rather than treating all unoccupied rooms as cancellations.

Illustrative one-night example: 100 available rooms, 75 rooms sold and USD 13,500 in room revenue produce an ADR of USD 180, occupancy of 75% and RevPAR of USD 135. The cross-check is USD 180 × 0.75 = USD 135. These are revenue measures, not profit.

For portfolio reporting, sum room revenue and the relevant room nights before dividing. A simple average of property percentages can distort the result when hotels differ in size. Follow consistent rules for complimentary rooms, out-of-order inventory and revenue recognition; see the CoStar/STR metric definitions.

Build a Baseline for Each Property

Review historical results by stay date, day of week, room type and segment. Combine these with on-the-books reservations, booking lead times, cancellations, local events and group commitments. Pickup is the change in bookings or room nights on the books between two snapshots for the same stay dates; distinguish gross new bookings from net pickup after cancellations.

Compare booking pace at equivalent lead times. A hotel with few bookings far in advance may be normal for its market, while the same position close to arrival may need action. Do not assume weekdays are weak in business districts or that early bookers always pay more.

Start with PMS reports and exports, supplementing them with distribution and accounting data where needed. Public competitor prices are not competitors’ realized ADR or RevPAR; comparable performance benchmarking requires an appropriate data source. Missing reports alone do not justify replacing a working PMS.

Set Decision Rules, Not Automatic Price Jumps

Define who can change rates, which dates require review and what evidence supports an exception. Set property-specific review triggers using forecast demand, remaining inventory, booking pace, lead time, room type and expected cancellations.

• Demand ahead of plan: review whether to raise remaining rates or close selected discounts, considering the demand still expected to arrive.
• Demand behind plan: first check visibility, availability, restrictions and conversion. A blanket discount may lower revenue without creating enough additional demand.
• Groups and longer stays: assess the whole stay, expected pickup, release terms and the contribution of other business that might be displaced.
• Rate floors: consider acquisition costs and incremental servicing costs by offer and channel. A minimum selling price alone does not guarantee overall profitability.

A lower-rate booking only displaces higher-rate business if that alternative demand actually exists. Likewise, closing a rate plan or imposing a minimum stay can protect valuable inventory or block useful demand. Review restrictions across adjacent nights, not only the busiest date.

Compare Distribution Costs, Including Direct Costs

Two bookings at USD 200 can contribute different amounts after acquisition costs. For OTA bookings, include the applicable commission and other contractual fees. For direct bookings, include relevant advertising, metasearch, payment, booking-engine and reservations costs. Direct does not mean cost-free.

Compare realized room revenue after consistently defined distribution costs. Do not deduct discounts again if the realized revenue already reflects them. This contribution is not operating profit: property operating costs still need to be covered. Evaluate channel decisions alongside demand, cancellation behaviour and length of stay, rather than maximizing direct share at any cost.

Distribute Approved Rates and Verify Delivery

Use supported integrations to distribute rates, availability and restrictions and to receive reservation changes. Assign a source of truth for each data field. Configure room and rate-plan mappings deliberately, test them and review them when products or contracts change; mapping is not something to assume will configure itself.

Check acknowledgements, exceptions and the guest-facing offer after significant changes. Synchronization reduces manual work but cannot guarantee zero overbookings or identical public prices. Channel-funded discounts, offer conditions and delivery failures can affect what guests see. Assess rate parity against comparable offers and applicable agreements and law, not as a universal obligation.

Keep a Practical Review Rhythm

• Near-term checks: review pickup, cancellations, delivery exceptions and high-demand dates frequently enough to act. Volatile dates may need daily or more frequent attention.
• Weekly decisions: review each property’s forecast and actions, recording the owner, reason, affected dates and follow-up.
• Monthly evaluation: reconcile realized results and costs, assess forecast errors and refine decision rules.

Compare equivalent seasons, weekdays and event periods. Quarter-over-quarter RevPAR growth alone does not establish that a pricing change worked. Check whether results came from rates, occupancy, room mix, market demand or costs.

Use Technology for the Right Job

A PMS supports property operations and reservation records. A channel manager distributes supported rate and inventory updates. A CRS centralizes reservation and commercial controls across relevant direct and indirect channels; a booking engine is the guest-facing booking interface. An RMS supports revenue decisions with forecasting and pricing capabilities, depending on the product.

These functions may overlap in a combined platform. A small chain does not automatically need a separate purchase for every label. Check supported integrations, data quality and actual workflow gaps before adding or replacing systems.

Where ChannelRUSH Fits

ChannelRUSH supports distribution execution through rate and availability distribution, multi-property controls and integrations with supported external PMS systems. Its channel-manager, CRS and booking-engine capabilities are distinct from revenue-management price recommendations.

ChannelRUSH does not provide a PMS or an RMS and does not recommend room prices. It also does not currently provide rate shopping or continuous monitoring of public OTA prices. Your team or a separately selected RMS determines the revenue strategy; distribution technology helps implement the approved decisions.

Related reading: hotel revenue management and dynamic pricing.