PEAQPLUS · THE BLOG peaqplus.com
Blog / Revenue Management Basics

Rack Rate vs BAR: Which Price Actually Drives Your Hotel’s Rates?

5 min read · By the Peaqplus team

Your PMS contains a rack rate, a BAR, and several prices described as base rates. They do not necessarily do the same job. Before changing next year’s rate structure, trace one price through its dependent plans—and identify the rates that are deliberately independent.

You increase the rate for a busy Friday. The flexible room-only price moves. The member price moves too. A breakfast package stays where it was, and the corporate rate does something nobody expected.

Before blaming distribution, ask a smaller question: which price did you change, and which plans are actually linked to it?

The rate called RACK in the PMS may be a reference, a parent rate, or a legacy code. Its name does not tell you its job. The configuration does.

Give the three terms different jobs

A rack rate is the hotel’s published, undiscounted reference rate. It can be used in quotations or price comparisons, but it is not necessarily the rate driving daily selling prices. It is not automatically a legal maximum, either; presentation and pricing rules depend on the applicable market.

BAR, or Best Available Rate, is the hotel’s best generally available unrestricted rate under the relevant conditions. Compare the same room, occupancy, stay date, inclusions, and cancellation terms. A restricted member or prepaid offer can be cheaper without making it the same product as flexible BAR.

A base rate in a PMS configuration is a rate selected as the parent for a dependent price. That is a technical relationship, not a universal commercial category. The parent might be BAR, rack, or another configured plan.

Oracle’s OPERA Cloud documentation describes both base-rate derivation and BAR-based rates. That is a useful distinction: a dependent price follows its configured reference, not whichever rate happens to sound most fundamental. The exact controls depend on your PMS and setup.

The rate management guide covers the wider architecture. Here, the job is narrower: establish what one change will actually affect before making it.

Follow one change through the rate chain

This is an illustrative setup, not a recommended price ladder or a description of every PMS. All prices use the same currency and tax basis for the same room, occupancy, and date. The breakfast supplement covers the same agreed occupancy throughout.

On a narrow screen, scroll the table sideways.

Rate planConfigured ruleBeforeAfter the base change
Flexible room-only baseManually maintained€120€130
Member room-onlyBase less 10%€108€117
Flexible breakfast packageBase plus €18€138€148
Fixed corporate agreementIndependently contracted€110€110
Published rack referenceMaintained separately€200€200

Only the linked plans move in this example. The corporate rate remaining unchanged is not a fault: it is what the fixed agreement requires. The rack rate remaining unchanged tells you that it was not the parent of this price chain.

Now imagine the breakfast plan is still €138 after the update. Do not immediately overwrite it. Check whether it is a standalone rate, has a date-specific override, references a different parent, or is awaiting distribution. A manual correction can hide a broken relationship until the next price change.

Also test the order of operations. A fixed supplement added before a percentage discount produces a different result from the same supplement added afterward. Write down the intended rule instead of relying on an old code name to explain it.

Check the guest-facing product, not just the number

Two equal prices can represent different offers. Two different prices can be correct. Before calling a rate wrong, compare:

  • Room type and occupancy, including extra-person charges.
  • Meals and other inclusions.
  • Cancellation, payment, and minimum-stay conditions.
  • Eligibility: public, member, corporate, or device-specific.
  • Currency, tax presentation, and the date on which the offer is valid.

Then check a real shop on the intended channel. A valid PMS price is not proof that every connected system displays the intended offer. Where possible, use a test environment or an approved low-risk test date; do not alter a busy production night just to experiment.

Finally, check the economics. A member price that follows the parent perfectly can still be a poor decision if the discount exceeds the value it creates. A breakfast supplement can cover a package rule without covering the relevant cost. Net ADR and contribution answer different questions from “did the rate calculate correctly?”

Leave a rate map someone else can use

For each important rate plan, record its owner, parent or independent status, adjustment rule, eligibility, applicable dates, and any override. Keep fixed negotiated agreements visible as intentional exceptions rather than trying to make every plan follow one base.

Test a small set of representative cases: a normal weekday, a peak date, a new-year date, and a date with a known override. Record the expected result and the observed result. If they differ, identify whether the problem sits in the rule, the override, or the distribution path before changing anything else.

This is also an opportunity to find rates that no longer have an owner. Review them before retiring them: a quiet-looking code may still serve an active contract or channel. Do not delete it merely because nobody in the meeting recognizes its name.

The output need not be elaborate. One maintained rate map and a short set of test cases are more useful than a confident claim that everything comes from rack.

Frequently asked questions

Does every hotel derive its selling rates from rack rate?

No. A hotel may use BAR or another plan as the parent, keep some rates independent, or combine several structures. Inspect the configured dependencies. A rate code’s name is not enough to establish them.

Should a fixed corporate rate rise when BAR rises?

Not simply because BAR moved. A fixed agreement and a dynamic discount off BAR are different arrangements. Check the contract, validity dates, availability conditions, and configured rule before treating an unchanged rate as an error.

Should we remove rack rate if it is not our base?

Not automatically. First establish where it is used: quotations, comparisons, reporting, integrations, or active offers. A rate can have a legitimate reference function without controlling the daily price chain.

Where to go from here

Use hotel rate management for the broader structure, corporate rates for negotiated agreements, and member and mobile discounts for the economics of eligibility-based offers.

Before next year’s rates go live, be able to answer one question without guessing: if this price changes, which other prices should change with it?

Free guides

Reading is one thing — knowing your next step is another. Answer one question and we hand you the guide that matches where your hotel is today. Free, delivered by email.

Find your guide →
Signal → Decision → Action → Outcome

See what we write about — applied in the platform.

Most of what we write is informed by what we see in customer deployments. In our 45–60 minute walkthrough, we run Peaqplus on our live demo environment — a simulated property with data that moves day to day.

No PMS access needed. No commitment.

Not ready for a demo? Start smaller —5-min revenue check →ROI in 4 numbers →