This worked case is part of the rate parity exception review guide, which covers the inventory before a channel contract renewal. Here, one flag is followed from the snapshot to the checked result.
The case: a $20.00 undercut that was not one (Illustrative)
A fictional 760-person hotel group runs twelve properties and a central revenue team. Every figure, code and name below is invented; it is not a real company, quote or deal.
- Rate snapshot, Tuesday 06:00. The shopping tool compares a Friday stay at one property: the brand website's rate is $219.00 and an online travel agency shows $199.00. The tool flags a $20.00 undercut.
- Rate plan check. The revenue analyst opens the property system. The $219.00 rate is BB-FLEX, which includes breakfast for two. The brand's room-only RO-FLEX is $199.00.
- Mapping check. In the channel manager, the agency's product is mapped to RO-FLEX. The agency listing says breakfast is not included.
- Terms check. The analyst checks which agreement covers that channel and whether it has any rate condition for this property's market. It does not.
- Decision. The revenue operations head closes the case as "inclusion mismatch, no breach" and asks for the shopping tool's comparison rule to match on meal plan as well as room type.
- Correction. The rule change is logged with a date and an owner.
- Checked result, Wednesday. The next snapshot compares RO-FLEX with the agency's room-only offer: $199.00 against $199.00. Parity holds.
Who decided what, and the record each decision left
| Step | Decision | Who made it | Record left behind | Where it usually lives |
|---|---|---|---|---|
| 1 | Flag a gap | Shopping tool rule | Snapshot: channel, stay date, shop time, price | Rate shopping tool |
| 2 | The two prices differ in inclusions | Revenue analyst | Rate plan definitions on that date | Property system or booking engine |
| 3 | Agency product is room-only | Revenue analyst | Mapping of channel product to rate plan | Channel manager |
| 4 | No rate condition applies | Revenue analyst | Agreement version and market | Contract repository |
| 5 | Close as no breach | Revenue operations head | Case note with reason | Spreadsheet, ticket or email |
| 6 | Change the comparison rule | Revenue operations head | Dated rule change | Shopping tool settings or change log |
| 7 | Confirm parity | Shopping tool | Next snapshot | Rate shopping tool |
Seven steps, at least five places. The reasoning that matters, steps 2 to 5, is held by no single system.
Why this sequence is useful evidence
Because it shows a trained reviewer separating three look-alike situations: a real undercut, a loading or mapping error, and two products that only look comparable. Each needs a different action, and only the joined records show which one occurred. A history of hundreds of such cases, each with its closing reason, is a record of commercial judgment that no shopping report contains.
Dates carry the rules. For an EEA property, the European Commission notes that Booking.com dropped its parity requirements there in July 2024, so a gap logged in spring 2024 and an identical gap logged that autumn can deserve different verdicts. Step 4 only works if the agreement version is filed with the date it took effect. Outside that channel and region, contracts and local law decide, and that is counsel's call, not the analyst's.
Closing codes: the field that makes a case reusable
The single most explanatory field in this whole chain is the reason written at step 5. Teams that close flags with a short, consistent code make their history far easier to read later. A workable set, drawn from the situations this page describes:
| Closing code | What the reviewer found | Typical action |
|---|---|---|
| Real undercut | Same product, lower price on a channel | Contact channel or adjust loading |
| Mapping error | Channel product points to the wrong internal plan | Remap and log the change |
| Inclusion mismatch | Different meal plan, cancellation rule or occupancy | Fix the comparison rule |
| Display accuracy | Metasearch total differs from booking-page total | Correct taxes, fees or feed |
| Permitted difference | Gap allowed under the terms in force | Note the terms version |
The display accuracy row comes from metasearch rather than contracts: Google's hotel price accuracy policy requires the booking-page total to match the total Google showed, including taxes and fees, and Hotel Center's accuracy report gives a reason for each mismatch. A flag closed under that rule should say so, because the remedy is a feed fix, not a conversation with a channel.
Asking a client "do you use closing codes, and since when?" is often the fastest way to learn whether its history is readable.
Recognizing similar cases at a client
Listen for these signals in an ordinary revenue meeting; none requires seeing a record.
- The team talks about "false alarms" from the shopping tool and can say roughly what share they are.
- Someone owns a log, ticket queue or spreadsheet where flags are closed with a reason.
- Meal plans, cancellation rules or occupancy have caused confusion between channels before.
- A room-type cleanup or channel manager change in the last few years required remapping.
- The commercial team can say which agreement applied to which channel in a given year.
The second and fifth signals matter most. The system map for this workflow shows which codes join the records, and the procurement approvals guide applies the same exception test in another function. Freight teams build similar trails in freight audit exceptions. If you advise the hotel group on revenue, the note on whether referring clients hurts the relationship covers how to raise the subject.
The person to introduce is the CEO, with the CFO or a commercial director often preparing the case; the who-can-license page covers that decision. The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. Buyer interest, the rights review result, what must be removed and any offer stay unknown until SourceX reviews the records. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application. More hotel workflows are on the hospitality page.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a hotel group's revenue team closes parity flags with written reasons like this one, register as a partner, check the company on who qualifies and read the program terms before you ask the revenue operations head for an introduction.