RippleMost rate errors are not pricing mistakes. They are somebody updating four places and getting to three.
A rate that exists separately in the PMS, the booking engine and a channel is three rates that agree until they do not — and the night they disagree is the night a room sells for last season’s price. In Ripple the rate plan is one definition. The booking engine prices from it, the desk quotes from it, and there is no fourth copy waiting to go stale.
Distribution
The calendar is the artefact.
Nightly rates and restrictions across room types, laid out over the period you are actually deciding about. Change a week, see the week change.
- Rate plans per room type, priced by night
- Seasonal and date-range pricing across a period you can read at once
- Minimum stay, closed-to-arrival and closed-to-departure restrictions
What one definition buys you.
The rate work that disappears when there is nothing to keep in step.
- Availability is one number
- What is left to sell is derived from the stays that exist, not maintained as a separate count that has to be corrected.
- A restriction means the same thing everywhere
- A two-night minimum set on a weekend applies at the desk and in the booking engine, because both are reading the same restriction.
- What a guest was charged stays true
- The rate that applied is recorded against the stay, so repricing next season does not rewrite what somebody agreed to last month.