Content Services for Lodging (CSL) provides Sabre-connected agencies with over 1.3 million unique lodging properties including traditional GDS content and aggregator content such as Booking.com, and Bedsonline. CSL is available via Sabre APIs and will become your new hotel shopping and booking capability when you upgrade to the latest Sabre Red 360 version (20.11). For Sabre Red 360 users, explore and get ready at http://www.sabrered360.com/csl-onboarding/.
If you are planning to book CSL aggregator content, adjustments are necessary in Trams Back Office (TBO) to capture and report these bookings. Please read the below table carefully as it outlines differences in lodging booking types and how they should be managed.
The following outlines the recommended process for aggregator bookings. There are no changes to traditional GDS lodging bookings.
|
|
Booking a "Sabre" Property via an Aggregator |
Booking an "Aggregator-Unique" Property via an Aggregator |
|
Description |
A "Sabre" property is a property that can be booked via an aggregator but can also be booked direct via its own Hotel Central Reservation System (CRS) in Sabre. |
An "Aggregator-Unique" Property is a property that can only be booked via an aggregator. The property cannot be booked direct via its own Hotel Central Reservation System (CRS). |
|
How to Tell the Source of a Booking |
You can determine whether a property is represented on its own CRS by looking at the Sabre ID field. If it contains a property ID, then you know it is a Sabre Property. |
You can determine whether a property is an Aggregator-Unique Hotel Property by looking at the Sabre ID field. If it does not contain a property ID ("No Data"), then you know it is an Aggregator-Unique Hotel Property. |
|
|
 |
 |
|
Without Adjustment |
Without adjustment, when these bookings are interfaced into TBO they create a duplicate Vendor Profile because TBO will recognize the aggregator code instead of the chain code and will create a new Interface ID despite the fact that the Vendor Profile already exists in TBO. |
Without adjustment, when these bookings are interfaced into TBO only the aggregator code will be used when creating the Interface ID. This will result in loss of hotel detail for reports and invoices and would require manual intervention during the interface processing to ensure the booking is linked to the correct Vendor Profile. |
|
With Adjustment |
We recommend that the agent uses the Sabre ID and the hotel chain code and enter it as a Vendor Code override in the PNR Remarks. If the agent also wishes to track which aggregator was used for the booking, the agent can add it to the end of the remark with a UDID. 5.S*MS1*VCBW176194*UD43 7B |
If the agency already has the hotel profile in TBO, we recommend the agent look up the Interface ID for that property in TBO and enter it as a Vendor Code override in the PNR Remarks. If the agent also wishes to track which aggregator was used for the booking, the agent can add it to the end of the remark with a UDID. 5.S*MS1*VCXXXXXXX*UD43 7B If the agency does not already have a Vendor Profile for the hotel in TBO, we recommend that the agent enter the Sabre Global ID as the Vendor Code override in the PNR. Doing this will support Sabre's long-term solution to automatically use the Sabre Global ID for the Interface ID, enabling these properties to interface seamlessly with the Vendor Profile. 5.S*MS1*VC100088159*UD43 7B NOTE: If the agency has Vendor Profiles already built for aggregator bookings that do not use a Sabre ID for the Interface ID, we recommend that you change the Interface ID in TBO to the Sabre Global ID. This will make it easier for the agent to create the Vendor Code override and ultimately, will align with our long-term solution to automatically use the Sabre Global ID for the Interface ID. |
If you do not want to use the recommendation, you can deactivate aggregator credentials via Hotel Manager.
If you have questions regarding this product update, please contact the Trams Support Team.