Pre-requisite: create Activities, Teams, Competition types, Logical Configuration, Rates Table, Sales Calendar
Aim: create and manage your services. Services are optional extras (concert programs, audio guides, books, DVDs, parking, snacks, etc.) or everything an audience may need apart from the ticket itself. In SecuTix, it is the most basic product, it is neither dated nor inventory controlled.
Services are also used in museums to configure counter products to count the visitors allowed to access the museum without a barcode (ticket, membership card...). For example: teachers can access the museum with a specific pass delivered by the ministry of education. In this case, a service will be used with a specific rule to allow to scan the same barcode at the entry, just to count teachers entering the museum. this feature is described below in Synchronisation
A service may regroup several items. For example : a "tshirt" service may have one item per size (small, medium, large...) or a guide book may have one item per language (English, French...).
Screen overview:
1- Title: click on the star to add this screen to your dashboard.
2- Filters: enables you to filter the list of services below to make it easier to find a specific service.
3- Action buttons: each one is discribed below.
4- List of services: the list can be sorted by clicking on the header of a colum. You can also change the order of the columns by clicking a header and dragging it to the desired position.
5- Summary: indicates the number of services displayed in the list taking account of the filters.
Action buttons:
The following buttons perform actions at Service level, i.e. for all the items included.
New
| Delete
| Validate
| Run
| Suspend
| Duplicate
| Copy from season or activity
| Print test ticket
| Export to Excel
|
|---|---|---|---|---|---|---|---|---|
| Delete an existing service (only possible for status Preparing or Validated). You must delete services one by one. | Validate a service (only for status Preparing). You must validate services one by one. | Activate the service so it can follow rules set in Product Profiles. You can activate several services simultaneously. | Stop (temporarily) the sales for all items of the selected service independently of Product profiles or quotas. Service must be suspended before any modification regarding VAT rate, alert threshold, product tyoe, audience type or ticket model or if you want to add items. | Duplicate (=copy/paste) the selected service and its items. | Enable to select services from another season to duplicate them in the current season. | If the selected service ha a ticket model, print a test ticket. A new window will open to ask you for a variable set. | Export the list of all the services to an excel file |
Create a new service
When creating a new service, you will have to go through the following menus (click on the menu you wish to get there directly) :
1) General
2) Items
8) Access control - Synchronisation
10) Payment methods
12) Validation
1) General
a) General | General
The general tab is the same as every product in SEcuTix :
Internal name (max 60 charac) : name of your service as it will appear in SecuTix screen (backoffice) and in the reports
External name (max 60 charac) : name of your service as it will appear to your public (online, tickets and documents)
Short public name (max 15 charac) : name of your service as it will appear online when accessed from a device with small resolution (smartphone...). It can also be used in ticket editor (espacially on the stub for thermal tickets) and in reports.
Public Description : description you can set for your service that will appear online. Lots of 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 charac) : code of the service. This code must be unique per entity (ex : not possible to have the same code for two services, but possible to have the same code for 1 tariff and 1 service). It can be used in ticket editor (espacially on the stub for thermal tickets) and in reports.
Tax VAT : VAT rate that will apply to your service (all items will have the same). To be selected among the dropdown elements. VAT rates are defined in Institution | Initialisation | VAT Rates.
Alert threshold : if the available quota left for one item of this service reaches this threshold, this will display the Quota Alert message in the back office.
Product type : Product type enables the system to classify the different ticketing products. Products sold at the box office are automatically classified by product type. Product type can also be used in reports filters. Product type are defined in Organisation | Initialisation | Product types
Audience type : Audience type is mainly used to target your audience in SecuTix Audience Management. Audience types are defined in Institution | Initialisation | List of values
Ticket model : Ticket model is not mandatory for a service and will be used for all the items of the service. When bought online, the ticket may be used as a voucher to pick up the product on site. Ticket models are defined in Organisation | Tools | Ticket models
Producer / Promoter / Partner : useful when using the producer portal. Producer contact (structure of type producer) that 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) that 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. Producer contact that 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 defined even if the producer has been set.
Merchant Id : in case of split payment, 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.
Logo : (max size 1 Mo) image that will be used online 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
Internet description URL : link to an external page that will appear online 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 service. To be used with care as it takes users out of the funnel.
Questionnaire : to gather more information about your customers, you have the possibility to define a series of questions that will be asked to each beneficary of the service at the end of its order.For further details, read the dedicated guide : How do I create questionnaires?
Include in shipment fee : for cases where shipment fees where set to be Per ticket, you can choose if the items of the service 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 Organisation | Initialisation | Shipment Fees
Remark : text field to insert comment to the service. This will remain at back office level.
b) General | Parameter
Type: not editable. Always "simple" for a service.
Kind: enables you to have a specific classification for services. The kinf is not visible in sales/reservation, nor only, nor in reports, it is only available through the API. Service kinds are defined in Institution | Initialisation | List of values
Internet text: further description that appears online below the public description.
2) Items
Once the service is running, you will need to suspend it in order to be able to modify existing items or add a new one. Deleting an item is only allowed when the service is in preparation or validated.
An item is simply defined by :
- A rank (integer) to set in which order the items will appear within the service on sales screen and online.
- An internal name (max 60 charac) : name of your item as it will appear in SecuTix screen (backoffice) and in the reports.
- An external name (max 60 charac) : name of your item as it will appear to your public (online, tickets and documents).
- A code (max 8 charac) : code of the item. This code must be unique per service (two items in different services may have the same code).
- A quota: the initial quantity of this item that can be sold.
If you add an item to an existing service, you don't need to revalidate the service so that the new item can be sold, you just need to run the service (since you needed to suspend it to add the item).
3) Sub-Groupings
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.
4) Custom variables
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.
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.
5) Transport Stops
Transport stops are for customers selling combined offers including leisure and public transportation. They may define which stations or stops belonging to a public transportation network allow to reach the product associated.
6) Quotas
This form shows you the quota for each item (which is the total quantity of an item that you put on sales), the alert threshold defined at the service level and the available quantity remaining (equal to total quota - sales - reservations).
When you see an alert quota message in the list of services, it means that at least one item availability is under the alert threshold in the service.
The correspondinq availability will then appear on a red background in this screen :
You can modify this quota at anytime by clicking 
on the line of the corresponding item. The following popup will open :
You can then change the total quota of the item. In the exemple above, the total quota is 500. 350 have been sold or reserved. Availability is then 150.
Since you can change only the total quota, if you want availability to 400, you will have to put 750 in the quota box (you want 400 available, 150 are already available from the initial 500, so you need a total quota of 400 - 150 + 500 = 750).
To make sure that you put the right value, just click anywhere in this popup outside of the box and the availability will be refresh.
7) Basic price
Services are not linked to a rate table. This basic price screen is used to set the price of your items.
By default, when you create an item, the price table isn't displayed. You first have to chose the items and the tariffs you want to define and click 
When you open a running item, the screen displays by default the existing prices.
In the example above, a new item "Turandot program" was added to the service but no price is yet defined for this item. So when you come to this basic price screen, you can see that the item is not selected in the first filter. You then need to drop it to the right box and click
It will add a column in the table below where you put the price :
Once you filled the price, do not forget to save 
8) Synchronisation
Since a service doesn't grant access to an event, a match or a visit, it should not be controlled.
But there are some cases where you may wish to control service tickets and therefore synchronise SecuTix Access Control. :
- You issue a ticket for a specific service as a voucher which will be exchanged for another good (a guide book, a snack...) and you don't want it to be reused or you want to know how many have really be used.
- You will use this service as a counter product. If you need several counters, create a service for each with a single item since statistics are per service, not per item.
The following requirements must be met before :
- the season of your product must already exist in the Access Control, see
- you need an Access Control calendar, see Organisation | Access Control | Calendars
- you need at least on sector, see Organisation | Access Control | Sectors
- you have a device attached to this sector to control the barcodes.
In the case of a counter product, the configuration is quite simple :
- Choose a calendar
- Set "Is counter" to "Yes"
- Check "Enable" box
- Add the sectors where you want to count
In this peculiar case, other rules validity are ignored (nb of days of validity, duration, nb of access, delay of invalidity...).
Here is an example :
9) Product profiles
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
10) 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 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.
11) Interface mappings
You can set in this screen your mappings regarding the service you are creating for the different interfaces and batches you may have. Note : those mappings will only apply at service level, not items.
You can also set mappings directly in the related interface. See : Organisation | Tools
12) 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.
Next Step: don't forget to manage the sales of this services and make sure some quota is always available.