Systems and records
Hotel rate plan eligibility data: judging a rate beyond its price
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
A booking agent should treat price as the last filter, not the first. Before comparing rates, it confirms the guest qualifies for each rate plan, that the stay dates pass length-of-stay, arrival and advance-purchase restrictions, that the total price includes mandatory charges, that cancellation terms fit the trip, and that no linked reservation, held accessible room or prior approval depends on the current booking.
Value drivers
Hotel rate plan eligibility
Key takeaways
- Eligibility comes before price: qualification, booking window, stay pattern, total price, cancellation terms and inventory state each can rule a rate out.
- Distribution systems show each guest the lowest rate they qualify for, so the cheapest visible number is context dependent.
- Total price, including mandatory charges, is the comparison that matters for short-term lodging under the FTC fee rule.
- Linked rooms, group blocks, packages and held accessible rooms are dependencies an agent must check before changing a rate.
- A useful dataset labels every offered plan as eligible, ineligible with its blocking condition, or needing approval, and verifies the outcome after the stay.
How should a booking agent judge a hotel rate beyond its price?
Judge eligibility first, then terms, then price. A rate the guest cannot legally or contractually book, or one whose cancellation window has already passed, is not a cheaper option; it is a wrong answer that happens to show a smaller number.
Hotel distribution systems already encode most of these conditions. Google's hotel price feeds, for example, let a property restrict a rate to a country, a device type or signed-in users through rate rules, and they carry separate restrictions for arrival dates, length of stay and how far ahead a stay must be bought. An agent that reads only the price field skips all of it.
This guide turns that reasoning into a dataset hotels and travel operators can build from their own reservation records: each case states the guest, the stay, the rate plans on offer, the conditions that apply, and the rate that was actually allowed. The goal is training and evaluation material for agents that rebook, quote or change stays, with the eligibility logic kept visible and checkable.
Which conditions decide whether a guest may book a rate?
Five groups of conditions decide eligibility: who the guest is, when they buy, which nights they stay, what they must pay in total, and what happens if plans change. Each lives in a different place in the record, which is why agents miss them.
The table maps each group to where it is usually recorded and what it blocks. Field names are examples from public documentation; a property management system or central reservation system will use its own names.
| Condition group | Typical record location | Example from public docs | What it blocks |
|---|---|---|---|
| Guest qualification | Rate plan rules, loyalty profile, corporate or group code | Rate rules that require a signed-in user or a user country | Selling a member, corporate or regional rate to a guest who does not hold that status |
| Purchase timing | Rate plan booking window | Minimum and maximum booking offset before arrival | Rebooking into an advance-purchase rate after its window has closed |
| Stay pattern | Availability restrictions by date | Minimum and maximum length of stay, closed to arrival or departure | Shortening or shifting a stay into a pattern the rate does not allow |
| Total price | Rate, taxes and mandatory charges | Mandatory charges that must be included in the total price shown | Comparing nightly rates when one plan adds a required charge at check-in |
| Change and cancellation | Cancellation policy and penalty windows | Refundable deadline in days and local time; tiered penalty windows; non-refundable nights | Treating a non-refundable or partially refundable rate as a free swap |
| Inventory state | Room type availability and master status | A master restriction that leaves nights closed until opened | Quoting a rate on a night that is not actually sellable |
Why is the lowest rate on screen often not the lowest eligible rate?
The lowest number a guest sees is the lowest rate that guest's context unlocks, not the lowest rate the hotel has. Google's conditional rates guide says that when several public or conditional rates exist for the same itinerary, the user is shown the lowest one they are eligible for, so two guests searching the same night can see different prices.
Private rates add another layer. Google describes them as rates for loyalty members or audience lists, using the same rule syntax as conditional rates. An agent acting for a guest without that membership must not carry a member rate into a quote, even if it appears in an internal rate grid.
Total price is the third gap. The FTC's Rule on Unfair or Deceptive Fees, in effect since May 12, 2025, covers short-term lodging and requires the total price, including mandatory charges such as a resort fee charged automatically, to be disclosed clearly and more prominently than other pricing. A cheaper nightly rate with a mandatory charge can be the more expensive option once the total is computed, and the dataset should label cases by total price, not nightly price.
Which fields does the rate plan constraint reasoning dataset need?
Each case in the dataset is one decision: given this reservation state and these rate plans, which plans are eligible, which one should the agent choose, and why. The fields below are the minimum that lets a reviewer replay the decision without access to the live system.
At a glance
Which fields does the rate plan constraint reasoning dataset need
Version this specification (for example v1.0, dated 2026-10-18) and record the version on every case, so a change to a field or label does not silently mix two definitions in one training set.
| Field | Content | Source record | Check before use |
|---|---|---|---|
| case_id and spec_version | Stable identifier and specification version | Assigned at export | Unique; version matches the current spec |
| reservation_state | Confirmation status, stay dates, room type, guest count, linked reservation ids at decision time | PMS or CRS reservation history | Snapshot timestamp precedes the decision |
| guest_qualifiers | Membership tier, corporate or group code, country, booking channel, coded as categories | Profile and booking source | No names, emails or card data; categories only |
| offered_rate_plans | Each plan's code, nightly amounts as relative ranks, mandatory charges flag, inclusions | Rate grid as it stood at the decision time | Plans match the property and dates in the case |
| plan_conditions | Qualification rule, booking window, length of stay, arrival or departure closures, cancellation terms | Rate plan setup and restriction history | Each condition carries its effective date range |
| dependencies | Linked rooms, group block, held accessible room, package components, prior approvals | Reservation links, group and package records | Every linked id resolves to a record in the export |
| eligibility_labels | Per plan: eligible, ineligible with the blocking condition, or needs approval | Derived by rule replay, then reviewed | At least one reviewer check per case type |
| chosen_plan and rationale | The plan the property actually allowed and the deciding condition | Final reservation state and notes | Outcome matches the reservation after the change |
| outcome_verification | Final confirmation, charges posted, any later dispute or reversal | Folio and change log | Read after the stay, not at quote time |
Which linked booking or held room blocks a cheaper rebooking?
A rate change is blocked whenever another record depends on the current booking. The agent must check those links before it looks at price, because a change that is cheap for one reservation can break three others.
Accessible rooms are the clearest case. Under the Department of Justice's ADA Title III rule for places of lodging, a hotel's reservation service must hold an accessible room until all other rooms of that type are rented, and must hold the specific accessible room a guest reserved for that guest. A rebooking that releases that room to save money undoes a protection the guest was owed, so the dataset should mark held accessible rooms as a hard dependency.
- Connecting or adjacent rooms booked together: changing one rate plan may release the room the other guest relies on.
- Group or block reservations: the block's terms usually govern the rate, and moving a guest out of the block can affect the group's commitments.
- Package rates: breakfast, parking or event access bundled into the rate disappear when the plan changes.
- Non-refundable nights: Expedia's Rapid documentation says nights listed as non-refundable are charged regardless, on top of any cancellation penalty, so a swap may cost more than it saves.
- Prior approvals: a manager's earlier exception (a waived penalty, a late checkout) may be tied to the original plan and not carry over.
Which rate wins when an illustrative delayed arrival meets an advance-purchase rate?
This example is illustrative; the property, codes and counts are invented to show the reasoning, not drawn from a real booking. A guest holds two nights on a flexible rate at a city hotel, in a room connected to a colleague's room on the same company code. The guest's flight is delayed, and they ask the agent to drop the first night and move to the cheapest available rate for the remaining night.
The agent finds four plans for the remaining night. The lowest nightly number belongs to an advance-purchase plan that requires booking at least seven days before arrival (illustrative), so it is ineligible. The second lowest is a member rate; the guest has no membership, so it is ineligible. The third is a public rate with a mandatory amenity charge that makes its total higher than the guest's current flexible rate. The fourth is the guest's existing company rate for one night.
Two dependencies then apply. Shortening the stay must not release the connecting room the colleague is using, and the flexible rate's refundable deadline, set in days and local hotel time, has to be checked to see whether the first night can still be canceled without penalty. In this case it can (illustrative), so the correct answer is to cancel the first night inside the window and keep the company rate for the second night, not to switch plans.
In the dataset, this case carries four eligibility labels (two ineligible with their blocking conditions, one eligible but more costly in total, one eligible and chosen), the dependency on the connected room, and the verified outcome from the folio after checkout.
When should the agent keep the more expensive rate?
Sometimes the right answer is the higher price, and the dataset needs those cases or an agent will learn that cheaper always wins. The common pattern is a guest whose plans are uncertain: a flexible rate with a later refundable deadline can be worth more to them than a lower non-refundable rate.
Label these cases with the condition that justified the choice, such as an open travel disruption, a pending group decision or an explicit guest instruction to keep cancellation flexibility. Expedia's documentation describes refundability as more than a yes-or-no flag: penalties can sit in up to three tiered windows and can be a fixed amount, a number of nights or a share of the total. A case that reduces all of that to refundable or not loses the information that justified the choice.
Keep a small share of cases where no change is allowed at all, for example when the stay has already started on a rate that permits no modification. These teach the agent to say no and explain why, which is often the most useful behavior in a disruption.
Which signals mean a rate question needs a revenue manager, not an agent?
Hand the decision to a person when the answer depends on judgment or authority the record does not contain. An agent can replay rules; it cannot decide to waive them.
- The only eligible plan requires an exception to a rate rule, a waived penalty or a rate below a floor the agent cannot see.
- The change touches a group block, a contracted corporate rate or a package whose terms sit in a separate agreement.
- A held accessible room, a medical or legal accommodation, or a complaint is part of the reservation.
- Rate plan conditions in the export disagree with what the confirmation sent to the guest promised.
- The total price cannot be computed because mandatory charges or taxes are missing from the record.
- For dataset builders: narrow the scope to one property type and one change type when conditions vary too much across brands to label consistently, and have a revenue or reservations manager review the eligibility labels before release.
What has to be settled before rate plan eligibility data is licensed?
Reservation histories with rate plan setups, restriction histories and change logs can become valuable evaluation material, but four questions are separate. Having system access does not mean the data may be shared; guest privacy permissions do not settle ownership; the hotel may not own data held under a brand or management agreement; and the contract with the brand or management company may limit licensing. De-identifying guest details does not by itself create a right to license the records.
Hotel operators that license reservation and rate histories through SourceX have it carry out the rights review, the contract, preparation and delivery. Qualification is checked with a short company assessment for which no reservation data is uploaded, and no folio or rate grid leaves the property before the operator has approved the scope and terms and signed.
Frequently asked questions
What is hotel rate plan eligibility data?
It is the record of which rate plans a specific guest could book for specific dates, and why. It combines guest qualifiers, rate plan rules, date restrictions, cancellation terms and linked reservations with the plan that was actually allowed. Without the conditions, a list of prices cannot teach an agent which rate was correct.
Why does the cheapest hotel rate sometimes not apply to my booking?
Many rates carry conditions: membership, booking a set number of days ahead, a minimum stay, a specific country or device, or no refunds. A rate that fails any condition is not available to that booking, whatever its price. Mandatory charges can also make a lower nightly rate cost more in total.
What should a rate plan constraint reasoning dataset include?
At minimum: the reservation state at decision time, coded guest qualifiers, the offered plans with their conditions and effective dates, any linked bookings or held rooms, a per-plan eligibility label with the blocking condition, the plan chosen, and the verified outcome after the stay. Version the specification so labels stay consistent.
Can an AI agent change a non-refundable hotel booking?
It can read the policy, but it usually should not change the rate on its own. Non-refundable nights and tiered penalties can make a change cost more than it saves, and waivers are a person's decision. The agent should explain the terms and route any exception to the property.
Which linked bookings stop a rate change?
Connecting rooms, group or block reservations, packages, held accessible rooms and earlier approvals tied to the original plan. Each should be marked in the record as a dependency so the agent checks it before comparing prices.
Sources
- Google shows a user the lowest rate they are eligible for when several public or conditional rates exist for an itinerary. Source
- Google rate rules restrict rates by user country, device type, signed-in status or a share of users, referenced by a rate rule id. Source
- Google private rates target loyalty members or audience lists and use the same syntax as conditional rates. Source
- Google ARI availability messages carry arrival and departure closures, length-of-stay limits and booking offset restrictions, with the master status closed by default. Source
- Google's Refundable element sets a full-refund deadline in days before check-in and a local hotel cutoff time, with Rates overriding PackageData and Result. Source
- Expedia Rapid cancellation policies use tiered penalty windows and list non-refundable nights that are charged regardless of other penalties. Source
- The FTC's Rule on Unfair or Deceptive Fees covers short-term lodging and requires clear disclosure of a total price that includes mandatory charges. Source
- The FTC's rule on unfair or deceptive fees for live-event tickets and short-term lodging took effect on May 12, 2025. Source
- The ADA Title III rule requires lodging reservation services to hold accessible rooms until other rooms of that type are rented and to hold the specific accessible room reserved. Source
See if your company qualifies
A short company assessment. No data uploads are needed.