Page Comparison

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

Aim: create and manage your events

...

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

...

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.

...

Logo 1:(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

Audience type:usually kept on "All public". For organization handling specific events for Kids, setting Kid in there will trigger the indicator Children Product, allowing you to easily target purchaser of those products.
See: Standard indicators. Otherwise this information can also be used through the API to group products together for example.

Time tolerance:in hours and minutes, this field allows you to set the amount of time FROM the beginning of the performance until which you will still be able to sell ticket.
For example, a time tolerance set as 00:45 will result in having the match event still available for sale up to 45 minutes after performance start.

...

Tariff at which tickets belonging to a season ticket are resold on resale platform:when using SECUTIX resale platform, you can set that the resale of any tickets coming from the season ticket related to this competition will be resold at a particular tariff. The benefit there is usually to make sure that anyone coming on the resale platform can purchase any tickets available. And not have a scenario where a ticket coming from a child season ticket can only be purchased by a child. The reseller will only be refunded of the amount of his ticket within his season ticket, and the delta between this price and the price paid by the purchaser will be kept by you. This field will be active with a tariff drop-down only if you set the parameter Tarriff modified for subscriptions on yes in the Organization | Initialization | Sales Channels (| Points of sales | Internet parameter)where the point of sales is the one used for your resale platform.

...

1st catalogue number of performances: the use case is mostly for Live Events. This feature allows you to setup the number you want to apply for your matches events / performances. In France the VAT rate must change from the 141st performance.
Thus this field allows to easily identify from when the VAT rate should be set differently.

Confirmation after reservation (days): when using reservations, this field give you the opportunity to have a deadline automatically set by SECUTIX, calculated in days after the reservation is created in the system.
Note: the reservation will not automatically be cancelled once this date reached.

Confirmation before performance (days):when using reservations, this field give you the opportunity to have a deadline automatically set by SECUTIX, calculated in days before the first match event included in the reservation.
Note: the reservation will not automatically be cancelled once this date reached.

...

Add: this button is for mass creating schedule, mostly for cases where a same event occurs several times a day during lots of days. Probably not used much in a context of creating competition with matches.

Rate type:the rate type allows you to categorize your events. You will later be able to apply Charges for a rate type, meaning for all events sharing the same rate type.
This information can be used through APIs to group performances for example.

Site:site in which your performances will take place. This will determine the space and the logical configuration that will be available in the following menu. See Institution | Venue | Site

Space:space in which your performances will take place. This will determine the logical configuration that will be available in the following menu. See Institution | Venue | Space

Logical configuration:logical configuration that will be applied to the performances you are creating. See Organization | Venue | Logical Configurations

Remark: text field that will remain at back office level.

...

Duration : expected duration of the matchevent. This information can be used in ticket template and through the APIs. Mostly used in Live Events.
It's also shown on Sales context when mouse hovering over a performance:

...

Kind:as the rate type, the kind can be used to categorize matchesevents. The kind is displayed on the match event 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

Number of breaks:number of breaks your matches event will have. Mostly used in Live Events.

Exchangeable ticket: determine whether or not a ticket can be exchanged. If set on No, you will not be able to perform any Exchange/Cancellation on ticket for your matchesevents.

Named ticket:there you can chose to force people to enter a beneficiary for every single ticket that will be generated (eticket, thermal ticket...). If set on No, it will be up to the user to add it or not, and ticket could be printed with no beneficiary set up.

Licence number:you can overload the licence number to apply it on the matches events your creating. Mostly used in Live Events.

Logo:you can overload competition logo with a logo set at match event level. When used, it is the image displayed on the ticketshop for the related match(es)events.

VAT:you can overload the vat to apply it on the matches events your creating. Mostly used in Live Events.

...

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.

...

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

...

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

...

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 matchesperformances, that will become available for Running. The following message will be displayed:

...