1. Mobile Boarding Pass QR
The mobile boarding pass is one of the highest-volume QR applications globally. The IATA standard (BCBP — Bar Coded Boarding Pass) defines the data structure encoded in the QR:
- Passenger name.
- Origin, destination, airline, flight number.
- Date, seat, class.
- Sequential ticket number.
- Check-in sequence number (boarding order).
The QR must display in high-brightness mode on phone screens to scan reliably in variable airport lighting.
2. Airport Wayfinding QR
A QR at each gate, terminal entrance, and transport interchange links to the interactive airport map pre-centred on the current location. Real-time flight information, departure board, and shop/restaurant finder in the same page. Particularly valuable in large airports for first-time visitors.
3. Lounge Access QR
Priority lounge access QRs are scanned at the lounge entrance to verify eligibility (credit card benefit, airline status, day pass purchase). The QR is issued per-entry by the credit card app or airline portal, time-limited to the current day and flight.
4. Duty-Free Personalisation QR
A QR at the duty-free entrance linked to the passenger's booking reference (scanned from the boarding pass) personalises the shopping experience: your duty-free allowance, recommended products based on destination country's allowances, and pre-order for collection at arrival.
5. Fast-Track Security QR
A QR in the booking confirmation or airline app links to the fast-track security slot booking for the departure time. Pre-booked fast-track QRs are scanned at the security lane entrance, ensuring orderly access without physical queue management.
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.
Related tools and guides
- For local payments, the [Pakistan payment QR](/pakistan-payment-qr) page explains the regional flow and what customers see.
- The [regional payment QR](/regional-payment-qr) guide covers payment codes used across different markets.
- The [bulk generator](/bulk-generator) builds many codes from a table when one-off generation would take too long.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- The [UTM builder](/utm-builder) adds campaign parameters so scans show up separately in your analytics.
- The [blog](/blog) collects more guides on sizing, printing, security, and payments for QR codes.
