Page Comparison

...

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.

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.

             b) General / Parameter

               Complement name (max 60 char.): text that will appear online between the name and the description.

Internal description: text field that can be used to insert particular comments that will remain on back office side.

...

Language: if not empty, the value will be shown in Sales context while mouse hovering over the performance 

Minimum age: informative (internal)

Waiting list allowed:for cases where events are sold out, and if the waiting list is activated, web users will have the ability to enter their email and declare their interest in buying tickets

...

Kind:as the rate type, the kind can be used to categorize matches. The kind is displayed on the match page of the ticketshop. In the example, Default is the match kind. The list of Kind can be modified from Institution | Initialization | List of values under the entity Performance

...

    3.

Anchor
ImportantSettings ImportantSettings

Important settings

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

               c) Activity profile              

This is where you associate the set of rules regarding the selling of your performances. Among the rules, it will determine tariffs, seat category and sales periods in which the event will be available per sales channels.
See: Organization | Catalog | Activity Profile

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

   4.

Anchor
Collateral Collateral

Advanced menus

               e) 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)

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.

               f)  Sub-groupings

                Sub-groupings are to be defined in Organization | Initialization | Sub-topics.
                At this stage, you can associate a sub-grouping to your events. This sub-grouping can then be used through APIs to group product together for example.

               g) Charges table allocation

When using Charges (fees that apply per ticket), you can associate there your existing charge table. You will first need to specify for which rate type it will apply (only used rate type will appear in the dropdown), then select your charge table.
Finally, you can specify on which sales channels those charges will be active. 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

              h) 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)  Interface mappings

You can set in this screen your mappings regarding the competition you are creating for the different interfaces and batches you may have. Note : those mappings will only apply at competition level, not matches.
You can also set mappings directly in the related interface. See: Organization | Tools

               j)  Ticket logos

               Tickets logos have to be uploaded in Organization | Initialization | Ticket logos. Mainly for sport customers

There you can associate the ticket logos you have created to the competition you are creating. Those logos can appear on the ticket templates, as you can set up to 10 fields using those extra logos.
This menu is usually used to insert partners / sponsors logos when those can change from one competition to another.

This menu can be seen as visual comfort variables as ticket logos just have to be images. What is in the image itself depends on your imagination.This menu can be hidden directly from operators rights if need be.

               k) Access control synchronization

                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 of the competition and its matches, that will become available for Running. The following message will be displayed:

Validation is required every time other performances are added afterward.

   6.  

Anchor
FiltersButtons FiltersButtons

Filters and screen buttons

...

Delete	Validate	Run	Suspend	Cancel	Close	Duplicate	Copy from Season	Performances	Print test ticket	Export to excel
Delete the chosen event (only if in "Preparing" of "Validating" state")	Validate the chosen event (only if in "Preparing" and all the mandatory fields are accordingly set). It works as the validation function included on the Event creation screen (point 6)	Activate the event so it can follow rules set in Activity Profile.	Stop (temporarily) the following of the rules set in the linked Activity profile(s) for the given event. Used to perform a few changes while on sale	Cancel the event (this does not perform any refund).	Close the event (i.e. figures are locked, and it is no longer possible to perform actions like sales, exchange/cancellation, cancel reservation, duplicate or reprint) When Season Tickets contain all the events, closing one will usually result in the inability to reprint the season ticket itself.	Duplicate the selected event (including calendar)	Copy an event from another Season	A shortcut to the performances screen. It will directly show only the performances related to the chosen event.	Print a sample ticket.	Export the screen table of events as an excel file