S-360 Screen Help

Page tree

Create your ticket templates in this section for all your products, including gift vouchers. These ticket templates can be re-used across various products and competitions.

There are multiple possible templates:

  • Thermal => for thermal printers (BOCA, Stimare)
  • PDF => standard A4 print@home
  • Mobile => PDF responsive for smartphones
  • Passbook => for Apple wallet

Main Screen

New: create a new template

Copy: select a template and copy the entire template. You can then rename it.

Delete: delete a template is possible only if this template is not associated to a ticket model

Export: select a template and export all fields in an XML format

Import: import a template (XML format). These export-imports functions are useful if you need to migrate a template from an environment to another. If you are satisfied with a template in PreProd, you can Export it and Import in PROD.

Hide: hide a template you do not use anymore



Name: can be defined when a new template is created. Extension is automatically added depending on the type of template

Basic template: technical internal value – type of template (PDF, mobile...)

Last Modification: template modified when and by whom (Institution@Operator)

Comment: free text for internal purposes. To add a comment, open the template, then click on  and edit your comment


Working on a template

Three types of elements can be added to tickets:

  • TEXT
    • Parameter value => dynamic text - e.g. contact name, seat category, match start time
    • Static value => hardcoded text – e.g. generic information
    • Custom value => Combination of dynamic values (and/or static values)
  • IMAGE
    • Static image => e.g. sponsor logo
    • Dynamic image => e.g. contact profile picture
  • BARCODE
    • 1D
    • 2D (QR Code will be available for thermal tickets as from in Whymper V3).




Italian Certification | Specific behaviour

NB: Due to Italian law, Italian clients using a Certified S-360 license must keep the following fields in the ticket template when used for fiscal products.


While "File: Operation_field" is not strictly mandatory, it is highly recommended.


Loads of useful tips are available here.

Next Steps

Once your templates are ready, or even if they are a work in progress, you can create Ticket Models that will then be associated to products,





  • No labels