Entrance and check-in guide
QR code event check-in in Cyprus
The door needs a workflow, not just a QR code.
A QR code is only the visible part of event entry. The useful system is the decision behind it: who may scan, what happens after the first valid check-in, how repeated codes are shown and how guest lists, tables and rewards stay separate at the door.
The short answer
How should QR check-in work at an event?
Sign in with your own authorized staff account, select the event and station, then choose Ticket, Table, Reward or Guest mode. Admit a ticket holder only after a successful result. Manual ticket codes use the same online checks; the scanner does not validate admission offline.
Prepare and rehearse the first scan
Set the event and station on a charged, connected device and check your staff access before guests arrive. In an authorized test setup, scan a valid test ticket and then scan it again. The first result records admission; the second must say Already redeemed. Repeat the rehearsal on the devices the team will use.
Use the right entry mode
Select Ticket for a paid ticket, Table for a table credential and Reward for a benefit. Use Guest mode to search the event guest list and check in the selected approved entry. A reward QR is not an entrance ticket; a table code is a separate credential from each guest ticket.
Read the result before admitting anyone
Redeemed confirms a successful redemption. Already redeemed means the code has been used; Wrong event or Wrong scan mode means the context needs checking. Invalid credential, Blocked, Not valid yet and Expired do not confirm admission. Age check required asks staff to complete the required check for the reward before retrying. Too many attempts calls for pausing, not repeated rapid scans. Move unresolved cases to the responsible manager.
Keep camera fallback separate from connection failure
Camera access needs HTTPS and permission in the browser. If the camera cannot read a ticket, enter its eight-character manual code in Ticket mode with an active connection. If connectivity fails, online and manual validation cannot confirm entry. Pause the live scanning decision and ask the responsible manager to follow the event emergency procedure; do not admit from screenshots alone.
Entrance and check-in guide
QR entry is reliable only when the scan decision is clear
The visible QR code is less important than the system response. Staff need to know whether a code is valid, already used, blocked, refunded or attached to another kind of entitlement before the guest reaches the bottleneck.
This guide treats scanning as an operational page rather than a technical feature list. It links mobile usability, manual fallback, live counts and permission boundaries to the visitor's real entrance experience.
In this guide
Decisions for this guide
Check these points against the current information before committing.
| Control | What to confirm | Risk avoided |
|---|---|---|
| Scan context | Set the event, station and correct ticket/table/reward mode. | A valid code for another context does not grant this entry. |
| Success result | Wait for a successful redemption before admitting the guest. | A camera read alone is not confirmation. |
| Exceptions | Read duplicate, age-check and blocked results separately. | These results require different staff decisions. |
| Manual validation | Test manual codes and the connection before opening doors. | Manual input still needs the online validation path. |
In this guide
Examples to work through
These are planning situations, not reports of events we attended.
Example 1
Before opening, use an authorized test setup to redeem a test ticket and scan it again. Staff should recognize the second result as already used rather than another admission.
Example 2
If the camera cannot read a code, enter the manual code in the correct mode with an active connection. A failed camera does not justify bypassing the validation result.
Example 3
If the scanner shows an age check, wrong event or blocked result, pause that admission and follow the organizer's procedure. Do not treat every warning as a successful scan.
E-E-A-T
How this operational guide was prepared
The guidance follows the product's implemented path from organizer verification and event setup to ticket inventory, connected payments, ticket issue, entrance and refunds. It distinguishes what the platform controls from what remains the organizer's legal and operational responsibility.
Payment statements are checked against Stripe's public Connect documentation. Product workflows are checked against the platform's implemented behavior. This is operational product guidance, not legal or tax advice; country activation still requires professional legal and tax approval.
The guide images are generated editorial illustrations. They help explain the setting but never replace real venue or event information.
Reviewed on 1 October 2026
Sources for this guide
These links support the local context or the specific booking and operational steps in this guide. A calendar or venue profile does not confirm admission, price or hours for a particular event; check its current organizer listing.
Send us the page and the detail that should be checked. We review corrections instead of silently changing factual claims.
Send a correction