This article provides definitions for the terminology used in the Availability, Rate & Reservation Data Exchange tables found in each Channel Connection article.
Overview
Each Channel Connection article in the RMS Help Centre includes an Availability, Rate & Reservation Data Exchange table. This table shows which data is sent and received between the channel and RMS, and whether each feature is supported by the integration.
This glossary defines every term used in those tables, organised by category.
✎ Please Note: RMS is highly configurable. Some Terminology, User Access & Permissions, Images, Labels, and Functions used in these articles may differ from your setup. CLICK HERE to find out more.
Support Status Values
Each feature in the data exchange table has one of the following support status values:
- Supported – The feature is available and functional for this channel connection. Data is exchanged between the channel and RMS for this feature.
- Not Supported – The feature is not available for this channel connection. Data is not exchanged between the channel and RMS for this feature.
- Custom Value – Some features display a specific value instead of Supported/Not Supported. For example, Live Availability may show “365 Days” or “731 Days” to indicate the supported availability window, and Email Confirmation Sent By shows the name of the party responsible for sending the confirmation email.
Availability
The Availability category covers how room inventory and availability data is shared between RMS and the channel.
| Term | Definition |
|---|---|
| Allotments | The number of rooms or sites allocated to a channel for a given date range. RMS sends allotment data to the channel so the channel knows how many units are available to sell. When supported, changes to allotments in RMS are automatically reflected on the channel. |
| Live Availability | The maximum number of days into the future for which RMS will send real-time availability data to the channel. For example, “365 Days” means the channel can display and accept bookings up to 365 days in advance. This value varies by channel. An asterisk (*) indicates a footnote with additional details specific to that channel. |
| Oversell Allotments | The ability to allow a channel to sell more rooms or sites than are physically available. When supported, RMS can send oversell allotment data to the channel, permitting overbooking up to a configured limit. When not supported, the channel can only sell up to the actual available inventory. |
| Release Back Time | The time before a guest’s arrival date at which unsold allotments are automatically released back to the general inventory pool. When supported, RMS communicates release back time settings to the channel so that unsold allocations are returned before the arrival date. |
Rates
The Rates category covers how pricing and rate information is communicated between RMS and the channel.
| Term | Definition |
|---|---|
| Additionals Rates | Extra charges that apply on top of the base rate, such as fees for additional guests, extra bedding, or other supplementary services. When supported, RMS sends these additional rate components to the channel so they are reflected in the total price shown to the guest. An asterisk (*) indicates a footnote with additional details specific to that channel. |
| Currency | The currency code (e.g. AUD, USD, EUR) in which rates are sent from RMS to the channel. When supported, the channel receives and displays rates in the currency configured in RMS. |
| Override Amount | A manually specified rate that overrides the standard calculated rate for a particular date or period. When supported, override amounts set in RMS are sent to the channel and take precedence over the default rate calculation. |
| Person Base | The base occupancy level on which the rate is calculated (e.g. the rate is for 2 guests, with additional charges per extra person). When supported, RMS sends person base pricing information to the channel, enabling the channel to display rates that vary by the number of occupants. |
| Rate Amount | The base nightly rate for a room or site. This is the primary rate value sent from RMS to the channel. When supported, changes to rate amounts in RMS are automatically updated on the channel. An asterisk (*) indicates a footnote with additional details specific to that channel. |
| Rate Description | The name or descriptive label of the rate type (e.g. “Standard Rate”, “Weekend Special”). When supported, RMS sends the rate description to the channel so guests can see the name of the rate plan they are booking. |
Restrictions
The Restrictions category covers booking restriction rules that RMS can communicate to the channel to control when and how bookings can be made.
| Term | Definition |
|---|---|
| Closed to Arrival | A restriction that prevents new arrivals on a specific date. When this restriction is applied in RMS and supported by the channel, guests cannot make a booking with an arrival date on the restricted day. Existing reservations are not affected. |
| Closed to Departure | A restriction that prevents departures on a specific date. When this restriction is applied in RMS and supported by the channel, guests cannot make a booking with a departure date on the restricted day. This is commonly used to enforce minimum stays over peak periods. |
| Maximum Nights | The maximum length of stay allowed for a booking. When supported, RMS sends the maximum nights restriction to the channel, preventing guests from booking stays longer than the configured limit. An asterisk (*) indicates a footnote with additional details specific to that channel. |
| Minimum Nights (MLOS) | Minimum Length of Stay. The minimum number of nights a guest must book. When supported, RMS sends the MLOS restriction to the channel, preventing bookings shorter than the configured minimum. This is the standard minimum stay restriction. An asterisk (*) indicates a footnote with additional details specific to that channel. |
| Minimum Nights (Soft Close) | A conditional minimum stay restriction that applies only when availability falls below a configured threshold. Unlike the standard MLOS which always applies, a Soft Close minimum stay activates dynamically — for example, requiring a 3-night minimum only when fewer than 5 rooms remain. When supported, RMS sends this soft close rule to the channel. An asterisk (*) indicates a footnote with additional details specific to that channel. |
| Stop Sell | A restriction that completely closes a room or site category for sale on a specific date or date range. When Stop Sell is applied in RMS and supported by the channel, the channel will show no availability for that category on the affected dates, preventing any new bookings. |
Guests
The Guests category covers the guest's personal and contact information that is received from the channel when a reservation is made.
| Term | Definition |
|---|---|
| Surname | The guest’s family name or last name. When supported, this is received from the channel and stored on the guest record in RMS. |
| Given | The guest’s first name (also referred to as “Given Name” in some channel articles). When supported, this is received from the channel and stored on the guest record in RMS. |
| Address | The guest’s street address. When supported, this is received from the channel and stored on the guest record in RMS. |
| Town/Suburb | The guest’s city, town, or suburb. When supported, this is received from the channel and stored on the guest record in RMS. |
| State | The guest’s state, province, or region. When supported, this is received from the channel and stored on the guest record in RMS. |
| Postcode | The guest’s postal or ZIP code. When supported, this is received from the channel and stored on the guest record in RMS. |
| Country | The guest’s country of residence. When supported, this is received from the channel and stored on the guest record in RMS. |
| Phone | The guest’s contact telephone number. When supported, this is received from the channel and stored on the guest record in RMS. |
| The guest’s email address. When supported, this is received from the channel and stored on the guest record in RMS. An asterisk (*) indicates a footnote with additional details specific to that channel. |
Reservations
The Reservations category covers the types of booking actions that can be exchanged between the channel and RMS.
| Term | Definition |
|---|---|
| Single Reservation | A booking for one room or site. When supported, individual reservations made on the channel are automatically delivered to RMS and created as a reservation. |
| Group Reservation | A booking that includes multiple rooms or sites under a single booking reference (also known as a multi-room booking). When supported, group bookings made on the channel are delivered to RMS and linked together as a group reservation. When not supported, multi-room bookings may arrive as separate individual reservations or may not be supported at all. |
| Modification | A change to an existing reservation, such as updated dates, room type, guest count, or rate. When supported, modifications made on the channel are automatically sent to RMS and the reservation is updated accordingly. When not supported, any changes must be made manually in RMS. An asterisk (*) indicates a footnote with additional details specific to that channel. |
| Cancellation | The cancellation of an existing reservation. When supported, cancellations made on the channel are automatically sent to RMS and the reservation status is updated to cancelled. When not supported, cancellations must be processed manually in RMS. |
| Email Confirmation Sent By | Identifies which party sends the booking confirmation email to the guest. The value shown is the name of the channel or system responsible for sending the confirmation (e.g. “Booking.com”, “RMS”, or the channel name). This is important for properties to know so they do not send duplicate confirmation emails to guests. |
Reservation Details
The Reservation Details category covers the specific data fields included with each reservation received from the channel.
| Term | Definition |
|---|---|
| Adults | The number of adult guests included in the reservation. When supported, the adult count from the channel booking is stored on the reservation in RMS. |
| Children | The number of child guests included in the reservation. When supported, the children count from the channel booking is stored on the reservation in RMS. |
| Infants | The number of infant guests included in the reservation. When supported, the infant count from the channel booking is stored on the reservation in RMS. |
| Arrive & Depart Date | The check-in (arrival) and check-out (departure) dates for the reservation. When supported, these dates from the channel booking are used to create the reservation period in RMS. |
| Booking Source | The source or origin of the booking, identifying which channel or platform the reservation came from (e.g. “Booking.com”, “Expedia”). When supported, the booking source is recorded on the reservation in RMS, which is useful for reporting and tracking channel performance. |
| Category | The room or site category (type) assigned to the reservation (e.g. “Standard Room”, “Powered Site”). When supported, the category mapped in the Channel Manager determines which RMS category the reservation is created under. |
| ETA | Estimated Time of Arrival. The approximate time the guest expects to arrive at the property. When supported, the ETA provided by the guest during the channel booking is stored on the reservation in RMS. |
| OTA Notes | Notes or special requests submitted by the guest through the OTA (Online Travel Agency) at the time of booking. When supported, these notes are received from the channel and stored on the reservation in RMS, where staff can review them before the guest’s arrival. |
| Rate Type | The rate plan or rate type associated with the reservation (e.g. “Best Available Rate”, “Non-Refundable”). When supported, the rate type mapped in the Channel Manager is assigned to the reservation in RMS. |
| Travel Agent | The travel agent or agency associated with the reservation. When supported, the travel agent information from the channel booking is stored on the reservation in RMS, which is useful for commission tracking and reporting. |
Comments
0 comments
Please sign in to leave a comment.