1. A QR Code Is Not a Secret
Anyone who photographs a ticket QR can present it. Security must come from the backend, not the symbol. Generate secure tickets with our [URL QR code generator](/url-qr-code-generator) encoding unique tokens, and verify scans with a [QR scanner](/qr-scanner) app connected to your validation system.
2. Design Pattern
* Encode a long, random, unguessable token or a signed payload.
* Validate at the gate against the database and mark the ticket as used on first entry.
* Show clear "already scanned" messages with the time and gate.
* Use short-lived rotating codes in the ticket app for high-value events.
3. Offline Gates
If connectivity is poor, preload a signed ticket list to the scanner devices and sync scans when back online. Use our [bulk generator](/bulk-generator) for creating multiple unique tickets efficiently.
4. Printing
Use level M, large modules sized with our [QR size calculator](/qr-size-calculator), and matte stock for printed tickets. Follow our [QR placement guide](/qr-placement-guide) for positioning on ticket stock. Test quality with our [printed QR tester](/printed-qr-tester) before mass printing. Track redemption rates with our [UTM builder](/utm-builder) if linking to validation pages.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
