Organisation | Tools | Ticket models

Pre-requisite: create Ticket templates.

→ The ticket model section is a mandatory step in order to further associate ticket templates with products.

The ticket model is an aggregation of templates that will be available for a given product. For example, if, for a given event, you want only mobile and print@home templates to be available to customer, you will associate your mobile and p@h templates in a ticket model. Note that only one ticket model can be applied for each product. In the case of competitions/events, you can associate a different ticket model for each match/performance. This enables you to make exceptions (for example if, for one match, you do not want to have mobile tickets but only mobile tickets, then you can create a specific ticket model that you will ).

When you create a new ticket model:

Ticket type (different for each product family):

• Single ticket => for competitions / events

• Pass => for visit pass, open pass

• Simple Card => for badges (ex: membership cards) and season tickets

• Service => for Services, Vouchers, Donations

• Countermark => for season ticket exchange (feature no longer used)

Hardware family (on what printer tickets will be printed):

• Badge printer => for printing on badge printers (such as Evolis)

• Document printer => if printing on document printers

• Ticket printer =>

Associate all relevant templates to this ticket model. Note that only one template can be associated for each ticket support (you cannot associate 2 different PDF templates for the same product)

Ticket support:

• Thermal ticket => for printing on BOCA, Stimare and other supported thermal printers

• A4 ticket => for printing of PDF from the box office only

• E-Ticket => for print@home PDF

• Simple Card => for season tickets/badges with visible barcodes

• Blockchain => for tickets to inject in mobile APP such as TIXnGO

• Mobile ticket => for mobile templates (PDF responsive to smartphones)

• Passbook => Apple wallet tickets

• RFID => to allow ticket injection on RFID cards

Numbered => choosing both enables both numbered and non-numbered seats

File => available only when you can associate a file (for RFID printed support only)

Ticket format => this displays all the ticket templates available for the selected Ticket support. Some support do no require any Ticket format (blockchain, RFID)

Card type => select your card type (for RFID only)

Display products already associated to this ticket model. For information only.

Validate your ticket model to finish configuration.

Next step: associate your model to products

You can also request template creation via a service ticket (quote) to support.