What does a hotel group's RFP actually look like when it's the one buying? It looks like a dozen different documents at once, each aimed at a wildly different category of vendor. And increasingly, each one is being rebuilt to look nothing like the version the same team sent out three years ago.
Hospitality procurement has usually been a strange animal. The buyer isn't one person. It's a corporate sourcing lead, a director of operations, an IT architect, and a general manager who all want different things from the same supplier. What's changed is that the paperwork tying them together is being pulled apart by category. A linen contract, a loyalty platform, and a booking engine now travel through very different RFPs, even inside the same group.
Linens, Amenities and the Commodity Categories
The classic hotel RFP still lives here: sheets, towels, toiletries, cleaning chemicals, disposables. On paper it looks like the simplest bid to run. In practice it's where procurement teams have gotten the most sophisticated, because the volumes are large and the margins on each line are thin.
The modern commodity RFP reflects that. It asks for landed cost, not unit price. It builds in fabric-weight tolerances, thread-count verification, and a wash-cycle warranty measured in industrial launderings rather than months. It also asks how the supplier plans to hold price when input costs move, because a 24-month contract that reprices every quarter isn't really a 24-month contract.
Group purchasing organizations sit in the middle of a lot of these bids now, aggregating demand across independent properties so they can negotiate on the same footing as the big flags. That changes the shape of the RFP itself: the questions get more standardized, the evaluation criteria get more transparent, and the winning suppliers are the ones who can answer both quickly and identically across dozens of properties.
The Technology Stack: PMS, Booking Engine and Payments
This is where the RFP process has changed the most. The property management system, the central reservations layer, the booking engine, the channel manager, the payment gateway: each of these used to be a separate multi-year selection with its own committee. Now they're increasingly bid together, because the buyer has learned that the integrations between them are where the money leaks.
A modern tech RFP for a hotel group tends to include:
- Integration inventory. Every system the new platform will touch, with the specific data flowing each direction, and who owns the connector when it breaks.
- Data portability terms. What the group gets back at contract end, in what format, and how quickly, negotiated before signature rather than after.
- Security posture. SOC 2 reports, PCI scope, breach-notification timelines, and evidence the vendor's own subprocessors are held to the same standard.
- Roadmap alignment. Not a slide deck of features, but a written commitment to specific capabilities on specific dates, with credits attached.
Shiji's hotel RFP explainer makes the practical point that AI now sits on the buyer's side of the table too, reading vendor responses, scoring them against the spec, and flagging where a proposal ducked a question. That shifts what a good response looks like: vague marketing prose loses to plain-English answers that map to the requirement line by line.
Loyalty Tech Is Its Own Category Now
Loyalty used to be a module inside the PMS conversation. It has quietly become the largest single technology bid a hotel group runs, because the program has grown into a revenue engine in its own right. Membership across the major brand programs reached 675 million members in 2024, growing more than twice as fast as new hotel supply.
A loyalty RFP looks nothing like a linen bid. It asks about identity resolution across booking channels, real-time points accrual, partner-network settlement, and personalization models that touch guest data. It asks how the platform handles a member who books through an OTA one week and direct the next, and whether the vendor's analytics can tell the group which offers actually moved incremental stays versus which ones discounted a booking that would have happened anyway.
This is a bid where the evaluation team includes marketing and data science, not IT and finance alone.
Where AI Is Changing the RFP Itself
The other shift is happening on both sides of the document. Buyers are using AI to draft requirements, extract vendor answers into comparison grids, and check responses against the original spec. Vendors are using it to find the bids in the first place, qualify which ones are worth chasing, and assemble the response from prior work.
Recent RFP.co coverage on thailand-business-news.com describes the shape of that supplier-side automation, with discovery, qualification, and response built into one workflow. That's roughly the mirror image of what hotel procurement teams are building on the buyer side.
The practical takeaway for a hotel group writing its next RFP: assume the responses will be assembled by a machine and read by one, and write the requirements so a machine on either side can't hide behind them. Ask for specifics, attach weights to every criterion, and name the integrations by system and version.
The categories are drifting apart, but the discipline the good RFPs share is the same across all of them: say exactly what you want, and make the answer easy to check.