Hotel rate shopping: check coverage, freshness, and source evidence

A rate screenshot is useful only when the team knows what it represents. Before reacting to a competitor’s price, check the stay date, the channel, the type of offer, and when the observation was captured. A member rate and a public flexible rate may tell different stories.

Hotel Central’s Rate Intelligence supports that research for a configured comp set. It does not promise universal live coverage, constant monitoring, or automatic price changes. Confirm supported sources and property enablement before relying on any refresh routine.

Start with a comparable stay

Choose the night you are reviewing. Then check whether the offers describe the same stay, room type, occupancy, and cancellation terms. If one result omits those details, keep that uncertainty in the decision rather than treating the lowest displayed price as the market rate.

For an upcoming Saturday, a manager might find a member offer beside a public rate. That is a reason to inspect the rate class, not a reason to lower the hotel’s price. Taxes and fees can also change the comparison when the available evidence does not show whether they are included.

Check when and where the rate was captured

Rate Intelligence provides source-detail review for available observations. Evidence can be verified, partial, manual, legacy, or unknown. A verified capture supports what was observed at that time; it does not guarantee that the offer is still bookable now.

Manual entries are useful when staff researches a competitor separately. Keep their status clear. A staff-entered price is not an automatically captured booking-page snapshot, and an older observation should not appear to be a current quote.

Treat missing coverage as a limit

A configured comp set is not a promise that every competitor, channel, or stay date can be collected. A source may be unsupported, deferred, or missing a configured booking URL. Those states should prompt a coverage discussion, not an invented rate.

Supported availability checks currently require Hotel Central assistance and a separate, explicitly confirmed request. Review the returned observation and last-check time. A missing rate is not evidence of a sell-out, and an unknown or restricted availability result is not interchangeable with available or sold out.

Confirm collection before depending on it

Automated collection is off by default and needs deliberate property enablement. Pilot scope, supported sources, refresh permissions, and collection limits matter. Buying an add-on or seeing a refresh control is not the same as confirming an always-on market feed.

Before selecting a routine, ask which competitors and dates are supported, which observations are manual, and who will review stale or incomplete evidence. A narrower set with understood limits can be more useful than a broad list that the team assumes is complete.

Keep research separate from the pricing decision

The hotel still decides what to charge. Consult your own occupancy, pickup, commitments, and operating context in the systems where you manage them. Revenue Pulse is a separate performance workspace; this research workflow does not imply a direct PMS feed or a Revenue Pulse alert connection.

Rate Intelligence does not recommend a new price or publish rates to booking channels. A manager may decide to hold the current rate, research further, or make a change in the existing pricing system. None of those outcomes should be represented as automatic.

Decide whether the workflow fits

This is a fit for a team with a curated comp set and a person responsible for reviewing sources and freshness. It is not the right substitute when the requirement is universal live coverage, unattended market monitoring, an RMS recommendation engine, or automatic distribution of rates.

Bring a proposed comp set and a typical stay-date review to the demo. Confirm what is supported, what remains manual, and what must be enabled for your property before making the add-on decision.