Parameters defining the reservation payment deadline can already be defined at product level for some product families. This improvement allows you to define also these parameters at season level. This brings you following advantages:
Solution
Defining the number of days at season level
You will be able to define the number of days in the season detail screen (menu organisation context > Initialisation > Seasons):
Compute the reservation deadline
- The number of days at season level are default values that may be overridden at product level
- If the number of days has been set-up (either at season level, at product level, or both)
- If the confirmation delay after reservation has been set, compute a reservation deadline DL1 by adding the confirmation delay after reservation to the reservation date
- If the confirmation delay before start time has been set, compute a reservation deadline DL2 by subtracting the confirmation delay before start time from the product validity start date
- Consider the minimum of DL 1 and DL 2
- If the computed reservation deadline is before the reservation date, consider the reservation date as the deadline
- If DL1 or DL2 can't be computed (because the information needed to compute them isn't available), it is simply ignored in computation above
- If no number of days at all has been set up
- Consider the performance start date or the timeslot start date or the season end date depending on the product family.
This computation is illustrated below:
Product families taken into account
The EXPIRATION DATE is only calculated for reservation orders for products from the following product families:
- Event/Competition
- Visit pass/Timeslot pass/Open pass
- Hospitality
- Service
- Goods
- Membership
The date is computed for orders created on Box Office and Ticket Shop
Getting started
You can enable this feature by making a request to our service team that will turn on the flag CONFIRMATION_DELAY_MANAGEMENT.