What should be inventoried before a channel contract renewal affects rate parity exception review history?
Record classes, time coverage, system owners, the terms history and the real access deadline. A renewal is the moment terms, tools and mappings change together, so the questions belong in the planning conversation, before notice dates pass.
| Record class | Usual home | Why it may not survive the renewal | Ask the revenue operations head |
|---|---|---|---|
| Rate shopping snapshots | Rate shopping tool | Some tools keep only a rolling window, and a new tool starts empty | How far back can past shops still be pulled? |
| Rate plan and inclusion definitions | Booking engine, channel manager | Plans are edited in place, so old inclusions are overwritten | Were plan changes versioned, or only the current plan kept? |
| Channel mapping history | Channel manager | Remapped from scratch for a new contract or tool | Which room and rate codes mapped to which channel product, by date? |
| Distribution terms by version | Contract repository, email | Only the signed renewal is filed as current | Is every version filed with its effective date and market? |
| Metasearch price accuracy reports | Hotel Center or metasearch account | Report views are rarely saved outside the account | Were mismatch reports exported or annotated at the time? |
| Review notes and correction logs | Spreadsheets, tickets, revenue team email | Owned by people, not by any system | Where does the reason each case was closed live? |
A partner collects answers, not files: no snapshots, rate exports or logins. For the same exercise in an investor setting, the portfolio review handoff checklist uses a similar format.
Why do the terms in force matter as much as the prices?
Because whether a price gap was an exception at all depends on the contract and market on that date. The European Commission's Digital Markets Act factsheet records that Booking.com must allow hotels to offer different prices and conditions on other channels, including their own websites, and that Booking.com removed parity requirements from its EEA terms in July 2024. A gap that was a contract issue for an EEA property in early 2024 may be a pricing choice after July 2024, while the same gap under another agreement or outside the EEA may still need review.
Metasearch adds a separate rule set. Google's hotel price accuracy policy requires the total price on the booking page to match the total Google shows, with taxes and fees disclosed, and Hotel Center's price accuracy report lists mismatches with a reason so partners can investigate. That is a display accuracy question, not a parity clause, and the records should say which rule a case was reviewed under. Without the dated terms, a reviewer later cannot tell a breach from a permitted price difference.
An illustrative inventory sheet
Illustrative only; the company, tools and dates are fictional. A 420-person hotel group with properties in the U.S. and the EU is renewing two online travel agency agreements and replacing its rate shopping tool in the same quarter. The revenue operations head completes the sheet from contracts and the project plan, without opening any records.
| Record class | System | Years held | Owner | Survives the renewal? | Reachable until |
|---|---|---|---|---|---|
| Rate snapshots | Outgoing shopping tool | Rolling window, length unconfirmed | Revenue manager | No, new tool starts empty | Shopping tool contract end |
| Rate plan versions | Booking engine | Current plans only; older edits not logged | Distribution manager | Current plans only | Not applicable |
| Channel mapping | Channel manager | 2019 to now | Distribution manager | Remapped for new products | Remapping date |
| Distribution terms | Contract repository | 2016 to now, by version | Commercial director | Yes, filed by company | Company retention policy |
| Price accuracy reports | Metasearch account | Not exported | Ecommerce lead | Unknown | Unknown until checked |
| Correction log | Shared revenue spreadsheet | 2020 to now | Revenue operations head | Yes, if the sheet is kept | Company retention policy |
Reading the sheet: the gaps are the snapshots and the mapping history, because they tie each past case to the product actually being compared. The question to settle before notice dates is whether the outgoing tool can export past shops with dates, channels and rate codes intact. Contract terms on getting data out are covered in SaaS data export rights, and the data scope worksheet gives the company a format for its own counts.
Which dates set the real access deadline?
Use dates from the company's own documents. Four usually matter: the notice date in each channel agreement, the renewal or new terms start date, the end of the outgoing shopping tool or channel manager contract, and any read-only or export period after it. If none is documented, there is no deadline yet; the next step is for the company to fix one, not for a partner to create urgency.
Do not advise the company to retain or copy records it has no authority or policy basis to keep. Rate snapshots are usually commercial data, but review notes and correction logs can quote guest bookings, and terms with channels can restrict disclosure. Those calls belong to the company's finance leadership, counsel and IT.
Ask the revenue operations head about coverage and rights
The revenue operations head knows coverage; authority sits higher. Distribution agreements often carry confidentiality terms, so counsel decides what could ever be licensed and what must be removed or summarized first, and the contract review workflows page shows how agreement records are usually treated. The person who can authorize a licensing discussion is the CEO, with the CFO or a commercial director often preparing the case.
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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. Unknown until SourceX reviews it: buyer interest, the rights review result and any terms. Partners sign the Channel Partner Agreement before submitting introductions; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. Related hotel workflows are on the hospitality page, including group booking change reconciliation and service recovery approvals, and other sectors on the industries hub.
Go deeper on rate parity exception review
- Rate parity exception review exception examples: a worked case of a package that looked cheaper because its inclusions differed.
- Rate parity exception review records across systems: a map of the codes that join snapshots, rate plans, mappings and terms.
- Who can license rate parity exception review records: a short answer on which executive to introduce and why.
- Rate parity exception review referral brief template: a fill-in brief for writing the company introduction.
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 is renewing its channel contracts and years of parity decisions sit in tools it may leave, register as a partner, check the company against who qualifies, and keep the program terms open when you introduce its CFO.