The short answer
Override a rate when you have a specific constraint or information the current rules do not handle well, such as an unusual local event, an owner-imposed rate requirement or a rate outside your acceptable range. Record the reason, expiry and system that owns the override; then verify it survives the next sync.
Who this is for: Hosts already running dynamic pricing who want a useful review routine instead of constant calendar tinkering.
What to take away
- Intervene for a named exception, not every normal price movement.
- Put the override in the system that will own it after sync.
- Review outcomes against your own goal without attributing every booking change to one price edit.
What deserves a manual review?
A rate outside a boundary you set, a major local event your rules may not reflect, a new discount, or a minimum stay that prevents a sensible gap booking are concrete reasons to inspect a date. If the owner needs the property, block that date in the availability calendar rather than treating it as a price override. A change in rate alone is not automatically a problem; dynamic tools are designed to change rates.
Compare the proposed rate with the rule you intended, the channel's nightly accommodation rate after discounts and the availability that guests can actually book.
Where should the override be made?
Follow the integration's precedence rules. Hospitable warns that a manual calendar edit can be overwritten by a connected third-party pricing tool at the next sync. Its native Dynamic Pricing, by contrast, describes manual date overrides that take priority. Before changing a rate, identify which workflow you have and where the lasting edit belongs.
Record the date, reason, owner and expected return to normal pricing so a temporary exception does not become a forgotten permanent rule.
Review the full calendar, not just booked nights
Pick a regular review time and look at near-term unbooked dates, gaps, upcoming high-demand periods and dates with manual changes. Compare the guest-facing price with your own acceptable range and note changes to discounts or restrictions. Keep the review small enough that someone will actually do it.
Track booked nights and revenue alongside rates if those measures matter to your goal, but do not claim a price edit caused every later booking change. Seasonality, availability and many other factors may have changed too.
Decide whether to keep, change or pause the rule
For a recurring exception, change the underlying rule if the tool supports it; for a one-off date, use a documented override. If prices repeatedly arrive in the PMS or channel differently than expected, pause automation and investigate the connection before adding more rules.
A useful review ends with an owner and next check date, even when the decision is to leave prices alone.
- Write the exact date and rate you inspected.
- Capture the tool, PMS and guest-facing values.
- Record whether the change is one-time or a rule change.
- Confirm the next sync and the person responsible for rechecking.
Do not turn a small sample into a revenue claim
A few bookings after an override do not establish that the override improved performance. Use your own records to inform future decisions, and compare similar dates and constraints where possible. Vendor feature pages describe available controls; they do not independently prove a revenue outcome for your listing.
If you cannot identify the rule or connection that controls a date, resolve that uncertainty before making broad portfolio changes.
Common questions
Can a manual rate be overwritten?
Yes, on some integration paths. Hospitable specifically warns this can happen when a third-party pricing tool syncs. Check where your own override needs to live.
How often should I review rates?
Use a cadence your team can sustain, and add checks when a major event, new promotion or connection change affects the calendar. There is no universal schedule that guarantees a better result.