QR Codes for Event Tickets and Check-In: Cut Lines, Cut Costs (2026)

If you run events — workshops, grand openings, charity dinners, pop-up markets, fitness classes — you know the pain: long check-in lines, printed guest lists that get lost, and zero data on who actually showed up.

QR codes fix all three problems. Each attendee gets a unique QR code ticket (via email, SMS, or a messaging app). At the door, your team scans it with any phone. Done — checked in, timestamped, no paper.

This guide walks through exactly how to set it up, whether you host 20-person workshops or 2,000-person festivals.

Step 1: Create your event page or RSVP form

You need a URL where each ticket lives. This can be:

• A Google Form or Typeform collecting name + email
• A ticketing platform (Eventbrite, TicketTailor, Humanitix)
• A simple landing page on your own site
• A WhatsApp or Messenger link for small events

The key: each registrant gets a unique URL (or a shared URL with a unique code embedded).

Step 2: Generate a QR code per ticket

Use QRs.bd's QR code generator to create codes. Two approaches:

• One dynamic QR per attendee — encode yourdomain.com/check-in?ticket=ABC123. The code stays the same; you update what happens behind it (valid, cancelled, used) without reprinting.
• One static QR for all attendees — encode a shared check-in page URL. Cheaper to set up, but you lose per-person tracking.

For anything bigger than a casual meetup, go dynamic.

Step 3: Distribute tickets

Send each attendee their QR code:

• Email — embed the QR image in the confirmation email
• SMS/WhatsApp — send the QR image or a short link to download it
• Passbook/Google Wallet — advanced but slick; the QR appears in their wallet app

Add a message: "Show this QR code at the door. Screenshot it in case you lose signal."

Step 4: Scan at the door

Your check-in team uses a phone or tablet with:

• QRs.bd's built-in scanner (if using our platform)
• Any QR scanner app that opens the URL and shows the ticket status
• A shared Google Sheet — if your QR encodes a Google Form URL, the sheet auto-collects timestamps

One person with a phone can check in 300+ guests per hour.

Every scan logs:

• Timestamp — when the guest arrived
• Ticket ID — who scanned in
• Device/location (if permissions allow)

This gives you:

• Show-up rate — tickets issued vs. scans. Typical for free events: 40–60%. For paid: 80–95%. Now you know.
• Peak arrival window — see when most people show up. If 70% arrive in the last 15 minutes, plan staffing accordingly.
• Repeat attendees — if you run recurring events, track who comes back.

Static QR codes encode a fixed URL. Once printed or sent, you can't change where they go.

Dynamic QR codes store a short redirect URL. You can update the destination anytime — without changing the code itself.

For events, this means:

• Venue change? Update the link to the new address. Everyone's existing QR still works.
• Event cancelled? Redirect to a cancellation notice. No one shows up to an empty room.
• Want to reuse the QR? After the event, redirect it to a photo gallery, feedback form, or next event's registration.

Dynamic QR codes are included on all QRs.bd plans — even the free tier gives you a limited number.

1. Using a shared QR for everyone — works for a 10-person meetup. Falls apart at 50+ because you can't track individual check-ins or prevent screenshot-sharing.
2. No offline plan — venues with poor signal can't load URLs. Print a backup guest list or have the scanner app cache ticket data.
3. Tiny QR codes on screens — if attendees show the code on their phone, make sure your scanner can read it from arm's length. Test before the event.
4. Forgetting to test the full flow — register yourself, receive the QR, scan it at the venue. If any step breaks, fix it before guests arrive.
5. No backup scanner — phones die, apps crash. Have at least one backup device with the same setup.