First, work out which kind of failure it is. A scanner that flashes red and does not beep cannot read the image — that is a display or print problem you can fix yourself. A scanner that beeps and then says invalid or already used read the code fine but the system declined it — that is a ticket or issuer problem, and the fix is different. The two halves of this guide cover each.
Part 1 — The scanner can't read the code
The reader is hunting for a sharp, high-contrast pattern with enough empty margin to lock onto. Anything that lowers contrast or hides the edges stops it. These are the five culprits, in order of how often they are to blame.
1. The screen is too dim
This is the number-one cause for phone tickets. Auto-brightness dims the display the moment it leaves direct light — which is exactly when you hold it under the scanner. Turn brightness to maximum manually and switch auto-brightness off before you reach the gate.
2. Glare and screen protectors
A matte protector scatters the scanner's illumination into a grey haze; a cracked one turns every crack into a false line. Tilt the phone slightly to kill reflections, and if you can, remove a heavy case or glare-prone protector.
3. The code is cropped or too small
Every 2D barcode needs a quiet zone — a blank margin around it. Zooming until the code touches the screen edges removes that margin and most readers lose lock. Show the whole code with a little space around it rather than filling the screen edge to edge.
Tip: "small ticket barcode" and "skinny barcode" complaints are usually this — the code is fine, it is just being displayed too small or too tightly cropped. Open the full ticket view rather than a thumbnail in an email.
4. Wrong distance or angle
Consumer scanners focus best at 10–20 cm. Too close and the camera cannot focus; too far and the modules are too small to resolve. Hold the code flat and square to the reader — scanners tolerate rotation, but a steep angle distorts the grid.
5. Faded or damaged print
For paper: thermal receipt paper fades with heat and time, and a printed code that has been folded across the middle may be unreadable. Reprint on plain paper, black on white, keeping the quiet zone. A 2D code should be at least about 2 cm on its short edge.
Part 2 — It scans, but the system rejects it
If you hear a beep or see the code light up and then get an error, the image was fine. The decoded ID reached the issuer's system and was declined. You cannot fix these by adjusting your screen — but knowing the cause tells you what to ask staff.
Double scan / "already used"
A ticket ID is marked used after its first successful scan. If you see "already scanned" it means either the code was read twice (a stray first scan, then the real one), or a copy of it went through ahead of you. Ask staff to look up the ID — they can see when and where it was first scanned, which usually resolves an accidental double scan on the spot.
Expired or rotating code
Some tickets use a rotating barcode that refreshes every 15–60 seconds and only works live inside the issuer's app. A screenshot of one of these scans as a perfectly valid barcode but is rejected because its time window has passed. Open the official app, let the code refresh, and present it live. See rotating barcode tickets for how these work.
Wrong ticket, wrong day, or wrong gate
It is easy to present a ticket for a different session, a different date, or a gate the ticket is not valid at. The scanner reads it correctly and the system declines it. Check the date, time, and entrance printed on the ticket against where you are standing.
"My ticket has no barcode" / "can't retrieve barcode"
Sometimes there is nothing to scan at all:
- The barcode is revealed late. Many issuers hide it until a few hours before doors, to limit screenshots. Open the app close to the event.
- It is app- or wallet-only. The code lives inside the official app or your phone's wallet, not in the confirmation email. Look for "view ticket" or "add to Apple/Google Wallet".
- There is no barcode by design. Some entries are validated by name, order number, or a QR you show from your account page. Read the confirmation email's entry instructions.
- It failed to load. A blank where the code should be usually means the app could not reach the server. Get online, reopen the ticket, and let it download before you reach the gate.
Full walkthrough: my ticket has no barcode.
Why scanning is slow
If the code reads but takes several seconds each time, the usual causes are a low-contrast image the reader has to work at, a code shown too small, or the system doing a live network check on every ticket at a busy gate. You can only influence the first two: brightness to maximum, code shown large but not cropped, held steady.
If nothing works: the manual fallback
Every ticket carries its ID in human-readable text, almost always directly beneath the barcode. Staff can type this in by hand — it takes ten seconds and always works. If the scanner keeps refusing, read the code out or point to it and ask them to enter it manually.
When it is the issuer, not you: if the ticket ID itself is rejected — not the scan — the problem is in the issuer's system. Step out of the line and contact the issuer using your confirmation email. We are a reference site and cannot look up or fix individual tickets; only the company that sold the ticket can.