Page Comparison

...

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

Image Removed

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

Image Added

General tab

Set an internal name (60 characters max.) and a code (8 characters max.) to your mapping table.

Image Added

Seat categories tab

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?"
Image Removed

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 :

Image Removedyou 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

You will need to declare which categories are allowed in each concert hall when someone buy a season ticket in Category 1.

Click on Image Added :

Image Added

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):

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 When you set up a new package or a season ticket, to make sure we you associate this the mapping table :

Image Removed

Et voilà!Image Added