Info
Under construction
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
♦ Championship
b) Grouping
c) Line
d) Quotas
e) Tariffs
f) Fixed price (Predefined only)
g) Seat category
3. Important settings
h) Product Profile
i) Payment methods
j) Shipping modes
4. Collateral menus
k) Charges
l) Custom variables
m) Transport stops
n) Price breakdown
o) Access control synchronisation
5. Validation
6. Filters and main screen buttons
1. Definition and types
In SecuTix a Season Ticket is as "Composed product".
It is defined as a contract between the organization an its customers, which offers seats for a purchase at reduced rates in return for a commitment to attend a certain number of events (all, or a subset).
Button 
allows to create a new season: according to your license, there are 3 types:
NB: once chosen, the price type cannot be modified
♦ Calculated price
The customer can buy a seat of tickets within a single season: the season ticket defines the conditions on the number of the tickets (globally or per topic).
The subscriber gets reduced prices compared to event tickets bought separately: the overall price of the season ticket is directly defined by the total number of tickets bought.
♦ Predefined/Fixed-price
For a predefined amount, the purchases has the right to choose at most N performances.
The customers pay upfront one overall price, which entitles them to a fixed number of seats that they can choose for themselves.
Subscribers can choose seats after purchasing the season ticket, without exceeding the permitted number of seats.
Italian Certification | Specific behaviour
For Italian clients using a Certified S-360 license only this type of season ticket will be available.
♦ Championship
Season tickets of this kind give the right to assist to all matches of a given championship.
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
2. Create a new season ticket: basic settings
a) General | General
Internal name (max 60 char.): name of your season ticket as it will appear in SecuTix screen (backoffice)
External name (max 60 char.): name of your season ticket as it will appear to your clients (online, documents, tickets)
Short public name (max 15 char.): name of your season ticket as it will appear online when accessed from a device with small resolution (smartphone...)
Public Description: it will be used by the ticketshop.
There will be as many descriptions as the numbers of external languages set at Institution | Initialization | Institution characteristics: if left empty, the Ticketshop will use the main language description.
Customization are possible on the inserted elements, including external content insert like images or video with the Source code button 
and the use of html codes.
Code (max 8 char.): STX code of the product. This code must be unique per entity (example: it's not possible to have the same code for two events, but possible for 1 rate table and 1 event)
Italian Certification | Specific behaviour
Italian clients using a Certified S-360 license will need to define it as a 4-characters code, unique by Institution.
The system will automatically add 4 more characters (8 in total) that will be displayed in C2 reports.
Another mandatory field is "Data di validità (scadenza)"
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 | 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
Ticket printing mode: it is required to choose among two options: 1) Simple card only, to avoid the printing of tickets; 2) Ticket only, to skip the printing of the season ticket itself
Ticket model: Ticket model that will be used for the season ticket (Simple card type only)
If left empty, and Ticket printing mode is set to "Tickets only", the system will use the ticket models of the events
Producer / Promoter / Partner: useful when using the producer portal. Producer contact (structure of type producer) can be linked to the product.
This contact will be able to access data related to this product in his producer portal.
Additional Producer / Promoter / Partner: useful when using the producer portal.
Additional producer contact (structure of type producer) can be linked to the product. This contact will be able to access data related to this product in his producer portal.
Invoice Producer / Promoter / Partner: useful when using the producer portal. This producer contact will be invoiced for the product.
The contact set in this field has no access to the producer data in the portal but can be the same as defined in the producer fields. Needs to be define even if the producer has been set.
Italian Certification | Specific behaviour
Italian clients using a Certified S-360 license will also have to define:
- "Organizzatore": a structure contact that must have both an Italian address and VAT/"Codice fiscale". Name and VAT are included in ticket template and C1 reports.
Merchant Id: in case of split payment (installments), configuration of the merchant ID (instead of having it inherited from ePC)
SHA Key: related to the merchant ID, hash key to finalize the setup of the merchant ID
Logo: (max 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
Internet description URL: link to an external page that will appear behind the More Information link.
This link is displayed after the Public description on the ticketshop. It aims at directing people to a page where you would usually present the event. To be used with care as it takes users out of the funnel.
Include in shipment fee: for cases where shipment fees where set to be Per ticket, you can choose if the product will be applying the shipment fees or not.
This provide the flexibility to say that some products are not eligible for shipment fees. See Organisation | Initialisation | Shipment Fees
Remark: text field to insert comment. This will remain at back office level.
b) General / Parameter
Settings 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 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)
Multi-seasons: allows to use the product across different seasons
Automatic renewal: if yes, required the activation and configuration of the Season Ticket renewal batch. The related fiels "Number of season" will be activated if so in order to allow the imputation.
Contingent: allows to select an existing contingent that will be considered as the only one available for this product.
It means that only the seats configured as such in the events' logical configurations will be selectable by the season tickets holders.
♦ Calculated price
wip
♦ Predefined/Fixed-price
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
In the example 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 2 different events + 2 tickets for the same performance of 2 other events
ii) 1 tickets per 2 different events + 2 tickets for two different performances of 2 other events
iii) 2 tickets for the same performance of 3 different events
etc etc
b) Grouping
c) Line
d) Quotas
e) Tariffs
f) Fixed price (Predefined only)
g) Seat category