What does it mean?
Let’s start with a bit of background on the integration between Palisis and TourCMS. The most common and well-known integration between the two systems is the downstream integration TourCMS -> Palisis. Meaning that when a booking arrives in TourCMS, the availability is checked against Palisis and the booking is automatically sent, as long as the check availability and notification webhooks point to Palisis. Therefore, devices are able to redeem vouchers which have been generated in TourCMS.
Figure 1. Downstream integration
Figure 2. Downstream integration with a subsystem
Now with the upstream integration, this process also works in the other direction, from Palisis to TourCMS. This means that when a booking is made in Palisis (boxoffice, device, webshop desktop or widget), it will automatically check the capacity against TourCMS (or another subsystem depending on the check availability webhook) and then the booking would be sent to TourCMS and the subsystem, as long as the notification webhook is correctly set up. Bookings coming from the TourCMS API are not sent as they are already in TourCMS.
Figure 3. Upstream integration
Figure 4. Upstream integration with a third subsystem
With the upstream integration, in addition to requesting availability from TourCMS and sending bookings there, Palisis is also able to pull prices from TourCMS or a subsystem, as long as the ‘Use Price from TourCMS’ checkbox is active for the operation line. In the same way, a booking cancelled in Palisis is also automatically canceled in TourCMS and the subsystem (if one is used).
This feature needs a pair of conditions to be implemented:
1. It will only apply to the mapped price plans between both systems. You can map different priceplans with different channels as long as you had entered the corresponding channel id in the priceplan mapping and you have provided our Support department with those channels credentials. If you don’t know how to configure that, take a look at our article about how to do the mapping between Palisis and TourCMS.
2. The TourCMS channel credentials have to be entered into the Palisis system internally. So, please, contact firstname.lastname@example.org informing us about the channel id and API key you want to use for the upstream integration. The channel id and API key can be retrieved from TourCMS in Configuration & setup > API.
3. The tour is TourCMS and the Operation line in Palisis should have the same schedule (departures at the same time). It means that the departure start time in TourCMS should be the same as the event time in Palisis.
What should I do?
First of all, please write to email@example.com to activate this functionality, sending your TourCMS account and the channel ID you want to integrate. Also, be sure price plans in Palisis are properly mapped to the corresponding tours in TourCMS. Now let’s see how to activate this functionality.
For each Operation Line (Configuration > Transportation > Operation lines), you have the option to select which platforms you want to check availability and/or send bookings to TourCMS.
Apart from that, you need to connect the travel agent "Palisis Distribution (TOURCMS49701)" to the corresponding channel in TourCMS as a "Trusted travel agent".
How do the bookings look?
The bookings in TourCMS are made by the travel agent "Palisis Distribution (TOURCMS49701)" and they will show the Palisis booking ID in the “Travel agent reference” field and the tickets IDs in the “Travel agent reference (Components)” field.
In Palisis, the TourCMS booking ID will be shown in the Foreign UID if there is no third party booking reference.
Please note that for bookings originating in TourCMS, voucher redemption will not be sent back to TourCMS in order to prevent duplicate bookings.