What a QR code ticket actually is
A QR code is a way of writing a short piece of text so that a camera can read it quickly and reliably. On a ticket, that text is usually one of two things: a reference that points to a record held by the organiser, or the ticket details themselves written into the code. The first kind is the one to want. The code says nothing on its own; the scanner looks it up and gets back a name, a ticket type and a status.
This matters because a code that carries its own details — a name, an email address, a seat — reveals them to anyone who photographs it, and cannot be changed once it has been sent. A code that is only a reference can be cancelled, reassigned or upgraded by changing the record, without sending the guest anything new.
Screenshots, forwarding and resold tickets
Every QR ticket can be copied. A screenshot is a perfect copy; so is a forwarded email or a photo of a printed page. No design of the code itself prevents this, and it is worth being honest about that rather than relying on it. What a ticket system can control is what happens when the copy is used.
The answer is single admission. The first scan of a code admits the guest and marks the ticket as used. Any later scan of the same code — whether it is the same person or a friend with the screenshot — shows the door that the ticket has already been admitted, when and at which door. At that point a human decides. This turns copying from an invisible problem into a visible one, which is the most a ticket can realistically do.
For events where resale or transfer is a real risk, show the guest’s name on the scanner screen and, for high-value tickets, ask for identification at the door. Decide your transfer policy in advance and write it on the ticket: if transfers are allowed, offer a way to change the name on the record so that the new holder receives a new code and the old one stops working.
Signed codes and why the code should carry nothing readable
A well-built QR ticket contains a long, random, unguessable reference — sometimes signed, so that the system can tell at once whether the code was issued by it or typed up by someone hoping to guess a valid one. Sequential numbers such as ticket 0001, 0002, 0003 are the classic mistake: anybody who sees one can work out the next.
The code should not contain the guest’s name, email address or anything else readable. The name belongs on the scanner’s screen, not in the image. That way a photo of a ticket posted on social media gives away nothing, and a lost ticket can be cancelled and reissued by changing what the code points to.
Re-entry: when the same ticket should open the door twice
A festival with a smoking area, a conference across two buildings, a gala where guests step out for air: some events need people to leave and come back. Decide which kind of event yours is before tickets are sent. If re-entry is allowed, the second scan of a code should be recorded as a re-entry rather than refused, and the report should keep re-entries apart from first arrivals, otherwise the attendance count grows every time someone goes outside.
If re-entry is not allowed, say so on the ticket and at the door. A guest who leaves expecting to return, and is then refused, is a complaint you could have prevented with one line of text.
Paper, phone or wallet
A QR ticket does not care what it is displayed on. A printed invitation, a phone screen, a tablet held up by a parent for the whole family: a scanner reads them all. Accept all of them. Some guests prefer paper, some have phones with cracked screens or low batteries, and a door that insists on one format turns a scan into a conversation.
Digital wallets — Apple Wallet and Google Wallet — are a convenient extra where they are offered: the pass sits in a familiar place and can appear on the lock screen near the time of the event. They are not a requirement. A ticket sent by email with a clear QR code, readable without logging in and without an app, is what every guest can open, and it should always be there even when a wallet pass is offered too.
Whatever the format, make the code large enough to scan at arm’s length, keep a quiet margin of white around it, and put the event name, date and door on the same page so the guest does not have to look elsewhere.
At the door: any phone can scan a QR ticket
Scanning a QR ticket needs a camera and a screen, not special hardware. Any smartphone the team already carries can be the scanner, as long as it shows the guest’s name, the ticket type and a clear status — admitted, already admitted, not valid — in a size readable in bad light. Bright screens from the guest’s side are rarely the problem; a dirty camera lens and a scanner held too close usually are.
Tell guests what to have ready. A line in the last reminder — “open this email at the door, brightness up” — saves more time than any scanner.
Free invitations and paid tickets on the same record
The mechanics are the same whether the ticket was free or paid: one code, one guest, one admission. What changes with paid tickets is the work before the door — ticket types, checkout, receipts, refunds — and that is worth keeping in the same guest record as invited guests, so the door sees a single list. In Winglark, GatePass gives every guest a personal QR code that any phone reads in a second, and paid ticket sales carry no commission and are opened together with the team as a managed activation, not switched on from a page.