Urgent.News

What's breaking now, across hundreds of outlets.

Tech

QR Code Generator: Why Half My Printed Tickets Refuse to Scan

Last month I printed 250 tickets for a company offsite. Each ticket carried a QR code pointing at our check-in form. On the morning of the event, roughly a third of them refused to scan. The phone camera would focus, hesitate, and give up. No error message, nothing. The codes looked perfect on my screen, so I blamed the print shop. Wrong call. The problem was in how I generated them, and it took…

In August, a reporter printed 250 tickets for a company offsite event, each containing a QR code that linked to a check-in form. However, upon arriving at the event, roughly one-third of the tickets failed to scan when attendees attempted to use their phone cameras. The issue turned out to be with how the QR codes were generated, not the print shop. The reporter discovered that there are several ways a printed QR code can fail to scan, and outlined the three main causes and solutions.

The first cause is the quiet zone, which is a margin of white space required around the QR code for scanners to properly detect it. If this margin is cropped or missing, the scanner will not be able to locate the code. The reporter initially set the border parameter to 0 to save ink, but this resulted in the codes failing to scan. To fix this issue, the border parameter should be set to 4, which ensures a four-module white margin around the code.

The second cause of scanning failures is when the URL within the QR code exceeds the maximum capacity that the code can accommodate. When the reporter added tracking parameters to the URL for marketing purposes, it caused the code to exceed its capacity. To resolve this issue, the reporter shortened the campaign parameters and returned to a lower error correction level (M instead of H). Additionally, a denser code with a larger grid size can help the scanner resolve the code more easily.

The third cause of QR code scanning failures is when the colors of the code are inverted. Most QR code scanners expect dark modules on a light background, and inverted codes are not recognized by most decoders. The reporter discovered that the poster version of the QR code, which came back as white modules on a navy blue background, failed to scan on any device they tried.

To prevent this issue, the reporter used dark modules on a light background and, if necessary, placed a white card behind the code to ensure proper recognition.

To avoid these scanning issues, the reporter recommends the following steps before printing QR codes:

1. Ensure the quiet zone is intact by using border=4 or -m 4 in the command line version.

2. Verify that the URL within the QR code is within the acceptable capacity limit for the chosen error correction level.

3. Use dark modules on a light background for maximum scanner compatibility, and add a white card behind the code if necessary to compensate for inverted colors.

By following these guidelines and performing a quick physical test with one proof ticket, the reporter was able to avoid the 11pm panic and ensure that the printed tickets would scan successfully at the offsite event.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Logistics Renewal Deadlines: When Should Failed Webhook Jobs Use a Delayed Queue or Cron?

Short answer: use a delayed queue when each failed webhook job needs its own retry time and audit trail; use cron to run a bounded redrive or reconciliation sweep when a little extra latency is…

  • Use delayed queue when each failed webhook job needs unique retry time and audit trail.
  • Cron schedule is suitable for bounded redrives, dead-letter reviews, or reconciliation passes.
  • Choose based on latency tolerance and need for individual retry time and audit trail.

How to Write a Creator Bio That Gets Follows (2026): Score Your Drafts, Keep One Call to Action, Cut Unproven Claims

Full disclosure: I built a bio-scoring tool on Capafy, so I'm biased. Everything below works with a notes app and fifteen honest minutes. You don't need the tool to use the method. TL;DR Your profile bio is the last thing a viewer reads before they decide to follow, and most creators write it once and forget it.

  • Bio's purpose is to convince viewers to follow a creator
  • Include only verifiable facts like posting frequency and credentials
  • Score drafts 0-10 on clarity, credibility, and call to action

More from Sunday 22 November →