Prerequisite: create a Season, at least one Tariff one Tariff, a price level for membership
A membership is a nominative product, therefore it requires a contact to be bought.
It can be a physical or virtual card allowing the
...
owners to be offered a privileged relationship, unlocking a set of benefits (free products, discounts, anticipated access, etc).
The membership process has 2 phases:
- Purchasing a membership card
- Use of the membership card and access to the specific conditions linked to it
- Create a new eventmembership: first basic settings
a) General: i. General
ii. Parameters
b) Quotas
c) Based price - Important settings
c)Activity Product profile
d) Payment methods - Advanced menus
e) Custom variablesGeneral: iii. Advanced
f) Sub-groupingsCustom variables
g) Charges table allocation
h) Transport stopsAccess control synchronization
i) Interface mappings
j) Ticket logos
k) Access control synchronization
Copy of Organisation | Catalog | Memberships
Price breakdown - Validation
- Filters and main screen buttons
1.Anchor CreateEvent CreateEvent
Create a new
| CreateEvent | |
| CreateEvent |
...
membership: first basic settings
Button 
allows to create a new event product 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 membership as it will appear in SECUTIX screen (backoffice)
External name (max 60 char.): name of your event membership as it will appear to your clients (online, documents, tickets)
Short public name (max 15 char.): name of your event 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 eventsmemberships, but possible for 1 rate table and 1 eventmembership)
Tax VAT:VAT rate that will be used for your eventmembership. 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 membership 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.
Product type: can be selected if configured here https://confluence.secutix.com/wiki/display/SSH/Organisation+%7C+Initialisation+%7C+Product+types
Ticket model:Ticket model that will be used for the event (applied for all the performances, if not overloaded at performance level)
membership. Even if modifiable, if not set before sales start, all tickets products 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 It is necessary to have a ticket model correctly set if the membership is supposed to be used online.
Producer / Promoter / Partner: useful when using the producer portal.
Additional producer contact (structure of type producer) can be linked to Logo: (max size 1 Mb) image that will be used to illustrate 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.
...
| title | Italian Certification | Specific behaviour |
|---|
...
- "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.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 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 eventmembership. To be used with care as it takes users out of the funnel.
Questionnaire:it makes the event membership available for questionnaireInclude 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 FeesRemark: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.
...
Available titling: if set on "yes" it will trigger this information on the the sales context (right click > details on the seat) and on the ticketshop.
The linked Logical Configuration must have the visibility level set on the seats before it is linked to the performance (see next paragraph).
Language: if not empty, the value will be shown in Sales context while mouse hovering over the performance
Minimum age: informative (internal)
...
Online self exchange: it allows self exchange on the ticketshop
...
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 / 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.
...
Validity rule:you can choose between the current season, a specific range of dates, or a predefined number of days/weeks/months/years after the purchase.
In the last scenario, you may decide to let the purchaser define the start validity date during the purchase.
Price level: an existing price level for membership must be selected. It will allow the membership owners to unlock specific tariffs (if any) linked to the same price level.
Quota:the maximum number of products you have available. Once saved, this parameter cannot be changed, however it will be possible to edit the quotas from the side menu "Quotas" (that will appear once saved and enter the configuration screen again).
Min and Max quantity for Member rate:it will define min and max number of tickets available to the owner at a member rate (price level), if any. It applies to events and matches.
Offer ticket charges on all purchases: it discounts the charges, if any.
Valid for partner organisations: it makes the membership valid for other organizations of the same institution, if set as partners here https://confluence.secutix.com/wiki/display/SSH/Institution+%7C+Initialisation+%7C+Organisations
Automatic renewal: it makes the product selectable for automatic renewal (batch required).
2. Anchor ImportantSettings ImportantSettings
Important settings
| ImportantSettings | |
| ImportantSettings |
Among the other menus be sure to define, or review, accordingly:
c) Product profile
This is where you associate the set of rules regarding the selling of your membership. Among the rules, it will determine tariffs, seat category and sales periods in which the event membership will be available per sales channels.
See: Organization | Catalog | Product 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.
...
3. Anchor Collateral Collateral
Advanced menus
| Collateral | |
| Collateral |
e) General / Advanced
Short public name (max 15 char.): name of your membership as it will appear online when accessed from a device with small resolution (smartphone...)
Audience type:usually kept on "All public". For organization handling specific products 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.
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
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
Remark:text field to insert comment. This will remain at back office level.
ef) 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.
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
kh) Access control synchronization
...
| Info | ||
|---|---|---|
| ||
Specific rules for charges and access control |
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) Price breakdown
This functionality enables you to define multiple price components (ticketing, promoter...) for prices defined previously.
Relevant information on the configuration can be found here and here for price breakdown bottom-up.
4. Anchor Validation Validation
Validation
| Validation | |
| Validation |
The validation step will make sure that you did not forget to set any mandatory information.After that the product becomes available for running.
...
5. Anchor FiltersButtons FiltersButtons
Filters and screen buttons
| FiltersButtons | |
| FiltersButtons |
Top page filters allow you to display the memberships by internal name and status.
...
Delete | Validate | Run | Suspend | Duplicate | Copy from Season | Bulk edit price | Bulk edit price for product | Print test ticket | Export to excel |
|---|---|---|---|---|---|---|---|---|---|
Delete the chosen product (only if in "Preparing" of "Validating" state"). | Validate the chosen product (only if in "Preparing" and all the mandatory fields are accordingly set). | Activate the product so it can follow rules set in linked Product Profile(s). | Stop (temporarily) the following of the rules set in the linked Product profile(s) for the given product. Used to perform a few changes while on sale. | Duplicate the selected product. | Copy a membership from another Season | Edit more tariffs' prices in the same time. It allows to select more lines/membership at once
| Like the previous one, you can edit more tariffs' prices in the same time, selecting by product. It does not allow to select more lines/membership at once | Print a sample ticket. | Export the screen table of events memberships as an excel file |
