Description
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 Operation line 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 priceplan is mapped towards TourCMS, so bookings from TourCMS arrive in Palisis. For the purpose of this article, we will name it "priceplan A".
What does it mean?
It means, that every time one of the following actions takes place in Palisis for "priceplan A", the available spaces for the corresponding departure in TourCMS will automatically be updated accordingly, in order to match the available spaces configured for "priceplan 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.
- Disable/enable a ticket on the "Search Tickets" 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 "Search Tickets" screen
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 called "Bus" which has 5 spaces. Until this moment there haven't been any bookings made for this event, so we have 5 available spaces both in Palisis and TourCMS.
We now have received 5 bookings and want to add more available spaces. We change the capacity template with 5 spaces to a template with 12 spaces. As a result, the TourCMS departure will also be updated to 12 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 21/11/2019 at 12:00, when you click on "Checkin" and select a new event, let's say 22/11/2019 at 16:00 then the corresponding spaces will be added to the TourCMS departure for 21/11/2019 at 12:00 and they will be reduced from the new TourCMS departure on 22/11/2019 at 16:00.
It's worth mentioning that once the Palisis capacity has been reached, the corresponding TourCMS departure will appear as manually closed.
As you can see in the example, if you have activated this option "Sync Capacity to Tour CMS” in your operation line, the departures in TourCMS will be updated with the capacity that you have in Palisis.
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 Operation Line screen.
-
Change of the capacity inside a template (change of the template itself).
-
Change of the timetable
Comments
0 comments
Article is closed for comments.