What a room rate needs to say that a listing page doesn't.

A number alone answers nothing

£140 a night means something different depending on whether breakfast is included, how many guests it covers, and what happens if the trip gets cancelled two days before arrival. A listing page can show the number without ever answering any of that, which leaves an agent with a price and nothing to check it against.

A boutique hotel lists a room at £140 a night. An AI agent checking that rate for a couple's weekend away needs more than the number to recommend it with confidence, it needs to know exactly what £140 buys.

£140 a night could include breakfast for two or nothing at all. It could be the rate for the room regardless of occupancy, or a rate for one guest with a supplement for a second. An agent comparing this hotel against another charging £160 with breakfast included has no way to make a fair comparison from the bare numbers alone, the cheaper rate might genuinely be the worse deal.

What a rate needs to state, specifically

What's included, breakfast, parking, are the obvious ones. Occupancy, whether the rate covers one guest or two, and what a third or fourth guest costs, matters just as much and gets left out more often. Cancellation terms, whether the rate is refundable, and up to how many days before arrival, decide whether an agent can recommend the rate at all for a trip that isn't fully confirmed yet.

The same room's rate can also show differently across the hotel's own site and a third-party listing, if one updates faster than the other, and neither number tells an agent which is current. A hotel quoting £140 directly while a marketplace listing still shows last month's £155 isn't lying on either page, it's just running two versions of the same fact at two different speeds, and an agent checking the wrong one recommends a price the hotel may no longer honour.

Why a generic listing page usually doesn't say enough

A listing built for a person browsing relies on that person reading the small print, or calling to check, or simply assuming standard terms apply. An agent checking the rate on a guest's behalf has no small print to read and no assumption to fall back on safely, it either finds the specific terms stated against the rate itself, or it has an unusable number. This site's own piece on what a booking request needs makes the same case from the customer's side; here it's the business's own published rate that's missing its conditions, not the request.

What this looks like done properly

Selfe attaches one rate's inclusions, occupancy and cancellation terms and reads them the same way on every channel, so an AI agent never compares a live number against a stale one.

A rate stated as "£140 per night, two guests, breakfast included, free cancellation up to 48 hours before arrival" answers every question an agent needs to compare it fairly against another hotel's rate. The same £140 stated with none of that attached is a number an agent can display but can't recommend with any confidence.

Does every rate need all of this spelled out individually?

The core four, inclusions, occupancy, cancellation terms, and who the rate covers, cover most of what changes an agent's recommendation.

What if cancellation terms vary depending on how far ahead someone books?

State the specific terms for each rate type, an advance-purchase rate and a flexible rate are genuinely different offers and should be stated as such.