Reference OTA booking numbers when sending modifications
James Lee
started a topic
7 days ago
1 person likes this idea
Currently, the logic for Stayntouch, when a modification is received from a CRS the system will match the reservation with the CRS number. If the CRS number does not exist, the modification then becomes a new reservation in Stayntouch. This becomes an issue when hotels switch CRS systems. As any modification from an OTA booking made from their previous CRS will then be duplicated in Stayntouch due to the new CRS number not existing in Stayntouch.
Pod Times Square is dealing with this issue as they have moved from Synxis to Siteminder. They are requesting that a 2nd logic be introduced to also look at the OTA Booking Numbers, if it exists, and match the reservations by that number. This way the modification does not cause a duplicate reservations. as the OTA Booking Number should exist already.
1 person likes this idea
Currently, the logic for Stayntouch, when a modification is received from a CRS the system will match the reservation with the CRS number. If the CRS number does not exist, the modification then becomes a new reservation in Stayntouch. This becomes an issue when hotels switch CRS systems. As any modification from an OTA booking made from their previous CRS will then be duplicated in Stayntouch due to the new CRS number not existing in Stayntouch.
Pod Times Square is dealing with this issue as they have moved from Synxis to Siteminder. They are requesting that a 2nd logic be introduced to also look at the OTA Booking Numbers, if it exists, and match the reservations by that number. This way the modification does not cause a duplicate reservations. as the OTA Booking Number should exist already.