How Palisis updates the capacity in TourCMS

Blanca Castillo
Blanca Castillo
  • Updated

Where do I find it?

Setup > Products & Services > Products

 

What does it mean?

In this article you will learn how the TourCMS capacity will automatically be updated once you have updated the corresponding capacity in Palisis.

This functionality is based on the following main assumptions which have to be met. In case of the contrary, the automatic update will fail:

  • The Product has the setting "Sync Capacity to Tour CMS" enabled and it also has a capacity template assigned.

  • The booking has an event that matches with a TourCMS departure in time. Please note, that this functionality won't work in case the event times and departure times differ.

Timetable in Palisis:

Departures in TourCMS:

  • The 'Price' is mapped towards TourCMS, so bookings from TourCMS arrive in Palisis. For the purpose of this article, we will name it "Price A". Note: the mapping section is still not available in the new backend.

 

Please, visit our related support article for more information How to do the mapping between TourCMS and Palisis

It means, that every time one of the following actions takes place in Palisis for "Price A", the available spaces for the corresponding departure in TourCMS will automatically be updated accordingly, in order to match the available spaces configured for "Price A":

  • New booking via device, Boxoffice, webshop or any other channel.

The same number of spaces will be reduced in the TourCMS departure.

  • Cancellation of a booking via device, Boxoffice or BackOffice.

The same number of spaces will be added to the TourCMS departure.

  • Activate/disable a ticket on the Booking detail screen.

If a ticket is being disabled, then, this space will be added to the TourCMS departure. If a ticket is enabled, then this space will be reduced in the TourCMS departure. 

Please, note that one space will be reduced/added as long as the capacity weight of the passenger category is 1. For instance, if the passenger category is "Family" with a capacity weight of 4, then 4 spaces will be reduced/added in TourCMS.

  • Reschedule a ticket in the Booking details screen.

LINK to article

The corresponding spaces will be added to the old TourCMS departure and reduced from the new one.

  • Refund a ticket and disabling it 

The same number of spaces will be added to the TourCMS departure.

  • Change of the capacity template in the "Pre-bookings" screen for a specific event

When you change the applied capacity template of a selected event in the "Pre-bookings" screen, the corresponding departure in TourCMS will be updated to the same vacant spaces.

Example:

Below, we have a capacity template showing 5 spaces, indicating that the event is overbooked. In TourCMS, the departure is closed due to the unavailability of seats.

If we wish to continue receiving bookings, we'll need to assign a larger capacity template to this event. In this instance, we'll update the capacity to 12 seats, so we have 7 vacancies. As a result, the TourCMS departure is also updated to 7 available spaces:

  • Check-in of a ticket with reschedule

The corresponding spaces will be added to the old TourCMS departure and reduced from the new one.

Example: Given a booking for 29/02/2024 at 16:00, when you click on "Reschedule" and select a new event, let's say 02/03/2024 at 16:00 then the corresponding spaces will be added to the TourCMS departure for 29/02/2024 at 16:00 and they will be reduced from the new TourCMS departure on 02/03/2024 at 16:00.

In Palisis we now have 4 vacancies:

And also in TourCMS:

Please, keep in mind that this functionality won't work in case the event times and departure times differ.

Exclusions

For now, the following actions won't update the capacity in TourCMS due to the huge impact this would imply in the system:

  • Change of the default capacity template in the 'Products' screen.

  • Change of the capacity inside a template (change of the template itself).

  • Change of the timetable