...
Aim: create tables to group logical seat categories from different logical configurations (most of the time, from different venues) in categories that will be used in composed products (packages or season tickets).
Description:
In the live events environment (mostly), you may have composed product / season tickets that could give access to venue with different logical configuration, and potentially different logical seat categories.
SecuTix handle this point through Mapping table.
Once you've setup the different logical configurations you want to map, go to Venue -> Mapping Table
Clic on new. Set a name From this screen, you can either :
- Create a new mapping table
- Delete an existing mapping table
- Duplicate a mapping table
General tab
Set an internal name (60 characters max.) and a code (8 characters max.) to your mapping table.
Then the idea is to define "I've got a physical category 1. If i'm in an event in my logical conf A, what should it correspond to? in my logical conf B?"
Seat categories tab
For each given physical seat category that is used in a logical configuration "A", you could define what is the corresponding seat category in a logical configuration "B".
Let's take an example :
- logical conf A : 4 logical categories : Cat 1, Cat 2, Cat 3, Cat 4
- logical conf B : 1 unique category : B
If i'm to take a season ticket encompassing events in both venues, i can take a season ticket in cat 1 that will give me cat 1 for event in A, and Cat B for event in B.
So i need to set this like this :
Then i need to apply the same method for each different category until i've mapped all the needed category :
Next Step: The very last is, when setupping the season ticket, to make sure we associate this mapping table :
Et voilà!: you want to sell a season ticket with events happening in 2 concert halls :
- "Large room" with 6 categories, labelled Cat 1 to Cat 6
- "Medium room" with only 3 categories, labelled Cat 1 to Cat 3
For each category in the season ticket, you have to declare which categories are allowed in each concert hall.
In our example, we want the following:
| Season ticket category | Seat category in Large room | SEat category in Medium room |
|---|---|---|
| Category 1 | Cat 1 | Cat 1 |
| Category 2 | Cat 2 | Cat 2 |
| Category 3 | Cat 3 | Cat 3 |
| Category 4 | Cat 4 | Cat 3 |
| Category 5 | Cat 5 | Cat 3 |
| Category 6 | Cat 6 | Cat 3 |
In order to create season ticket category 4, click on 
:
And fill the following:
Seat category is the mapped category that will be used in the composed product.
Internal name (max 60 char) : name of the mapped category that will appear in SecuTix screen (backoffice, reports...)
External name (max 60 char) : name of the mapped category that will appear to your public (online, on tickets and documents)
Code (max 8 char) : code of the mapped category. This code must be unique per mapping table
Seat category (logial): select (drop to the left frame) the categories from the different logical configuration that you want to group in the mapped category.
In the screen shot above, Cat 4 of the season ticket will grant access to seats in Cat 4 in the Large room and in Cat 3 in the Medium room
Then you need to repeat the same method for each different category to be sold in the composed product.
Next Step: When you set up a new package or a season ticket, make sure you associate the mapping table :
