...
Info | ||
---|---|---|
| ||
|
Solution
Solution principle
Basically, the The experience vouchers involve following steps:
...
- 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
...
products
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:
...
After having selected one of the vouchers available, the list of available events and performances the voucher may be exchanged with is displayed:
The list displays performances ordered by event and date (if multiple performances inside the same event).
Depending on the set-up, the list of performances available for a given voucher may be very long. You can enable a two-level display (the internet user selects first an event, then a performance) to shorten the list
By default, the performances belonging to events having less than three (redeemable) performances can be selected directly (in the example above: performance Cinderella of 18th of June 2024). If the event contains 3 performances or more, it's displayed in a compact way (in the example above: Swan lake). The internet user may expand the event to see all the available performances by clicking on the arrow:
At any moment, the internet user may dismiss the detailed list of performances by clicking on the up arrow.
The number of performances per event under which events are expanded automatically may be configured. For example, if you want this page to display directly all the performances without the need to expand the events (not recommended because you may end up with a very long list), you would set a very high value. See the Getting started section for more detail.
...
The configuration key config.gravity.RedemptionProducts.groupTriggerQuantity defines the number of performances per event from which the two level display is enabled (select first event then expand the event to select a performance). For instance, if config.gravity.RedemptionProducts.groupTriggerQuantity is set to 3, the internet user will select first an event, then a performance if there are events having 3 or more performances available for the same eventwill be displayed in a compact way.