Currently, the resale platform allows to resale tickets not belonging to a season ticket at the initial tariff. For tickets belonging to season tickets, you had the choice between keeping the initial tariff or forcing a given (generally occasional) tariff. A new mode, called seat release, provides more flexibility by allowing your customers to choose the tariff when buying tickets on the resale platform.
Solution
Solution overview
The resale platform provides you the choice between two modes:
- The ticket marketplace mode consists in putting a ticket to a marketplace. The tariff of the initial ticket can't be changed. Depending, on the set-up you've chosen, the reseller may define the resale price of his ticket within the defined margin. This mode matches the already existing behaviour
- The seat release mode consists in releasing a seat and let a new customer buy any ticket based on that seat. The internet user can choose the tariff when buying a ticket on the resale platform. The reseller can't choose the resale price. Because of this tariff change, the new ticket may be cheaper than the initial one (example: an adult has put a ticket on resale, and the new buyer is a student). You can avoid loss of revenue in such cases in two different ways:
- You don't allow that the new ticket to be cheaper than the initial one
- You let the reseller assume the potential loss
The current feature allowing to force the new tariff of a ticket initially belonging to a season ticket has been kept as is. For legacy reasons, it's related to the ticket marketplace mode.
Set-up the new seat release mode
The resale type to be used by the resale platform is defined in the menu Organisation context > Organisation characteristic > Parameters.
You choose first between the ticket marketplace and the seat release mode.
Ticket marketplace mode
As today, you can define the range of the price of the resold ticket as a min and max percentage of the initial price of the ticket.
You can also define if the tickets belonging to season tickets (aka subscriptions) keep their initial tariff or if the new ticket must get a defined tariff. The tariff itself is defined at event or competition level (i.e. the event or competition included in the season ticket).
As today, the reseller will get the price he has defined (or the initial ticket price if the minimum and maximum price are set to 100%), minus a potential refund fee. The new buyer will pay the price defined by the reseller (or the initial ticket price if the minimum and maximum price are set to 100%), plus a potential sales fee.
Seat resale mode
For each shipment mode, you can define for which product families it should be authorized.
For example, you could define that standard (postal) mail and registered email are only used for memberships (because single tickets are using electronic shipment modes and goods are shipped by some external shipping provider).
Set-up allowed shipment modes at product level
The set-up defined above can be overridden for a given product. For example, you've got one very expensive membership providing many privileges and you want to provide it only by registered mail.
Selection of shipment modes on Ticket Shop
Case 1: There exists one (or several) common shipment mode(s) allowed for all items of the cart
The Ticket Shop will only propose this (or these) common shipment mode(s).
This approach allows to minimise the number of shipments, thus reducing shipment costs and fees for you and your customers.
Case 2: There doesn't exist any common shipment mode for all items of the cart
The internet user will be invited to select one shipment mode for each item in the cart. When the page is displayed, the list of shipment modes available for the first item is expanded while the list for the other ones are closed. The internet user may at each moment view or hide the details of the shipment modes available for one product.
The file detail displays the different shipments created:
Getting started
Create a ticket to our service team to enable the feature. The service team will:
- Set the feature flag SHIPMENT_MODE_PER_PRODUCT
Current restrictions
Scenario | Status |
Ticket Shop | |
Direct sale on Ticket Shop (no creation of options or reservations) | Shipment mode set-up per product is taken into account Internet user may select multiple shipment modes if needed The file detail mentions all the shipments with their respective cost but doesn’t mention which products belong to which shipment → not a big issue |
Online exchange | OK (same as above) |
Reservation on Ticket Shop | Shipment mode set-up per product is ignored → a reservation order may be created with a reference shipment which shipment mode is inconsistent with the shipment mode set-up per product |
Ticket Shop sale converted to reservation:
| High risk of technical error if the sales order has multiple shipments → currently, shipment mode per product isn’t compatible with order amount limit or prepayment |
Pay online a reservation order created on-line | The reference shipment (which shipment mode may be inconsistent with the shipment mode set-up per product) is ignored, allowing the internet user to use the new feature → Only consequence:
|
Box Office | |
Reservation and sales | The behaviour is the same for reservation and sales orders: the shipment mode per product set-up is taken into account but the order may contain only one shipment. The operator needs to split the order if there is no shipment mode common to the whole order. |
Payment of a reservation performed on BO | No problem since reservation and sales handle the shipments in the same way. |
Hybrid scenarios | |
Payment of an online reservation at the Box Office | Because the online reservation doesn’t take into account the shipment mode set-up per product, the BO operator may need to split the order, i.e. create 2 sales orders for one reservation order. |
Payment of a BO reservation online | No problem |
| Fixed price season tickets | No shipment mode can be selected if the season ticket is defined as "ticket only" and no performance has been selected yet. |
