/
Organisation | Catalogue | Events

Organisation | Catalogue | Events

Oct 20, 2024

Prerequisite: create a Season, at least one Activity, a Rate table and a Logical Configuration

Aim: create and manage your events

  1. Create a new event: first basic settings
    a) General:  i. General
                       ii. Parameters

  2. Create the performances
    b) Calendar

  3. Important settings
    c) Activity profile
    d) Payment methods

  4. Advanced menus
    e) Custom variables
    f)  Sub-groupings
    g) Charges table allocation
    h) Transport stops
    i)  Interface mappings
    j)  Ticket logos
    k) Access control synchronization

  5. Validation

  6. Filters and main screen buttons

     1.
Create a new event: first basic settings

         Button

allows to create a new event from scratch. First, it requires to select one Activity, among the list of the existing ones:

             a) General / General

Internal name (max 60 char.): name of your event as it will appear in SECUTIX screen (backoffice)

External name (max 60 char.): name of your event as it will appear to your clients (online, documents, tickets)

Short public name (max 15 char.): name of your product 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)

Tax VAT: VAT rate that will be used for your event. To be selected among the dropdown elements. It cannot be changed afterwards.
See : Institution | Initialization | VAT Rates

Alert ratio (%): Threshold of remaining availability from which the event 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.

Ticket model: Ticket model that will be used for the event (applied for all the performances, if not overloaded at performance level)
Even if modifiable, if not set before sales start, all tickets already issued cannot be reprinted anyway.

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:

General

  • "Tipo Evento": choosing among the predefined SIAE list. The correct VAT will be then input automatically. Both values are included in ticket template and C1 reports.

  • "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

Allow ticket printing before seating: in the case of post seating, you can choose to still issue ticket even if no seat was allocated to the contact.
This means that you will need either to handle the seating on event day or to issue a new ticket (that will invalidate the initial one) once the seating applied.

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.

Questionnaire: it makes the event available for questionnaire

Include in shipment fee: for cases where shipment fees where set to be Per ticket, you can choose if the tickets of the competition you are creating will be applied 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.