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
3. Other important settings
h) Product Profile
i) Payment methods
4. Advanced menus
j) Charges
k) Custom variables
l) Transport stops
m) Price breakdown
n) Access control synchronization (not used)
5. Validation
6. Filters and main screen buttons
1. Anchor Types Types
Definition and types
Types | |
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 ticket: according to your license, there are 3 types:
...
NB: once chosen, the price type cannot be modified
♦ Calculated price
The customerneeds customer needs to choice their tickets at the time of ordering the season ticket. The price is the sum of the prices of the tickets, using a specific season ticket tariff.
...
When selected it requires to specify the competition. See Organization | Catalog | Competition
♦ NEW Fixed seat season ticket
This season tickets is thought to meet some specific needs for German and Austrian markets.
See more details here.
2. Anchor New New
Create a new season ticket: basic settings
New | |
New |
a) General | General
Internal name (max 60 char.): name of your season ticket as it will appear in SECUTIX screen (backoffice)
...
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.
...
Tax VAT:VAT rate that will be used for your season ticket. To be selected among the drop down elements. It cannot be changed afterwards.
See : Institution | 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
Ticket printing mode: it is required to choose among two options: 1) Ticket only, to skip the printing of the season ticket itself (no card), 2) Simple card only, to avoid the printing of tickets;
...
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 Organization | Initialization | Shipment Fees
Remark:text field to insert comment. This will remain at back office level.
...
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.
...
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 |
Among the other menus be sure you define, or review, accordingly:
...
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
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.
...
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.
4. Anchor Collateral Collateral
Advanced menus
Collateral | |
Collateral |
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 | ||
---|---|---|
| ||
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 List of variables in the Ticket Editor (auto translated to English)
...
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
Not used at season ticket level.
5. Anchor Validation Validation
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.
6. Anchor Settings Settings
Filters and main screen buttons
Settings | |
Settings |
The screen buttons perform the following actions:
...