Ticketing methods in the shop

Ticket security

The ticket numbers are unique per brand owner or head office. However, this also means that individual tickets could possibly (statistically very unlikely) be processed on another Hypersoft system. However, if you design your tickets uniquely in some other way besides the code, confusion should be impossible. As a rule, unique numbers within your brand and a comprehensible design language should be sufficient for clear recognition.

(For increased security needs on this topic, please contact Hypersoft).

Variant ticket sales with simple validity

Ticket history with simple validity is already possible via the webshop. The tickets are created in the item master like other webshop items and contain the validity in the item name. Example:

New Year's Eve 2021/2022 31.12.2021

These items must be assigned to a merchandise group in the item master (for the evaluations) and to a merchandise group in the webshop (for the grouping there). The desired assortment must also be set.

The items appear in the desired product group in the shop, (e.g. Events). The validity is indicated by the item name, so that you can also set up a suitable item for each Saturday weeks in advance.

Availability of the number of tickets...

An availability can be stored for each ticket item, which is checked by the shop. Here you can define how many tickets you want to sell with this item. For this purpose, all functions of the item availability in the webshop also apply to these ticket items. This way you can simply limit the number of people by the maximum number of tickets available. Afterwards, the tickets are displayed in such a waythat one remains informed about the general offer, but the item can no longer be placed in the shopping cart.

Item availability can also be controlled from the POS system. The sale of tickets at the POS in the "function of a box office" is possible, but does not produce compatible tickets at the POS (if necessary, items are printed on forms and order receipts, depending on the type of printer).

Sending the tickets by mail...

As soon as a ticket item is sold via the webshop, the portal notices that it is a ticket and sends one or more tickets to the orderer by email. The mail can be configured accordingly for this purpose .

For the delivery of tickets, the user's e-mail address must be set up as a mandatory field in the customer data.

Check tickets at the location

When redeeming the ticket, the POS system can only determine the simple validity of the ticket and validate it, so that no further validity can be determined with the code. The workflow at the POS is similar to that of the location tickets as described at Ticket control in cashier mode (but without birthday notice, customer pictures and re-entry functions).

The simple examination with these restrictions is also possible at Old Mobile Entry 1. An extension of the programme to make it compatible with current mobile hardware will follow shortly.

In fact, however, you must bear in mind that a ticket item with the name New Year's Eve 31.12.2021 can be accepted and validated as valid only once, but on any date. A corresponding imprint on the ticket with a visual check by employees complements the corresponding security of the workflow.

Variant ticket sales with complex validity

This topic concerns project work that is subject to planning.

The Hypersoft // system is a standard programme that can be used in many different configurations. The correct application of the topics described here requires expert knowledge and an alignment of expectations, and not all Hypersoft employees and partners are equally trained in all of the topics labelled in this way. For this reason, we characterise these topics as project work requiring planning, so that you can contact your Hypersoft sales partner or Hypersoft Support in good time with this necessary planning. This approach ensures that we record your requirements carefully and respond to them in a targeted manner.


Ticket sales with complex validity are currently only possible via the reservation and shopping cart interface at3rd Party Customers, Reservation, Tickets API. Here, the external system must transmit the desired ticket items with validity to the shopping cart.

When redeeming the ticket, the entry system can check the ticket or the validity of the ticket with the aforementioned restrictions and simply accept or reject the ticket.

3rd party ticket sales via link

The ticket system can also receive a shopping cart via a link and then carry out the payment in the Hypersoft Check-Out process of the webshop and send the tickets to the orderer. Your 3rd party system can generate appropriate links for this. The shopping cart can contain ticket items but also all other items. The tickets are further processed in the Hypersoft system. The other items in the standard only billed.

You can create the customer record in the Hypersoft system via the customer data interface, or allow only a guest order with mail and name in the Hypersoft Webshop.

Your 3rd party system can use these links, for example, to redirect to us via an order button there: the 3rd party system could also send a mail to the orderer with the link and the request for payment.


Back to the parent page: Ticketing in the webshop