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.
- OTA Channel Manager
- Features
- Rates and outlet bookings
Rates and outlet bookings
Prepare dated rates and record restaurant or spa bookings against a stay.
OverviewOutlet bookings×
OTA Channel Manager · Rates and outlet bookings
New
Outlet bookings
Channel mappings
| Booking number | Outlet type | Outlet name | Starts at | Guest count | Reservation | |
|---|---|---|---|---|---|---|
| CM-49193 | Restaurant | Outlet 151 | 15 Oct | 4 | RSR-72845 | |
| CM-66037 | Spa | Outlet 632 | 16 Oct | 11 | RSR-54023 | |
| CM-83396 | Restaurant | Outlet 551 | 08 Oct | 2 | RSR-96084 | |
| CM-71097 | Spa | Outlet 433 | 10 Oct | 39 | RSR-28985 | |
| CM-12459 | Restaurant | Outlet 877 | 22 Oct | 7 | RSR-65864 |
6 of 6 records
Outlet 151Channel mappings · CM-49193
RestaurantStarts at15 Oct
Guest count4
ReservationRSR-72845
What you can do
Rates and outlet bookings in daily work
Rate plans carry a unit type, effective dates, nightly rate and minimum nights. The Property Manager maintains them as the property prepares future stays. The reservation records its own nightly rate, so the team can explain the amount attached to a specific booking even as rate plans change over time.
Restaurant and spa bookings can be recorded against the guest stay. The booking has an outlet type, outlet name, start time and guest count. Link it to the reservation so the desk can see the service in the context of the guest’s visit. Confirm the outlet’s actual appointment or table separately with the staff who run it.
A rate plan describes a unit type over a dated period; it is not itself the accepted price of a stay. The Property Manager should compare the plan with the reservation’s nightly rate when a guest changes dates or unit type. An outlet booking is another linked record. It records the requested service time and party size, while the restaurant or spa team still needs to agree that it can serve the guest at that time.
How the work is organized
- Rate context. The Property Manager checks a plan’s unit type, effective dates, nightly rate and minimum nights.
- Stay price. The reservation retains the nightly rate used for that booking.
- Outlet request. The Front Desk Agent links a restaurant or spa booking to the stay and checks its time and party size.
What to agree during setup
Agree who maintains dated rate plans and how the desk chooses the reservation’s nightly rate. Review a stay that crosses a plan boundary so the team knows which price it will quote. For restaurant and spa bookings, agree who confirms the requested time with the outlet staff and who corrects a booking tied to the wrong stay.
Check the handoff on an actual case
Use a weekend stay with a spa request. Have the Property Manager compare the stay dates with the rate plan’s effective period and minimum nights. The Front Desk Agent records the spa booking against the intended reservation and checks its start time, outlet and guest count with the outlet staff. Change the guest’s stay dates and review the rate and outlet time again before telling the guest the arrangement is settled.
What your team sees
- Outlet bookings — Check restaurant and spa requests by outlet, start time and linked stay.
- Arrival schedule — Review effective rate periods by unit type before quoting a stay.
Follow the work through
Walk through the related operating process with the team, then use the data model to check the records each step changes.
What it keeps track of
Data model- Rate plans
- Dated nightly rate plans by unit type with minimum stay rules.
- Channel mappings
- Restaurant or spa bookings recorded against a reservation with outlet, start time and guest count.
- Reservations
- Stay and resource bookings with arrival, departure, party size and nightly rate.
Who uses it
Permissions- Property Manager
- , Front Desk Agent.
Set up OTA Channel Manager your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.