All Collections
Distribution
Connectivities
Map your room rates to your connected PMS, RMS or CRS
Map your room rates to your connected PMS, RMS or CRS
Updated over a week ago

To map your room rates to a connected property management system, PMS; revenue management system, RMS; or central reservations system, CRS, go to Distribution > Connectivities.

Introduction to mapping to your connected PMS, RMS or CRS

If you have a property management system (PMS), revenue management system (RMS) or central reservations system (CRS) integrated with the SiteMinder platform (Distribution > Connectivities), you must map all your required room rates in your platform to the corresponding room rate in your connected system.

This will ensure your inventory grid reflects accurate availability and rates, and updates are sent to your connected channels. It will ensure any new reservations made via your connected channels are sent directly into your connected system, reducing the likelihood of overbookings or missed reservations.

Before mapping to your PMS, RMS or CRS, make sure you:

  • Create rooms and rates in your platform and in your PMS, RMS or CRS — rooms and rates must be configured in the same manner across your platform, channels, and integrated systems.

  • Map your room rates to your PMS, RMS or CRS before mapping your channels — this helps to ensure that the inventory in your systems is synchronised and up to date.

To help prevent cross-mapping and overbookings, rooms and rates must be configured in the same manner across your platform, channels, and integrated systems.

Map your room rates to your connected PMS, RMS or CRS

Follow the steps below to map your room rates to your connected PMS, RMS or CRS.

  1. Go to Distribution > Connectivities and click on the name of your connected system.

  2. Go to the Rooms and rates mapping tab.

  3. Under the Mapping status filter, select Unmapped.

  4. Locate the room rate you want to map and click on Map to < name>.

  5. Click on Save.

  6. Repeat steps 4 through 6 for each room rate that you want to map.

  7. Once you have mapped all required room rates, initiate a 'push' of all inventory from your connected system to ensure the most up-to-date information is sent through. If you do not know how to do this, please contact your system provider’s support team.

Common mapping fields

  • Room code — the code assigned to this room type in your PMS, RMS or CRS.

  • Rate code — the code assigned to this rate plan in your PMS, RMS or CRS.

  • Inventory code — the code assigned to this room rate in your PMS, RMS or CRS.

To help avoid overbookings or missed reservations, you must map all of your required room rates from your platform to your connected PMS, RMS or CRS that you have connected in Distribution > Connectivities.

If you have unmapped rates:

  • Availability, rate and restriction updates made in your connected PMS, RMS or CRS will not be sent to your SiteMinder platform or to your connected channel(s), and vice versa.

  • If an unmapped rate is booked on a connected channel, the reservation will not be sent through to your connected PMS, RMS or CRS (if applicable).

To review and map any unmapped rates, go to Distribution > Connectivities > Room and Rate Mapping > Unmapped.


If you have unwanted room rates in your channel(s) or connected systems, you should delete them to avoid any potential issues. Contact the support team of the channel or system provider if you need help with this.

Set up reservation delivery failure emails

You can choose to receive email notifications if a reservation fails to be delivered from our platform to your connected PMS, RMS or CRS..

To set up these Reservation delivery failure emails , follow the steps below.

  1. Go to Distribution > Connectivities and click on the name of your connected system.

  2. Go to the Settings tab.

  3. Locate the Reservation delivery failure emails section and click on its edit button.

  4. Add recipient e-mail addresses, as required — a maximum of five in each of the five fields.

  5. Click on Save.

Did this answer your question?