Skip to content

The One QR Code Mistake That's Costing You Scans

Let's be direct: the single most common QR code mistake is sending people somewhere bad.

Not a broken link. Not a wrong URL. Just a destination that's wrong for the context — a homepage when they expected a specific offer, a PDF that takes 8 seconds to load on mobile, a desktop page that's unreadable on a 6-inch screen.

The QR code worked. The scan happened. The customer bounced in 3 seconds and never came back. You'll never know, because your analytics show a scan and assume success.

The destination problem: what it looks like in practice

Scenario one: a restaurant puts a QR code on every table. It goes to the restaurant's website homepage. The customer scans it. They see a homepage with a hero image, a mission statement, a news section. They wanted the menu. They didn't get it. Many close the browser rather than navigate. The QR code 'worked'. The experience was poor.

Scenario two: a product brand puts a QR code on packaging pointing to a 4MB PDF menu of their full product range, hosted on a server that's not optimised for mobile. The customer is in a kitchen with moderate WiFi. The PDF loads in 9 seconds, then renders at desktop scale on a phone screen. They close it. The QR code 'worked'. The experience was poor.

Scenario three: a marketing campaign runs QR codes on flyers. The flyer promotes a 20% discount. The QR code goes to the homepage because nobody set up a landing page in time. The customer scans, sees no discount, assumes the offer isn't real, leaves. The QR code 'worked'. The campaign failed.

The fix: obsess about the destination first

Before you design the QR code. Before you decide where to put it. Decide exactly where it should go and make sure that page is:

  • Mobile-optimised — tested on iOS and Android in a real environment
  • Fast — loads in under 3 seconds on a 4G connection
  • Relevant — directly related to what the customer expected when they scanned
  • Specific — a product page, not a homepage; a landing page, not a sitemap
  • Current — the right page, not a page that was right six months ago

The other mistakes, in order of how often they happen

No call to action on the code

A QR code with no label. People don't scan mystery codes. Add 'View menu', 'Claim offer', 'Watch video'. Scan rates go up. Every time.

Too small to scan reliably

Minimum 2cm × 2cm at arm's length. More for anything viewed from further away. Designers consistently make QR codes too small because they feel like they're taking up too much space. The code needs to be big enough to do its job.

Saved as a low-resolution PNG and scaled up for print

The blurring that comes from scaling a raster image makes small QR codes fail. Always export SVG or PDF for anything going to print.

Static code pointing to a URL that later changed

The page moved. The URL structure changed. The code on 10,000 printed items is now pointing to a 404. A dynamic QR code would have let you update the destination without touching the print. For anything that might change — use dynamic.

Not testing before printing

Scan it. On multiple devices. Before you send it to print. This takes 2 minutes and prevents 100% of print-run failures caused by QR code issues.

The checklist

  • Destination decided and tested before designing the code
  • Mobile landing page loads in under 3 seconds on 4G
  • Call to action frame added to the code
  • Code is at least 2cm × 2cm at intended print size
  • Exported as SVG or PDF for print
  • Tested on iOS and Android
  • Dynamic code used for anything that might change

Most QR code failures aren't technical. They're planning failures that no amount of design sophistication will fix.

Build a QR code that works — and tracks everything →