CRS-IFC: Data Exchange Between StayNTouch Cloud PMS and SiteMinder

Modified on: Fri, 5 Mar, 2021 at 3:36 AM

Applies to:       StayNTouch Cloud PMS    StayNTouch PMS Overlay

Data Exchange Between StayNTouch Cloud PMS and SiteMinder

The idea of 2-way interface between StayNTouch Cloud PMS and SiteMinder is a bit misleading. It means both systems are sending data to each other; however, the traffic flow is not 1:1 between StayNTouch Cloud PMS and SiteMinder. 


Availability updates are sent only from PMS to CRS. StayNTouch Cloud PMS sends availability updates with changes of inventory (e.g., new reservations, called reservation, room Out of Order, etc.).


Rates and restrictions are sent only from PMS to CRS. Rates created in StayNTouch Cloud PMS and configured in the channel manager will be sent to the CRS.


To successfully synchronize rates at the time of the rate creation, the recommended process to allow data to be successfully published to the CRS is as follows: 

  1. Build the rate in the CRS.
  2. Build the rate in StayNTouch Cloud PMS. The rate code used must match in both systems (unless a translation table is used, in which case, the translation must be defined prior to step 3).
  3. Publish the rate by adding the new rate code in the StayNTouch Cloud PMS channel manager.


Rates are updated only if the following are true: 

  • A rate change is made in StayNTouch Cloud PMS rate manager or a change is made in the StayNTouch Cloud PMS rate code details and pushed to the rate manager. 
  • A rate sync is triggered on the StayNTouch Cloud PMS side.

Please note, if the rate codes (and the rooms associated to the rates) DO NOT match the rate code exactly, they will automatically move to "not active" in StayNTouch Cloud PMS channel manager and will stop sending updates. Any room type mismatch will also cause the availability updates sent by StayNTouch Cloud PMS to fail


New reservations, updates, and cancellations are sent only from the CRS to StayNTouch Cloud PMS.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.