How Palisis creates/updates departures and prices in TourCMS

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.

Departure end time from Palisis duration

Palisis sends the TourCMS departure end time based on the event start time and the duration configured in the Palisis timetable. This applies to both newly created and updated departures.

• If no duration is set in Palisis, the TourCMS departure uses the same value for start time and end time.

• If a duration is set, Palisis calculates the TourCMS end time as start time + duration.

Example: if the Palisis event starts at 12:00 and the duration is 45 minutes, TourCMS receives an end time of 12:45.

Priceplan name in TourCMS product note

When Palisis creates departures in TourCMS, it also sends the priceplan name as a product note on the TourCMS departure.

This works for both single‑language and multi‑language setups: 
Palisis sends either the default or the translated priceplan name to TourCMS and stores it as the departure product note in the correct language, as long as the corresponding channel is mapped.

Important: Only one product note is sent per departure.

• If there is only one channel mapped, the note is sent in that channel’s language.

• If a translation exists for the price, the note is sent in the translated language for the channel using that language.

Important: This functionality also requires the Sync capacity and Sync price settings to be enabled.

Example: Price translated to German, and the German channel is properly mapped.

This helps your distribution partners (and your own team) quickly identify which priceplan was used to create the departure, especially when you have several variations of the same tour (e.g. “Standard”, “Premium”, “Evening Tour”, etc.).

Best practices for an initial setup

For the initial setup, kindly follow the steps outlined below to prevent inconsistencies between TourCMS and Palisis:

• The tour is almost fully set up in TourCMS, without departures. 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.