Page History

...

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

3. Important Other important settings
h) Product Profile
i) Payment methods
j) Shipping modes

4. Collateral menus

kj) Charges
lk) Custom variables
ml) Transport stops
nm) Price breakdown
on) Access control synchronisation

5. Validation

...

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

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 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.

...

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.

f) Fixed price (Predefined and Championship only)

This is a mandatory screen for predefined season tickets: it is required to set the prices of the whole season tickets, by allowed 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

Among the other menus be sure you define, or review, accordingly:

h) Product profile

This is where you associate the set of rules regarding the selling of your season ticket. Among the rules, it will determine tariffs, quantities and sales date ranges for which the product will be available per sales channels.
See: Organization | Catalog | Product Profile

Image Added

i) Payment methods

From this menu, you can define payment methods that can be used to purchase this product.

The rule is as follow: it is the intersection of Point of Sales Payment Methods, Product Family Payment Methods (see: Institution | Initialization | Payment Methods) and Product Payment Methods.

Thus, if you associate no payment methods in this screen, SecuTix will check for specific Payment Methods set at Product Family level. If none, it means that any Payment methods available on the point of sales will be usable for the product. The payment method you associate at product level must be available at least on the point of sales. Otherwise nothing will happen.

So if you want to have a payment method that is only available for your season tickets for example, you need to associate this payment method to your point of sales AND associate it at product family level.
That way this payment methods will only be available for your season tickets products on your point of sales.

Image Added

4.
Anchor
#Collateral
#Collateral
Collateral menus

j) Charges

When using Charges (fees that apply per ticket), you can associate one or more of your existing charges tables, by time and sales channel.
Either All sales channels or a List you can set up. You can apply different charges table on different sales channels.
See : Organization | Catalog | Charges tables

Info

title	Italian Certification \| Specific behaviour

Italian clients using a Certified S-360 license can configure presale prices in Price Breakdown menu (point j, below) as described here

k) Custom variables

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 "Free text" (1 to 6) in the ticket editor. See (French) Liste des variables dans l'éditeur de maquettes de billets

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.

TixNGo for instance is using those fields to input the parameters such as the image or the url that will be displayed on the ticket in the TixNGo wallet.

l) Transport stops

              This options are for customers selling combined offers including leisure and public transportation. Mainly for Swiss customers
              They may define which stations or stops belonging to a public transportation network allow to reach the product associated.

              i) Price breakdown

This screen allows to define multiple price components (ticketing, food, parking, promoter...) for prices defined previously.
Relevant information on the configuration can be found here and here for price breakdown bottom-up.

k) Access control synchronisation

When using SecuTix Access Control, this screen allows you to synchronize directly the product you have just created with SecuTix Access Control.

The season of your product must already exist in the Access Control.

Obviously this screen is useful only if you have already sync your season with the Access Control, but created the product afterwards.

5.
Anchor
#Validation
#Validation
Validation

The validation step will make sure that you did not forget to set any mandatory information. In such a case, the message displayed will refer to what is missing.
If nothing is missing it will proceed in the actual creation that will become available for Running.