These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Revenue Management System
- Features
- Rate plans
Rate plans
Keep seasonal price periods and stay rules clear.
OverviewRate Plan Calendar×
Revenue Management System · Rate plans
New
Rate Plan Calendar
Rate plans
| Id | Unit type | Starts at | Ends at | Nightly rate | Minimum nights | |
|---|---|---|---|---|---|---|
| IDD-966 | UT-720 | 14 Oct | 16 Oct | 480 | 20 | |
| IDD-417 | UT-917 | 13 Oct | 16 Oct | 510 | 20 | |
| IDD-490 | UT-321 | 12 Oct | 14 Oct | 680 | 290 | |
| IDD-299 | UT-561 | 11 Oct | 14 Oct | 840 | 870 | |
| IDD-516 | UT-826 | 10 Oct | 16 Oct | 930 | 340 |
6 of 6 records
IDD-966Rate plans · RP-62198
Unit typeUT-720
Starts at14 Oct
Ends at16 Oct
Nightly rate480
Minimum nights20
What you can do
Define the nightly basis
Rate plans records unit type, effective start and end dates, nightly rate and minimum nights. Revenue Manager uses it to define a seasonal basis for booking conversations. Front Desk Agent can read that basis beside the reservation’s own nightly rate. A later edit to a plan should prompt a deliberate decision about future requests; it must not silently change the rate already recorded on a stay.
How the work is organized
- Periods. Rate Plan Calendar exposes effective dates for each unit type.
- Terms. Minimum nights belongs with the nightly rate so the booking conversation includes the stay rule.
- Comparison. Rate recommendations preserve current and proposed amounts for a particular stay date.
A spring plan that ends on a Sunday and a summer plan that starts Monday is easy to understand. Overlapping periods for the same unit type need a property decision before staff rely on the price. Use the actual arrival and departure interval when assessing a minimum stay. Keep unit type spelling consistent with Units and demand snapshots, since these records use text to identify a type.
What to agree during setup
Choose who may change seasonal terms and who checks them when taking a reservation. Agree how the property handles two plan periods that cover the same unit type and date. Keep unit type spelling consistent across plans, units and observations. Decide how the front desk chooses a recorded nightly rate when a stay crosses plan periods. A plan edit should be reviewed against future requests while existing reservations retain their recorded rate.
Check the handoff on an actual case
Set a plan ending Sunday and another beginning Monday for the same unit type. Front Desk Agent takes a stay crossing that boundary and asks Revenue Manager which nightly amount and minimum-night term to apply. Record the agreed amount on the reservation and preserve it after a later plan edit. Add an overlapping plan period and have Revenue Manager resolve the ambiguity before the next request. Compare the final plan dates with the reservation; they answer different questions.
What your team sees
- Rate Plan Calendar — Shows effective price periods and minimum stays.
- Recommendations Awaiting Review — Shows proposals that may change the working rate.
- Published Rates — Shows rate decisions released for a stay date.
Follow the work through
Walk the linked records in the rate review process. Use implementation to agree the first operating cycle and the data model to check the imported references.
What it keeps track of
Data model- Rate plans
- Seasonal nightly rate plans by unit type with minimum stay rules.
- Units
- Rentable rooms and suites with capacity and housekeeping status.
- Reservations
- Guest stays with arrival, departure, rate and lifecycle status.
- Rate recommendations
- Proposed nightly rate changes for a stay date, with reason and review status.
Who uses it
Permissions- Revenue Manager
- Owns seasonal pricing.
- Front Desk Agent
- Reads plans while confirming stays.
- Property Manager
- Reviews changes affecting the operation.
Set up Revenue Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.