Noteworthy information about the Ticket Shop

With the ticket shop, ticket items can be processed from the item master via the web shop. The tickets are automatically sent to the user by email after the order process. You create ticket items in the item master, here you can see how to Create ticket item.

The turnover of the tickets is booked in the standard when they are sold, even if they are services in the future.

Technical background and requirements

All ticket items sold via Webshop 2.0 automatically become online tickets. For this, the ticket items must receive the property Ticket in the item master. Here, the portal is the leading system that assigns the ticket numbers. In this case, the portal generates a 14-digit ticket number at the time of sale, which is composed as follows: 49 (Country Code) 95 (Online Ticket) 1234567890 (10 randomly generated digits). Example: 49 95 1234567890

This allows 1.7 million ticket numbers to be created per brand owner (or head office).

The prerequisite is an established master token per location.

Setting up the ticket system

A ticket centre must be defined to set up the ticket system. This is typically the customer number of the head office. This can currently only be defined by Hypersoft's development department, but does not require classification as project work subject to planning).

Define ticket items

Ticket items are defined like other items in the multifunctional item master. To set up ticket items, see the Create ticket item Ticket Item section.

Own assortment...

Please use a separate assortment for the order type Tickets, which does not overlap with other order types. Thus, when selecting the order type tickets, the user is also only shown ticket merchandise groups and ticket articles.

Workflow at the Ticket Shop

  1. Ticket items with the Ticket property are sold via Webshop 2.0.

  2. The portal generates a 14-digit ticket number.

  3. The order including the ticket number is transferred to the POS.

  4. After ordering and processing at the POS, the user receives the ordered tickets via download and email.

  5. Optionally, the invoice can be sent to the user by email using NoCOO.

  6. When redeeming, the POS will query the respective ticket number for validity in the portal.

  7. The portal gives the feedback Valid or not valid.

  8. If the ticket was valid, the POS sends the information is redeemed to the portal so that the ticket is validated.

Tickets can be checked at the POS or with Mobile Entry. Sold tickets can be viewed in the order overview in the portal and optionally downloaded.

Use tickets with queries

Ticket items can also be sold with queries and ingredients via the Recipe item type.The items can be configured accordingly as described in the Basic Knowledge 4: Components and Queries the item master section. Thus it is possible, for example, to create a cinema ticket with the queries soft drink and/or popcorn. The ticket item will continue to be delivered by eMail regardless of the components. You can see examples in the shop under Tickets with queries from user view.

The additional sales are displayed in the ticket. No voucher is created that could be used to book the items at the POS. The booking can be made in the POS system, for example, with the corresponding price level (0) or loss reason ticket supplement. The tickets could be collected as replacements. Another variant would be to issue vouchers for the additional sales when checking the ticket.

Restrictions and limitations

  • It is currently not possible to create multiple tickets, which can be redeemed 3 times, for example.

  • Currently, no specific ticket quotas can be managed; the standard system for item availability of the webshop applies.

licenses

The standard licences of the webshop are also sufficient for the Ticket Shop. The Ticket Shop is one of the available order types.

Back to the parent page: Ticket Shop from the user's point of view