| Info | ||
|---|---|---|
| ||
|
Prerequisite: create a Season, Tariffs (subscribed contact/structure), Price Level, Ticket models
Aim: create and manage your season tickets
2. Create a new season ticket: basic settings
a) General: i. General
ii. Parameters
♦ Calculated price
♦ Predefined/Fixed-price and Championship
b) Grouping
c) Line
d) Quotas
e) Tariffs
f) Fixed price (Predefined only)
g) Seat category
...
It is a special type of fixed-price season ticket that does not allow the customer to choose: once purchased, it cannot be modified but offers access to every match in a championship of a given sport club
When selected it requires to specify the competition. See Organization | Catalog | Competition
...
Tax VAT:VAT rate that will be used for your season ticket. To be selected among the dropdown elements. It cannot be changed afterwards.
See : Institution | Initialisation Initialization | VAT Rates
Product types: it is possible to choose among the values created in Organization | Initialization | Product Types
Alert ratio (%): Threshold of remaining availability from which the season ticket will be considered as with "limited availability".
This will trigger the availability color used on the ticketshop (it will become orange as soon as the level is reached) and display the Alert Quota message in the back office.
Seat category mapping: allows to select among the values defined in Organization | Venue | Mapping tables
...
SHA Key:related to the merchant ID, hash key to finalize the setup of the merchant ID
Logo:(max size size 1 Mb) image that will be used to illustrate the product. This image will appear on the landing page and on different pages of the ticket shop.
Depending on the setup of your landing page, you may want to pay attention to the ratio or to where you position the main element in your image. More info on A dynamic shop window
...
b) General / Parameter
Settings The following settings are shared by all types:
Price type: shows the season ticket type chosen at first stage of the creation process.
Allow subscriber quality: indicates whether the contacts become "subscriber" after purchasing this product. If yes, it will trigger Season Ticket Holder Indicator in Standard Indicators if activated.
It also means the customers will be entitled to access Subscriber Tariffs outside the season ticket.
Minimum subscription lines: is the minimum number of lines to be chosen when the season ticket is purchased
Maximum subscription lines: is the maximum number of lines allowed by the season tickets
Separate events: ??
Price level: it allows to select among the "Subscriber" Price level levels predefined in Organization | Initialization | Price level. It is mandatory.
Internet cultural contact: defines if cultural contact is optional/mandatory/not required for online sales
Same seat: as well as general configuration limits the overlapping between simple tickets and season tickets sales, if set as "yes" the system will pick the same seat for all the performances selected with the season ticket.
Whereas this is not possible, the system will suggest the most similar seats (according to best-seat algorithm)
...
Charge definition: it defines if charges are calculated at the season ticket or event level
Additional seats (tab): ♦ Predefined/Fixed-price and in this specif tab it is possible to define the rules for additional seats, with dedicated limits (global and per performances), as well as tariffs.
♦ Predefined/Fixed-price and Championship
Number of authorized tickets: is the total number of tickets that a customer could select inside this season ticket product
Maximum number of tickets per event: defines how many tickets per event are allowed by the product
Maximum number of tickets per performance: defines how many tickets per performance are allowed by the product
Min subscription lines*: defines how many lines (events) must be chosen at the same time the season tickets is purchased. If set to 0 it means the subscriber can buy just the season ticket without using it contextually.
Max subscription lines*: defines how many lines (events) can be chosen at most
*Lines are specified in the homonym menu
Example: In the example configuration shown above the product allows max. 6 tickets, to be used for no more than 4 events (among which 2 must be chosen straightaway).
Since there's a max limit per event and performance equal = 2, the customer can use the season ticket in several combinations:
i) 1 tickets per for 2 different events + 2 tickets for the same performance of 2 other different events
ii) 1 tickets per for 2 different events + 2 tickets for two different separated performances of 2 other different events
iii) 2 tickets for the same performance of 3 different events
etc etc
b) Grouping
The screen (optional) allows to defines groups of lines, for which set specific min and max limits.
Such setting has to be consistent with the basic limits defined in General | Parameter otherwise the season ticket might not work as expected or at all.
c) Line
In this menu you link the of your season's events to the season ticket:. Other lines can be added after the product is validated/run, though it must be set as suspended first.
In order add (
) the events the following screen requires the selection of the Activity first and the Grouping (if configured).
Choice: if Optional, the subscriber have the possibility to choose the given event, picking among the available dates defined by "Performance selection".
if Mandatory, the customer must select the event as defined by "Performance selection".
NB: this setting must be consistent with the basic limits defined in General | Parameter and Groupings (when used), otherwise the season ticket might not work as expected or at all.
Allow seat category upgrade/downgrade (used for online sales only): xx
Performance selection: the dropdown menu allows to choose one performance only, among several ones, or all (always in light of the already defined filters)
Filter rate types: this filters allows to select among the possible different rate types used by the event's performances
Perfomances: allows to select the list of available dates
Other lines can be added afterwards though the season ticket must be set as suspended first. d) Quotas
In this screen you set how many season ticket of this kind you intend to sell. This value can be modified ongoing.
♦ Calculated price
...
Quotas must be defined per each seat category for which the season ticket is allowed to be used.
e) Tariffs
In this screen you can select specific subscriber type tariffs, or consider all the available ones. NB: at least one Subscriber Contact Tariff must have been configured first
Computed price season ticket holder will be then able to access such tariffs according to the given rules: NB be sure to add these tariffs to the events' rates table included in Line menu.
...
This is a mandatory screen for predefined season tickets: it is required to set the total prices of the whole season ticketsticket, by allowed permitted tariffs and seat categories.
g) Seat category
An informative screen that displays all the seat categories selected (with a quota) for any given Site/Space/Logical configuration used by the selected events (Lines)
3.Anchor #Settings #Settings
Other important settings
| #Settings | |
| #Settings |
...
Custom variables are to be created in Organization | Initialization | Custom Variables.
Custom variables are element you can display on ticket. They are usually used to display static information that can not be setup elsewhere in SecuTix.
They are related to the fields fields "Free text" (1 to 6) in in the ticket editor. See (French) Liste des variables dans l'éditeur de maquettes de billets List of variables in the Ticket Editor (auto translated to English)
They can also be used through API and interfaces between SecuTix and 3rd party system, in order to setup in SecuTix sets of information that will be pushed and handled by the 3rd party system.
...