S-360 already provides the possibility to buy financial vouchers and give them to some friend or family member. S-360 now manages experience vouchers that can be directly redeemed with a ticketing product (for the moment: only events) without any payment process, thus providing a user experience better suited to a gifting process.

Solution

Solution principle

Basically, the experience vouchers involve following steps:

• Configure the experience voucher, in particular define the products the voucher may be redeemed (or exchanged) with
• A first contact purchases the voucher (currently, only possible on the box office)
• The voucher purchaser gives the voucher to a second contact, called the voucher holder or beneficiary
• The voucher holder redeems the voucher online with one of the products defined during set-up

Set-up of the experience voucher

Define the VAT perception policy

Before defining the experience voucher, you have to decide at which time the VAT will be computed, because this will have an impact on the voucher set-up. S-360 lets you the choice between

• VAT perception at voucher sale: a directive in the European Union obliges to use this option if all information to perceive the VAT are already known at this stage (for example, same VAT rate for all the products that can be exchanged with the voucher)
• VAT perception at voucher redemption: in the European Union, this option can only be used if VAT cannot be perceived at the time of voucher sale

Set-up the open product(s)

You have to create an open product that will be used automatically by S-360 during the redemption process in order to ensure accounting consistency. More precisely, you have to create one open product for each VAT code of experience voucher. This needs to be done only once per season. Provide following information during set-up:

• A meaningful name (for example: for experience voucher with 10% VAT) in order to ease the later set-up of the experience voucher
• The VAT code that you plan to use for your experience vouchers. If you perceive VAT at voucher sale, select a VAT code matching a non zero VAT rate. If you perceive the VAT at voucher redemption, select the VAT code matching a zero VAT rate.
• Create one item with a very large quota
• A dummy price for each tariff that will be used by the experience vouchers and the products that can be received by redeeming these vouchers. Only the tariff matters, not the price. In case of doubt, you can define prices for tariffs you aren't sure they will be used.The open product doesn't need to be added to the product profile (and shouldn't be added to prevent it from being displayed on the Ticket Shop catalog)

Set-up the experience voucher

The experience voucher is a new product family displayed in the other products section. The current voucher product family as been renamed as financial voucher to avoid any confusion.

Following parameters are specific to the experience voucher:

The section Experience voucher parameters allows you to define an expiry date for the voucher itself. You can define an absolute date or a number of date from the date of purchase. The experience voucher can't be redeemed anymore once the expiry date has been reached.

A redemption period can be defined in the section Redemption parameters. This period may depend on the selected performance date. For example,an experience voucher could be redeemed against a given performance between 30 days (start) and 2 days (end) before the performance takes place. Of course, in order to redeem the voucher, the expiry date must not have been reached.

The operator must select the open product that will be used automatically by S-360 during the redemption process. The drop-down only displays running products belonging to the same season and having the same VAT code. The open product must not match a gift aid or the cancellation insurance (these are discarded automatically from the drop down list)..

The screen below allows to list all the events that can be obtained by redeeming the current voucher:

By clicking on the New button, one or more events may be added to the list:

The list may be filtered by name as in the example above. If you perceive VAT at voucher sale time, the product must have the same VAT code as the voucher. If you perceive VAT at voucher redemption time, the product may have any VAT code. The list is filtered accordingly. Note that you may add products belonging to another season.

After having clicked on Add, the event (with all its performances) is added to the list of products that can be acquired with the concerned voucher. If you want to limit the redemption possibility to a subset of performances, you have to double click on the line. The following screen is displayed:

.

The list of performances will also be filtered according to the VAT code (if the performance has a VAT code different from the event it belongs to).

The experience voucher will be bought for a given seat category and tariff. Seat categories are defined at item level, as illustrated below:

The number of vouchers available for each seat category is defined in the quota screen (similar to other product families)

The prices must be defined for each seat category (matching an item) and tariff:

The amounts of the experience voucher and the event that may be acquired with the voucher don't need to match (see the section about the redemption process for more detail). However, the tariff and seat category have to match.

When creating a new season ticket, the operator will have to choose its type:

The types Calculated price and Predefined price already exist. The new type Fixed seat season ticket that matches this new season ticket is basically a Calculated price season ticket that includes the fixed seat logic described in this page.

The season ticket type of an existing season ticket is recalled at the top of the Parameters tab:

The fixed seat season ticket can only be defined as a season ticket without (fixed) seat category. This means that the operator will define a global quota for a given fixed seat season ticket and not a specific quota for each seat category. The reason for that is that a given seat (selected by an end customer for the whole season ticket) may have a different seat category for different performances if these performances use different logical configurations. The price paid by the end customer takes the actual seat category into account.

Sales at box office

The sales process is basically the same as for a calculated price season ticket. After having selected the product, the operator selects (as usually) the seat category, contingent, tariff and quantity. The only difference is that the seat category will apply on the first performance of the season ticket, as illustrated below.

In the second step, the operator selects, as usually, the performances to be purchased inside the season ticket. 

The 3 first events use 3 different logical configurations belonging to the same physical configuration (and same space). The last event takes place in a different space, implying a different physical configuration.

S-360 displays a grouped map displaying the seats that are available for both 3 events sharing the same physical configuration. By clicking on the information icon, the operator can see for which performances he's selecting a seat and on which performance the displayed seat map is based. For instance, the seat map above is based on Mozart concert of 29.11.2025 and S-360 will automatically select a seat that is in the selected seat category (in this example, seat category 2) for the Mozart concert. The selected seat (seat 135 of row AA) could be in another seat category for one of the other performances (in this example, Bach concerts).

Finally, the operator selects a seat for the last performance taking place in another space.

The operator may override the behaviour above and select the seats separately for each performance by selecting the map by map option as illustrated below:

However, SecuTix doesn't recommend this option since it breaks the fixed seat logic. Indeed, the box office will automatically switch to this logic if no seat is available for all the performances sharing the same physical configuration.

The seat map will select by default:

• The preferred seat of the selected contact(s) if the information is available
• Otherwise, the best seat (i.e. the seat returned by the best seat selection feature)

Preferred seat

After the purchase process, the selected seats are stored as preferred seats. For a given contact, there may be one preferred seat per physical configuration. If a preferred seat already exists for the given contact and physical configuration, it will be overridden by the newly selected seat. Preferred seats may be viewed in the Contact module with the new menu entry Preferred seats. The operator may delete a preferred seat, this action having no impact on the purchased tickets. Preferred seats are only stored during a purchase process. They can't be defined directly from the screen below.

If multiple season tickets are purchased at the same time, the preferred seats will be stored for each cultural contact specified.

Preferred seats will be used during the purchase of another fixed seat season ticket using the same physical configuration(s) and during season ticket renewal. 

Preferred seat information that isn't valid anymore (because of major changes brought to the physical configuration) are simply ignored.

Fixed seat season ticket renewal

Summary

The renewal batch selects the seat according to following decreasing priority:

• Reuse as is the seat used in the origin season ticket if both origin and target season ticket use the same physical configuration. Raise an error if the seat isn't available anymore or has another seat category
• In the new physical configuration, search for a seat with same area, row and seat number as in the origin season ticket
• If it doesn't exist or isn't available, define if a preferred seat has been defined for the new physical configuration
• If no preferred seat has been defined or if it isn't available, use the best seat allocation

Detail

The table below describes the behaviour in detail by listing all possible cases. Here are some explanations on the main columns of the table:

• Found seat in new physical configuration with same area, row, seat number: the batch searches for the seat (defined by its area, row and number) that is he most used in the origin season ticket and looks if this seat exists in the physical configuration of the target season ticket. It considers also the seat category of that seat.
• Identified seat based on preferred seat: for a given physical configuration used in the target season ticket, the batch checks if there exists a preferred seat
• Identified seat based on best seat allocation in same seat category: the batch uses the same seat selection logic as in the sales at box office described above. It uses the seat category of the origin season ticket as defined in the first bullet point above.

The batch will proceed in two different steps:

1. It will first renew all season tickets that can reuse the same seat (same physical configuration or other configuration containing a seat with the same area, row and seat number).
2. In a second step, all renewals requiring a seat change will be performed

The goal is to avoid following scenario:

• A first season ticket uses seat A that has been marked as invalid. The batch allocates seat B
• A second season ticket uses seat B that has been allocated in the mean time for the first season ticket. As a result, seat C is allocated to this season ticket
• A third season ticket uses seat C...

By default, the batch will perform both steps mentioned above. You may change this behavior by adding the custom parameter renewStrategy. This parameter may have 3 values:

• BOTH: performs steps 1 and 2
• NOT_PROCESSED_SSTK: the batch performs only step 1 and stores the season ticket requiring a different seat in a temporary table
• PROCESSED_ERROR_SSTK: the batch performs only step 2 based on the content of this temporary table

However, SecuTix recommends to keep the default behaviour unless you need to handle very specific cases.

This parameter only impacts the renewal of fixed seat season ticket.

Other new parameters

The renewal batch may be run in reservation only mode. More precisely, the Create reservation field proposes following values:

• Always: a reservation is systematically created (no sales order)
• Never: a reservation is never created. In other words, the batch tries systematically to create a sales order and, in case of payment failure or shipment information missing, no order is created at all
• If payment fails: the batch tries to create a sales order and creates a reservation if payment fails or shipment information is missing

Current restrictions

Getting started

You don't have anything to do to benefit from the fixed seat season ticket. It's directly available.