Copy of Organisation | Catalog | Memberships

Prerequisite: create a Season, at least one Tariff

A membership can be a physical or virtual card allowing the owner to be offered a privileged relationship, unlocking a set of benefits (free products, discounts, anticipated access, etc).

The membership process has 2 phases:

1. Purchasing a membership card
2. Use of the membership card and access to the specific conditions linked to it

1. Create a new event: first basic settings
   a) General:  i. General
                      ii. Parameters
   
   
   
   
2. Important settings
   c) Activity profile
   d) Payment methods
   
   
3. Advanced menus
   e) Custom variables
   f)  Sub-groupings
   g) Charges table allocation
   h) Transport stops
   i)  Interface mappings
   j)  Ticket logos
   k) Access control synchronization
   
   
4. Copy of Organisation | Catalog | Memberships
   
   
5. Filters and main screen buttons
   

     1. Create a new event: first basic settings

         Button allows to create a new event 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 as it will appear in SECUTIX screen (backoffice)

External name (max 60 char.): name of your event 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 events, but possible for 1 rate table and 1 event)

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.

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.

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 still available for sale up to 45 minutes after performance start.

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)

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

Online self exchange: it allows self exchange on the ticketshop

Season ticket authorized: to specify if the event is valid for a season ticket product (the event needs then to be selected during the configuration of at the season ticket level)

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.

Countermark accepted: the feature related to this field is not active anymore.

Ticket producer: this field tells SECUTIX whether or not a ticket has already been produced. If set on YES, then SECUTIX will NOT generate any ticket at the moment of the sale. The use case is when you handle event for third parties, and you have been given directly (thermal) tickets from this 3rd party. You can still set these events in SECUTIX and sell them from SECUTIX to keep track and be able to report, but the ticket itself will not be a ticket generated from SECUTIX. You will have to handle/send the tickets you received out of SECUTIX.

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.

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 included in the reservation. Note: the reservation will not automatically be cancelled once this date reached.

    3. Important settings

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

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

              
               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

      
               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.

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.

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

   6.   Filters and screen buttons

Top page filters allow you to display the memberships by internal name and status.

The other screen buttons perform the following actions: