← Back to blog

Offline Ticket Scanning: How It Works and How to Run It

November 18, 2026
Offline Ticket Scanning: How It Works and How to Run It

Offline ticket scanning works when the scanner already holds what it needs to judge a ticket: a list of valid codes, or a way to check that a code was signed by the system that sold it. The fan's phone holds the ticket, the scanner holds the rules, and the gate keeps moving with zero bars of signal. Gym bleachers, rural fields and packed tournaments are exactly where Wi-Fi quits, so the setup below is worth doing before your next event.

Athlo
Keep Game Day Moving
Athlo brings QR-ticketed events together with local sports tools, giving athletes, parents, and organizers one hub for their sports community.
Visit

TL;DR

  • Offline scanning needs two things ready in advance: the ticket saved on the fan's phone, and a scanner loaded with valid tickets or able to verify signed codes.
  • A scanner alone can only catch duplicates it saw itself. Two gates need to sync afterward, so decide in advance how you handle a ticket scanned at both.
  • Test your real devices in your real building. Airplane mode in the parking lot beats finding out at the door.
  • Fans should open their ticket at home, or add it to Apple Wallet or Google Wallet, before they leave.
  • Have a paper backup list and a spare charged phone at every gate.

Table of Contents

Why gates fail when the internet does

Picture a Friday night in a high school gym. Three hundred people, one cell tower, and a Wi-Fi network that was fine at 4 p.m. At 6:45 the line is out the door, the scanner is spinning, and somebody's uncle is announcing he drove an hour for this.

Every entry system has the same failure points:

  1. The fan's ticket won't load. The ticket lives on a server and the phone can't reach it.
  2. The scanner can't check the code. It asks a server "is this valid?" and gets no answer.
  3. The gates can't talk to each other. Gate A admits a ticket, and Gate B has no idea.

Offline scanning is a fix for each of those three, one at a time. If you only fix one, the line still stalls.

Fix 1: Get the ticket onto the phone before the game

The easiest win happens at the fan's end. A ticket that only exists as a web page fails the moment signal drops. A ticket saved to the phone does not.

Large venues tell fans the same thing. The United Center's mobile ticketing guide says to add tickets to Apple Wallet or Google Play so they can be reached without an internet connection, and notes that the Ticketmaster app's offline mode saves tickets once they've been viewed. It also points out that wallet tickets don't display a barcode: fans hold the phone near the scanner instead.

What that means for a youth tournament or a school event:

  • Tell fans in your confirmation message to open or save their ticket before leaving home.
  • Put "screenshot is not a backup" in your pre-event note if your scanners read live QR codes, since some codes rotate or are tied to the account.
  • At the door, have a volunteer ready to help the one grandparent whose phone is at 3%.

If you're buying rather than selling, our guide on buying youth sports event tickets QR style walks through what to save and when.

Fix 2: Teach the scanner to judge tickets without a server

This is the part people think is magic. It isn't. There are two common ways a scanner decides offline.

Method A: A downloaded guest list

Before doors open, the scanner downloads every valid ticket code for the event. When a fan walks up, the scanner looks the code up in its own memory. Found and not yet used? Green light. Found but already marked used on this device? Red light, duplicate.

This is simple and works well. The catch is in the last sentence: "already used on this device." A scanner offline has no way to know another scanner admitted the same code ten minutes ago. More on that in a moment.

Method B: Signed codes the scanner can verify

The second approach puts the proof inside the code itself. The open-source kadenz-scanner project describes one clean version: the server signs each ticket's QR token, and publishes a manifest of SHA-256 digests with a status for every ticket. Offline, the scanner hashes whatever it scans and looks for a matching digest. A match means the server signed that exact token. The scanner can recognize valid tickets, but it cannot forge or mint new ones.

In plain words: a hash is a fingerprint of the code. The scanner keeps a list of fingerprints, not a list of secrets, so a lost or stolen scanner doesn't hand anyone the keys to print fake tickets. If you want a friendly primer on why a signed code beats a plain one, this explainer on QR codes on invitations shows how a code ties a guest to a specific response, the same idea that stops a screenshot copy from becoming a free pass.

Method B: Signed codes the scanner can verify

If you want the fraud side in more depth, we cover it in our checklist to stop ticket fraud.

Which method should you expect?

Downloaded guest listSigned codes
What the scanner holdsEvery valid codeFingerprints of signed codes, plus status
Catches forged codesYes, if not on the listYes, no match means no entry
Catches repeat scans on one deviceYesYes
Catches repeats across gatesOnly after syncOnly after sync
Late sales after the downloadMissing until refreshedMissing until refreshed

Both methods share the same two weak spots: the other gate, and anything sold after the scanner last refreshed. Plan around those and you're 90% there.

Fix 3: Make multiple gates behave

Here's how a pickup-game-style disaster happens at an event. A parent scans in at Gate A. Their cousin, holding the same forwarded ticket, walks up to Gate B. Both scanners are offline. Both say green.

No software fully solves that while both gates are cut off from each other. What you can do:

  • Assign tickets to lanes. Send ticket holders by last name, section, or ticket type to a specific gate. Fewer overlaps, fewer duplicates.
  • Use one gate if the crowd is small. A youth rec game with 150 people doesn't need three entrances. One gate with one scanner can't double-admit.
  • Share records when you can. Some setups let nearby scanners exchange check-in records directly. If yours does, turn it on and test it. If it doesn't, plan to merge records the moment you reconnect.
  • Decide the rule in advance. If a duplicate shows up after sync, who decides, and what happens? Usually the answer is "the first scan stands, the second person is escorted to the organizer." Write it down so volunteers don't improvise.

What happens when the signal comes back

Offline scans don't vanish. They queue on the device and upload when it reconnects. A good system handles that carefully, and these are the things worth looking for:

  • Save first, confirm second. The scan should be stored on the device before the screen shows the green check. Otherwise a crash loses an admission.
  • Every scan is its own record. It should carry the ticket, the device, the event and a local timestamp.
  • Replays don't double count. If a sync times out and retries, the same admission shouldn't be counted twice.
  • Device clocks can be wrong. A phone with the wrong time will stamp scans wrongly, so check the clock on every scanner during setup.

After reconnect, review the duplicate list before you close out the night. That's where your real attendance count lives, and it's where you'll catch the cousin from the example above.

Your pre-event offline checklist

Run this the day before, in the actual building if you can get in. If you can't, run it in a room with signal off.

  1. Charge everything. Scanners, backups, battery packs. Bring cables.
  2. Load the ticket data. Open the scanner while online so it downloads the guest list or manifest. Confirm the ticket count matches your sales.
  3. Switch to airplane mode. Scan a real ticket. Then scan it again. The second scan should fail.
  4. Test two scanners. Scan the same ticket on both while disconnected, then reconnect and see how the system reports it.
  5. Restart a device mid-scan. Reopen the app and confirm earlier scans are still there.
  6. Try the weird tickets. A refunded ticket, a ticket bought an hour ago, a wrong-time phone. See what each one does.
  7. Check your door setup. Lighting, phone height, and a place for fans to stand so the camera can read the code. Our QR check-in guide for sports organizers covers the layout side.
  8. Print a backup list. Names and ticket types, sorted by last name. Paper doesn't need a battery.
  9. Brief your volunteers. One sentence each: what green means, what red means, who to call.
  10. Plan for a lost device. Know who can disable it and what attendee data sits on it.

For how a fan's scan moves from ticket to gate, see our step-by-step QR code entry flow. If your venue has choke points at the door, our gate management guide for youth sports is the companion read.

Troubleshooting at the door

What you seeLikely causeWhat to do
Code won't readGlare, dim screen, cracked glassRaise brightness, tilt phone, or look the name up on your list
"Already used"Real repeat, or forwarded ticketCheck the scan time and ask the fan who entered with it
"Not found"Bought after the last refresh, or wrong eventCheck the order confirmation, then admit manually and log it
Scanner frozenLow battery or app memorySwap to the backup, restart the first one later
Line backing upOne scanner, too many fansOpen a second lane for wallet tickets or pre-check names

The golden rule: when in doubt, keep the line moving and sort it out afterward. A parent waiting 10 minutes in the cold remembers the wait longer than the fix.

Where Athlo fits

Where Athlo fits

If you run youth or high school events, Athlo's event ticketing gives you QR-ticketed entry and payments in one app, so tickets, check-in and payouts sit in one place instead of three. Athlo (athloapp.com) is a free download, with Athlo Plus at $3.99 per month and Athlo Pro at $7.99 per month if you want more. Core social features are free, and a fee applies to payments processed for tickets, games and coaching sessions.

If you're deciding between paper and phones at the door, our comparison of online vs. paper tickets lays out the tradeoffs, and our post on mobile ticket scanning at the door covers what we've found actually works.

Athlo

Plans and event tools are listed on the Athlo home page.

Our take on offline entry

We think of the gate as the one moment where everything you built, the schedule, the payments, the promotion, either pays off or turns into a traffic jam. Fans don't care how clever your system is. They care that the line moves.

That's why we like keeping the whole ticket journey in one place: the sale, the QR code, the scan, and the payout. When a ticket and its payment live together, you can answer the three questions every organizer gets at the door: did this person pay, did they already come in, and who gets the money.

Our advice for any organizer, with any tool: prepare for a bad connection before it happens. Save tickets early, test your scanners in the real building, and give your volunteers a simple rule for the weird cases. Protect the vibe like it's the product. A smooth gate is the first thing families remember about your event.

Abdulazeez

FAQ

Can you scan tickets on a phone without internet?

Yes, if the ticket is saved on the fan's phone and the scanner can judge it locally. Wallet tickets in Apple Wallet or Google Wallet are the most reliable for the fan side, as the United Center's guide notes. The scanner needs a preloaded ticket list or a way to verify signed codes.

Can a QR code be scanned without internet?

A phone camera can read any QR code without internet, because the code is just a pattern containing data. What it can't do offline is open a web page that code points to. Ticket scanners get around that by checking the code against data they already hold.

How does offline scanning stop fake tickets?

The scanner either holds a list of every valid code, or checks that the code was signed by the ticketing system. A made-up code won't match, so it's rejected. Signed-token designs like the one in the kadenz-scanner project let a scanner recognize real tickets without being able to create them.

What happens to scans when the connection returns?

The scanner uploads its saved scans and the system merges them with other gates' records. Repeats across gates show up at that point, so review them before you finalize attendance. A well-built system ignores a replayed upload instead of counting the same entry twice.

What should I bring as a backup?

Bring a printed attendee list, a spare charged phone, a battery pack and a pen. Add a short written rule for duplicates so every volunteer handles them the same way.

Sources

Ready to run your next event with QR tickets? Download Athlo (athloapp.com) on the App Store or Google Play.