Page Comparison

...

Sub-groupings are to be defined in Organisation | Initialisation | Sub-topics. At this stage, you can associate a sub-grouping to your service. This sub-grouping can then be used through APIs to group product together for example. It also groups your services in the sales-reservation screen.

...

Custom variables are to be created in Organisation | Initialisation | 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 Texte_Libre in the ticket editor. See List of variables in the Ticket model editor

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.

...

Obviously this screen is useful only if you have already sync your season with the Access Control, but created the product afterwards.

Décrire le fonctionnement des produits de comptage - alerter sur le fait de ne pas les mettre en vente, juste une fois pour générer un code barre

This is where you associate the set of rules regarding the selling of your service. Among the rules, the sales channels on which the service will be available.

See : Organisation | Catalog | Product Profile

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 authorised in your Payment Methods (see : Institution | Initialisation | Payment Methods) and Product Payment Methods.

Thus, if you associate no payment methods in this screen, SecuTix will check which Payment Methods are authorised for the Product Family. 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 it will not be allowed for any product. Also keep in mind that if you allow a payment method only to one Product Family or on specific Product, it will not be available to someone buy other products at the same time.

For example: if you want to allow Slimpay payment only for season tickets, you need to associate this payment method to your point of sales AND associate only the season ticket family in Slimpay payment method. But in that case, if your client add a single ticket for a friend in his cart, Slimpay will not be proposed as a payment method.

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 : Organisation | Tools

...