Video
Where can I find it?
Setup > Products & Services > Products > Edit
What does it mean?
In this article, you'll discover how a price change in Palisis automatically updates TourCMS prices for existing departures. For departures that don't exist yet, they're generated based on the timetable and prices in Palisis.
This feature enables you to create departure schedules and prices solely in Palisis. The system then replicates these changes in TourCMS, eliminating the need to input the same information in both systems. Say goodbye to duplicating dates across platforms and welcome the efficiency of synchronized updates between Palisis and TourCMS!
If a calendar event is closed or removed in Palisis, it will also be closed in TourCMS. Consequently, both systems will offer the same availability and prices since they are synchronized.
Note: This process is asynchronous, meaning it does not trigger the sync simultaneously.
What should I do?
This functionality is based on the following main assumptions that must be met. In case of the contrary, the automatic update will fail:
- The tour is properly created in TourCMS except for the ‘DATES & PRICES’ tab.
- The product is created in Palisis with a capacity template, Route, Calendar (Timetable) and Prices.
- The product has the settings "Sync capacity to TourCMS " and "Sync price to TourCMS" enabled, and it also has a capacity template assigned. Please note that if you want to sync price to TourCMS then you have to select both checkboxes, however, if you only want to sync the capacity, you only need to select the option "Sync capacity to TourCMS".
A price must be configured for the API channel (the channel used for the TourCMS API connection); otherwise the synchronization will fail.
- The tour in TourCMS and the product in Palisis share identical event times. Please be aware that this feature will not function if there are discrepancies between the event and departure times.
Calendar > Timetable in Palisis:
Departures in TourCMS:
- The products must be mapped with TourCMS.
Please visit the support article ‘How to do the mapping between TourCMS and Palisis’ to learn the process.
Best practices for an initial setup
For the initial setup, kindly follow the steps outlined below to prevent inconsistencies between TourCMS and Palisis:
- No departures in TourCMS. It means that ‘DATES & PRICES’ is empty for future departures.
- Create the Product, Route and Prices in Palisis.
- Turn on the Sync switches in Palisis.
- Enter the mapping in Palisis. Please visit the support article ‘How to map between TourCMS and Palisis’ to learn the process.
- Finally, create the Calendar (Timetable) in Palisis for that product. It will trigger the creation of departures in TourCMS according to the mapping.
Please keep in mind that a change in the mapping or in the calendar (timetable) will affect the synchronization.
Troubleshooting
If your departures or prices aren't automatically updating or appearing in TourCMS after making changes in Palisis, check the following:
TourCMS tour setup:
- Ensure the tour in TourCMS is properly created, but with an empty 'DATES & PRICES' tab for future departures. This synchronization feature is designed for Palisis to be the primary source for this information.
Palisis product setup:
- Verify that your product in Palisis is fully configured with:
- A capacity template has been assigned.
- A Route.
- Prices defined.
- The Calendar (Timetable) should be created in Palisis after the initial setup (see "Best practices for an initial setup" below).
Synchronization settings in Palisis:
- Go to your product settings in Palisis. Confirm that the "Sync capacity to TourCMS" and "Sync price to TourCMS" checkboxes are enabled. Important: If you want to sync prices, both checkboxes must be selected. If you only want to sync capacity, only "Sync capacity to TourCMS" needs to be enabled.
- Ensure a capacity template is assigned to the product.
A price must be configured for the API channel (the channel used for the TourCMS API connection); otherwise the synchronization will fail.
Identical event times:
- This is a critical requirement for the synchronization to function correctly. The tour event times in TourCMS and the product event times in Palisis must be identical. Any discrepancies will prevent the synchronization from working.
- Palisis: Check these times by navigating to Calendar > Timetable.
- TourCMS: Verify these times under Departures.
Product mapping with TourCMS:
The products in Palisis must be correctly mapped with TourCMS.
Refer to the "How to do the mapping between TourCMS and Palisis" support article to review your mapping setup.
Changes in mapping or calendar (timetable):
Be aware that any change in the mapping or in the Palisis calendar (timetable) will directly affect the synchronization. If you've recently modified these, it might be the cause of the issue.
Still having issues?
If you've checked all the points above and are still experiencing problems with your automatic price and departure synchronization, please gather all relevant details and contact our Support team here for further assistance.