Online Ticketing¶

The ticketing module enables advance sale of event tickets via the online shop. Guests purchase tickets online, receive QR code tickets by email, and are checked in by scan at the entrance. Ideal for clubs, events, and venues with limited capacity.

Before using it with customers

The checklist before the first event, the complete route to the entry screen and the limits that apply today are described under Setup, entry and operating limits. Event tickets are not to be confused with support tickets in the customer portal. For your own website there is also the guide Embedding ticket sales.

Activation: Admin → Settings → Operations → Ticketing

The ticket-scan screen and the Ticket tab of the article are shown in German regardless of the interface language; their labels are therefore given below in the original, with a translation in brackets.

Which flow suits my business?¶

Business	Sales	Entry
Event without club card	Online shop or embedded ticket shop	POS → „Ticket-Scan": check, then confirm entry
Club/disco with card account	Online shop or embedded ticket shop	Disco → Entry: check ticket, place card, optionally M/F, confirm entry
On-site sales only	Selling at the POS does not create a scannable ticket	For box-office-only operation, ticketing is not the right tool

Ticketing therefore also works without the disco module. Only if services are to be transferred to a club card are the disco module and a card needed as well.

Prerequisites before setup¶

The licence module Ticketing is enabled and ticketing is activated under Admin → Settings → Operations.
For online sales the Ticketing module is sufficient — the online shop (online ordering) is not required. The opening hours of the guest page must be set up (tickets can only be ordered within these hours), as well as at least one online payment provider. The settings for this (payment providers, design, legal texts, email, embedding) are under Admin → Online-/QR-Einstellungen.
Email sending works, so that the confirmation and PDF reach the guest.
At least one in-house payment method is active if refunds are to be processed on screen.
For the disco flow, admission groups, card readers and the disco workstation are set up.
The entry device has network access to DiKAS. For Scan with camera (phone, tablet or webcam on a PC) the browser must allow camera access; alternatively a hardware scanner can be used like a keyboard.

Recommended responsibilities

Ticket articles, prices, contingents and refunds should only be maintained by authorised staff. The actual scan workstation only needs a login and activated ticketing. At present the ticketing module has no separate fine-grained permission for each individual action; hand out operational user accounts sparingly for that reason.

Feature Overview¶

Feature	Description
Online Ticket Sales	Guests buy tickets via the shop with Stripe or PayPal
QR Code Tickets	Each ticket has a unique QR code as PDF
Entry Scan	Scan QR code, verify validity, grant entry
Event Dates	One fixed date, several dates to choose from, or a free choice of day
Capacity Management	Maximum ticket count per date with optional overbooking
Group Purchase	Buy multiple tickets at once (e.g., for birthdays)
Personalized Tickets	The customer's name is recorded and printed on the ticket
Disco Integration	Link tickets with admission group, free drinks, and credit
End-of-Day Report	Ticket statistics in the Z-report

Setting Up Ticket Articles¶

Tickets are based on regular articles with the type Ticket (ExtraOption 15).

Step 1: Create Article¶

Admin → Articles → New Article
Enter name (e.g., "New Year's Eve Party 2026")
Set price
Set article type to Ticket
Save

Step 2: Ticket Configuration¶

After setting the article type to "Ticket", the Ticket tab appears:

Dates — „Veranstaltungstermine"¶

Field	Description
„Veranstaltungstermine" (event dates)	The days on which the event takes place. Add further days with „Termin hinzufügen" (add date), remove them with the bin icon

Exactly one date: the shop shows the date as fixed; the guest does not have to choose anything.
Several dates: the guest chooses one of the dates entered.
No date: as before, the guest chooses any day from today — suitable for day admission, e.g. in a club.

Past dates are hidden automatically; a ticket whose dates are all in the past disappears from the shop. A date that is not entered cannot be ordered.

Disco Link — „Disco-Verknüpfung"¶

Field	Description
„Eintrittsgruppe" (admission group)	Which disco admission group applies to this ticket

Extras¶

Field	Description
„Freigetränke" (free drinks)	Number of included complimentary drinks
„Freiguthaben" (free credit)	Credit that is automatically posted to the card
„Garderobe inklusive" (cloakroom included)	Cloakroom service included in the ticket price

With „Garderobe inklusive", exactly the first single cloakroom booking on the assigned disco card is free of charge. Further cloakroom items are charged at the normal price.

Contingent — „Kontingent"¶

Field	Description
„Max. Kapazität/Tag" (max. capacity per date)	Maximum number of available tickets per event day
„Überbuchung %" (overbooking)	Allowed overbooking in percent (e.g., 10 % = 110 at max 100)

Cancellation Rules — „Storno-Regeln"¶

Field	Description
„Storno-Frist (Stunden vor Event)" (cancellation deadline in hours)	How many hours before the event cancellation is allowed
„Erstattung erlauben" (allow refund)	Whether a refund is possible after cancellation

Options — „Optionen"¶

Field	Description
„Personalisiert (Name)" (personalized)	Guest name must be provided and is printed on the ticket
„Geschlecht am Ticket-Einlass abfragen" (ask gender at ticket entry)	Optionally shows M/F at disco entry for statistics; has no effect on price or validity
„Gruppenkauf erlauben" (allow group purchase)	Allows purchasing multiple tickets in one order
„Max. Gruppengröße" (max. group size)	Maximum number of tickets per order (default: 10)
„Zeitfenster von / bis" (time slot)	Entry only between specific times (e.g., 22:00–01:00)

Test before the first sale¶

Create a date with a small test contingent.
Open the ticket shop like a guest, without an admin login.
Make a complete test purchase including payment.
Check the incoming email, PDF, name, date, QR code and included services.
First only check the ticket („Prüfen"), then really admit it („Einlass") and then try a double scan.
Compare the number sold, open tickets and contingent in Admin → Tickets.
Test cancellation and refund with a separate test order.

No automatic name check at the door

Earlier versions of this page promised a comparison of the guest name during the scan. It does not exist: entry checks validity, time window and double scan — not whether the person matches the printed name. If you need that, compare the name against an ID at the door yourself.

Ticket Status¶

A ticket goes through the following states:

Purchased → Checked In
          → Cancelled → Refunded
          → Expired

Status	Color	Meaning
Purchased	Blue	Ticket has been paid, waiting for entry
Checked In	Green	Guest has passed through entry
Cancelled	Red	Ticket was cancelled (by guest or admin)
Refunded	Gray	Purchase price was refunded
Expired	Orange	Event date has passed without entry

Online Shop (Guest View)¶

Purchasing Tickets¶

Guest opens the ticket shop (Tickets section in the shop or the embedded ticket page)
All available event tickets are displayed
Guest selects a ticket, the date if there are several, and the quantity
Included services are shown (free drinks, credit, cloakroom)
At checkout the guest enters name and email and pays online. If the cart contains only tickets, the checkout asks neither for pickup or delivery nor for a preferred time, and cash payment is not offered — the tickets arrive by email after payment.
The order page shows "Confirming payment …" and then "Thank you! Your tickets have been sent to ." with the tickets (QR code, ticket code, PDF).
The guest receives one confirmation email with all tickets of the order as PDF.

If tickets and food or drinks are in the same cart, the order runs like a normal shop order. Ticket-only orders do not appear in the order acceptance at the POS or on the kitchen or pickup monitor; they are completed after payment and listed under Admin → Tickets.

The ticket is only created once the payment has been confirmed and the associated POS receipt has been created. If the guest cancels the payment or the payment provider declines it, no valid ticket may be issued. If the contingent runs out between selection and checkout, the guest has to choose another date or a smaller quantity.

What the Guest Receives¶

One email per order with booking confirmation and all tickets as PDF attachments
The tickets directly on the order page (QR code, ticket code to type in, PDF)
PDF ticket in A6 format with:
QR code (unique entry code)
Ticket number (e.g., TKT-20260315-A4B2C6)
Event name and date
Guest name (for personalized tickets)
Included extras
Cancellation email if the ticket is cancelled

If an email has not arrived, first check the spam folder and the address entered. Staff can look up the ticket under Admin → Tickets and download the PDF again. The guest should only start a new purchase after it has been checked whether the first purchase has already been paid and exists as a ticket.

My tickets in the customer portal¶

A customer logged in to the portal sees their own tickets under My tickets and can reopen the QR code/PDF there. A customer can only cancel their own ticket that has not yet been redeemed, and only within the configured cancellation deadline. Tickets from a guest purchase without a matching customer assignment are found via the confirmation email or by staff.

Availability Display¶

Tickets with a capacity limit show "… left"; when only a few places remain, the note is highlighted
At 0 the ticket shows "Sold out" and can no longer be added to the cart for that date
Guests do not see how many tickets have been sold or how large the contingent is — that is only shown in the admin area (Admin → Tickets → Capacity)

Treat the QR code like cash

A photo or forwarded screenshot contains the same valid entry code. At the entrance the first successful scan wins; every further attempt is rejected as already redeemed. Do not share the QR code and PDF publicly.

Entry (QR Scan)¶

POS ticket scan without disco (standalone)¶

For entry without the disco module (e.g., pure event tickets):

POS → Menu → „Ticket-Scan"
Read the QR code with a hardware scanner, type in the ticket number or choose Scan with camera (see below)
Choose „Prüfen" (check). This step only checks:
Is the ticket valid?
Does the date match?
Is the time within the time slot?
Has the ticket already been checked in?
The result is displayed in color:
Green: Valid — grant entry
Red: Invalid — no entry
If the guest is actually admitted, press „Einlass" (entry). Only this second step invalidates the ticket and marks it as checked in. A mere check does not invalidate the ticket and can safely be repeated before the entry decision.

Scan with camera¶

Scan with camera works on any device with a camera: phone, tablet or a webcam on a PC.

The first time, the browser asks for camera permission — choose Allow.
The rear camera is preferred. If the device has several cameras, Switch camera changes to the next one.
The picture of a front camera or webcam is mirrored so the guest can hold the phone intuitively. This does not affect recognition.
If "No camera access" appears, permission was denied or the camera is in use: allow camera access for the page in the browser and close the camera in other programs. If the browser cannot recognise codes, the screen says so as well; then use a hardware scanner or type in the ticket number.

Meaning of the check results¶

Display	Meaning	Action at the entrance
„Ticket gültig." (ticket valid)	Date, time window, status and payment are correct	For a personalized ticket check the identity manually if required, then „Einlass"
„Ticket nicht gefunden." (ticket not found)	Code is unknown or incomplete	Scan the QR code again; check the ticket number/PDF and the purchase in the admin area
„Ticket gilt für …" (ticket valid for )	Ticket belongs to a different event day	Do not grant entry; clarify the date with the guest
„Einlass nur von … bis …" (entry only from … to …)	The configured entry period has not yet started or is over	Do not grant entry; call in the person responsible
„Ticket wurde bereits eingelöst." (already redeemed)	A previous entry has been saved	No second entry; check time and operator in the ticket administration
„Ticket wurde storniert." / „Ticket ist abgelaufen." (cancelled / expired)	Ticket no longer entitles to entry	No entry; clarify the status in the admin area

Entry is the invalidation

Only press „Einlass" if the person may really pass. The screen offers no simple way to undo an entry confirmed by mistake. In that case do not create a second ticket; have a responsible person check and document the case in the admin area.

Disco Entry with Ticket¶

If the disco module is active, an additional QR scan area appears on the Entry page:

Scan the QR code and check it. Here too this step only checks; it does not yet invalidate the ticket.
For a valid ticket, scan or place the disco card. A card is still required for disco entry.
If „Geschlecht am Ticket-Einlass abfragen" is enabled for the ticket article, record M/F. If the option is not enabled, the statistics value remains not specified.
Confirm entry. The ticket is invalidated once, the card is opened and the guest is linked to the disco card. DiKAS transfers the already paid admission as well as the configured admission group, free drinks, free credit and the cloakroom entitlement to the card. If the cloakroom is included, the first cloakroom booking is free; further bookings are charged normally.

The transferred services are not charged again: the ticket is the admission that has already been paid.

Linking the card, invalidating the ticket and transferring the services belong to one common entry process. A blocked card, a card already in use or an unreadable card must not be used. After an error, check ticket and card again instead of creating the guest a second time as a normal disco guest.

Admin Management¶

Tickets Page¶

Admin → Tickets (Sidebar)

Tab: Tickets¶

Search by ticket number, name, or guest name
Filter by status (Purchased, Checked In, Cancelled, etc.)
Date range restriction
Table with: number, name, date, status, price, paid, guest
Actions: Cancel ticket, download PDF

Tab: Capacity¶

Select date
Capacity cards per ticket type:
Progress bar (sold / maximum)
Remaining tickets

Tab: Statistics¶

Key metrics at a glance:

Metric	Description
Sold	Total number of tickets sold
Checked In	Of those, actually attended
Open	Purchased but not yet checked in
Cancelled	Cancelled by guest or admin
Expired	Not redeemed and expired
Refunded	Purchase price refunded
Revenue	Total revenue from ticket sales

Tab: Configuration¶

Overview of all ticket articles with their configurations, including the Dates column.

Group Purchase¶

For groups (e.g., birthdays, corporate events):

Guest selects quantity in the shop (e.g., 5 tickets)
For personalized tickets, the name of the person ordering is used on all tickets
All tickets are created as a group
Each ticket receives its own QR code
In the admin screen tickets are cancelled individually

Cancellation & Refund¶

Cancellation by Guest¶

Only possible if the ticket still has the status Purchased
Cancellation deadline must be observed (configurable per ticket type)
After the deadline, online cancellation is no longer possible

Cancellation by Admin¶

Admin → Tickets → select ticket → Cancel
Cancellation reason can be provided
Guest receives a cancellation email
A ticket that has already been redeemed cannot be cancelled like an unused ticket; check the special case operationally and do not "correct" it with a second ticket purchase

Refund¶

Only possible after prior cancellation
Must be allowed in the ticket configuration („Erstattung erlauben")
Admin → Tickets → cancelled ticket → Refund
Check the amount and select an active payment method
At most the amount actually paid can be refunded
First a negative, TSE-signed counter-receipt is created; only then does the ticket status change
Refund amount, payment method and receipt reference are documented

Cancellation and refund are two separate steps: a cancellation blocks entry and releases the reserved contingent place. Money only flows back with the subsequent refund.

Automatic Expiration¶

Tickets automatically expire 1 day after the event date if they were not checked in. The system checks hourly for expired tickets and sets their status to Expired.

End-of-Day Report¶

The following ticket metrics appear in the Z-report (end-of-day report):

Metric	Description
Sold online	Count and amount of tickets sold in the period
Checked in	Number of checked-in tickets
Refunded	Count and amount of refunds

Payment Methods¶

The following online payment methods are available for tickets (set up under Admin → Online-/QR-Einstellungen; visible without the online shop as soon as ticketing is active):

Payment Method	Description
Stripe	Credit/debit card, Apple Pay, Google Pay
PayPal	PayPal account or credit card via PayPal

Payment processing takes place directly in the guest's browser (Stripe.js / PayPal SDK). Tickets are only created after successful payment.

Operations on the event day¶

Before entry starts¶

Test DiKAS, the internet/network connection, scanner or phone camera and card reader.
Check a test ticket intended for this purpose and verify the display. Do not admit a real customer ticket for testing purposes.
Check the event day, time window, contingent and sold/open figures.
For disco operation, read a card as a test and check the correct admission group.
Name the person responsible for name questions, cancellations and refunds.

During entry¶

Every entrance works online against the same DiKAS data. The first successful entry invalidates the ticket; further parallel scans are rejected.
After each result, deliberately switch to „Nächstes Ticket" (next ticket). If in doubt, only check again.
Do not bypass red and orange results with a manual normal guest entry.
For personalized tickets, only compare names manually with an ID if the business has decided on this check.

After entry ends¶

Compare sold, checked in and open under Admin → Tickets → Statistics.
Process open cancellations and refunds.
Check the ticket values in the end-of-day report. They supplement the receipt figures and are not added as a second revenue.
Document anomalies with ticket number, time, workstation and operator; do not pass on the QR code unnecessarily.

Troubleshooting¶

Problem	Check and procedure
Ticket shop or ticket menu missing	Check the licence module, activation under Operations and online shop activation
Ticket article does not appear	Check article type Ticket, active ticket configuration and shop visibility
No remaining quantity visible	„Max. Kapazität/Tag" is missing; without a value the display is not reliable
Date is sold out	Reduce the quantity, choose another date or deliberately adjust the contingent; do not change overbooking spontaneously at the entrance
Payment cancelled/failed	Check with the payment provider and in the order; without a confirmed payment do not expect a ticket
No email/PDF	Check spam and address, search the ticket by name/number and provide the PDF again from the admin area
Camera does not start	Check browser permission and HTTPS; use a hardware scanner or manual entry
QR code is not recognised	Increase display brightness, clean the lens, change the distance or enter the code manually
Network/server not reachable	No offline entry on suspicion. Restore the connection and check the ticket again afterwards
Already redeemed	Check time/workstation in the admin area; do not grant a second entry
Refund fails	Fix the receipt/TSE error and reload the ticket; do not pay out twice
Disco card unreadable/blocked	Only use another permitted card after clarification; do not invalidate the ticket separately and do not create the guest twice
M/F selection missing	This is correct if the statistics question is switched off on the ticket article

Data protection and traceability¶

Personalized tickets store the name of the person ordering and the email on the ticket. For a group purchase the same name appears on all individual tickets.
The optional M/F selection serves exclusively for entry statistics and is not an identity check. If it is switched off, not specified is stored.
Status changes such as entry, cancellation and refund are logged with time and originator.
QR code and PDF are proof of entry. Only pass them on to the guest and authorised staff.
Retention and deletion periods follow the business's own data protection and receipt retention rules; DiKAS does not replace this organisational decision.

Current limits¶

Scannable tickets are only created via the online cart, not by selling the article at the POS.
No seats, seating plans, price categories, date-specific prices, multi-day or season tickets. Price and contingent apply equally to all dates of a ticket article.
No separate guest list and no individual participant names for group purchases.
A group cannot be cancelled in one go; the tickets are cancelled individually.
A ticket is always paid in full online. Deposits and partial payments do not exist.
A ticket is valid for one business day; for night events this extends until 06:00.
There is no offline entry. For large events, QR search and entry throughput must be tested in advance under realistic load.
Proof of entry is the PDF or the QR code; Apple and Google Wallet are not supported.

Embedding in your own website is described in Embedding ticket sales.

Frequently Asked Questions¶

Can a ticket be used multiple times? No, each ticket has a unique QR code and can only be checked in once.

What happens with a name error on personalized tickets? The system does not compare names — the entry scan checks validity, date, time window and double scan. A wrong name is therefore never detected technically. If you want to check the name, compare it against an ID at the door yourself.

Can tickets be sold at the POS? No, not as a scannable admission ticket. A ticket article can end up on a POS receipt like a normal article, but this creates no ticket document, QR code, PDF or contingent deduction. Sell scannable tickets exclusively via the online shop. Existing tickets can be scanned and checked in at the POS.

How does overbooking work? With e.g., 100 seats and 10 % overbooking, 110 tickets can be sold. Experience shows that not all buyers show up — overbooking compensates for no-shows.

Is the guest automatically notified upon cancellation? Yes, the guest automatically receives an email upon cancellation.

Is the disco module required for entry? No. Without disco, the standalone ticket-scan screen is used. Only transferring to a club card account requires disco and a card.

Is the M/F question mandatory? No. It can be switched off per ticket article and is only used for statistics. Without the question, not specified is stored.

Can DiKAS store the ticket in Apple or Google Wallet? No. Proof of entry is the PDF or the QR code — both can be kept on the phone and shown at the entrance.