How Do QR Codes Work in Customer Service?

A customer stands at a dry cleaner’s collection counter with the phone held up, aiming at a small printed square taped to the till surround. They move closer. They move back. Nothing happens. The queue behind them has stopped moving as well.

That scene is illustrative rather than a real venue, but the mechanics behind it are not. A QR code is a printed block of data, and in customer service that data is usually a web address. The scan itself is a camera reading a pattern and handing the result to the phone. Everything that decides whether the customer gets what they came for happens afterwards, somewhere else.

So the interesting part of a QR code, for anyone running a counter, is never the square. It is the handful of things sitting behind the square that can quietly go wrong.

Key Takeaways

  • A QR code stores a string of characters, almost always a web address. The scan is a camera reading it, and nothing travels back.
  • Static and dynamic are not two kinds of code. The difference is whether the string encoded was a final address or a redirect somebody else controls.
  • Error correction is a choice made when the code is generated, and it is why a scuffed code still scans (Denso Wave, retrieved 30 August 2026).
  • The National Cyber Security Centre says a code in a pub or restaurant is probably safe to scan, and a code in an open space like a car park might be riskier (NCSC, 2024).
  • A scan needs a phone, a camera, enough sight to aim and a live connection. Any one missing, and the customer needs another route.

How does a QR code actually work?

A QR code holds data in a grid of black and white squares, and it is built to be read badly. The camera does not need a clean, flat, brightly lit view. It needs enough of the pattern to work out the rest. That tolerance is designed in, not luck.

Each small square in the grid is a module. How many modules a code carries is set by its version, and the format defines a lot of versions. Version 1 is 21 modules across, and each step up adds four more per side. In Denso Wave’s words: “The symbol versions of QR Code range from Version 1 to Version 40.” (Denso Wave, retrieved 30 August 2026)

The tolerance comes from error correction. Denso Wave, the company that invented the format, puts it simply: “QR Code has error correction capability to restore data if the code is dirty or damaged.”

What matters operationally is that the strength of that recovery is a choice. Whoever generates the code picks one of four levels, and the code carries the consequence for the rest of its printed life.

Error correction levelWhat the source statesWhat it is suited to
L“Approx. 7% of codewords can be restored.”Clean conditions carrying a large amount of data
M“Approx. 15% of codewords can be restored.”The level Denso Wave states is most frequently selected, and the one used in its own worked sizing example
Q“Approx. 25% of codewords can be restored.”One of the two levels suggested for a factory setting where codes get dirty
H“Approx. 30% of codewords can be restored.”The other, and the most tolerant of damage
Source: Denso Wave, standardisation page and error correction page, retrieved 30 August 2026. The right-hand column paraphrases Denso Wave’s own guidance on choosing a level.

Recovery is not free. Raising the level hands more of the grid over to correction data, so either the code carries less, or the same content needs a higher version and more modules. A tougher code is a bigger code. That trade sits behind every printed square, and somebody made the call before it went to print.

What is the difference between a static and a dynamic QR code?

They are not two kinds of code. A QR code stores a string of characters, and that is the whole of it. If the string encoded was the final web address, the destination is fixed the moment the code is printed. If it was a short redirect address, whoever controls that redirect decides where it lands afterwards. The difference is in what was encoded, not in the code.

The standard’s own published scope does not carry the distinction either. Its registered title is “Information technology – Automatic identification and data capture techniques – QR code bar code symbology specification”, and its published scope reads:

“This document specifies requirements for the symbology known as “QR code”. It specifies the QR code symbology characteristics, data character encoding methods, symbol formats, dimensional characteristics, error correction rules, reference decoding algorithm, production quality requirements and user-selectable application parameters.”

The words static and dynamic appear nowhere in the text of the IEC product page for that standard, including the scope above. That was checked by stripping the page’s markup and counting: zero occurrences of each. It is a finding about that page and its published scope. The full text runs to 111 pages, sells for CHF 227.-, and was not read here (IEC Webstore, edition 4.0, 2024).

There is a genuine tension in that. Denso Wave states that it waived the rights to the patent it held (Patent No. 2938338) for standard QR codes only (Denso Wave, retrieved 30 August 2026). The document describing that format sits behind a price.

Six of the eight guides that come up first for this question were fetched and read on 30 August 2026. Their markup was stripped first, so each check ran over the page text. Two of the six set static against dynamic and explain the difference. Three of the rest mention dynamic codes without ever naming a static one, so the choice never appears as a choice.

None of the six names the standard, the error correction levels or the margin a code needs. That is why those sit further up this article.

In practice, it comes down to one thing. A printed code carrying a final address is a commitment you cannot revise without reprinting. That decision gets made before anything reaches the printer.

The code is a pointer, not a channel

A scan runs one way and is over instantly. The phone reads a string of characters off a surface and passes it on. Nothing comes back. The code does not know it was scanned, who scanned it, how often, or whether anything useful happened next.

So a printed code is not a connection to a customer. It is an instruction to go somewhere. Everything the customer then experiences belongs to whatever is waiting at that address: a page, a menu, a payment form, a sign-up screen.

That address can still count the arrivals. A redirect logs whoever passes through it, which is how scan tracking is sold. The counting happens at the destination, not in the square on the counter, and it is a property of what you encoded rather than of the code.

Two ordinary decisions follow from that. The first is what the destination asks for on arrival, because what a phone number obliges you to look after starts at the moment the form requests one. The second is what to put in the message once it arrives, which decides whether the scan repaid the effort.

A code can scan perfectly and still fail the person at the counter. If the page is slow, the form is broken or the wording is a wall of text, the square did its job and nothing else did.

What makes a scan fail?

The causes worth checking first are physical rather than technical. In open-ended interviews, researchers studying customers aged 60 and over heard about three of them:

“Some spoke about their struggles to scan QR codes due to glare, poor placement or small font sizes, which demanded more mental effort and often led to frustration and anger.” (Phys.org reporting Petkovic, Nanu et al., Journal of Hospitality and Tourism Insights, 2026)

Glare, placement, print size. Those are three things some interviewees raised, not a ranking. The study pairs those interviews with a separate questionnaire, and the reported numbers belong to the questionnaire rather than to this finding. The same write-up records the opposite experience too, from people who met well-designed codes and came away satisfied. The institution is in the United States.

Light is the fix both phone makers reach for, though not the same fix. Apple’s scanning instructions carry one tip, which is “Tip: Tap the flashlight to add more light.” That is the scanning phone throwing light onto a printed square.

Google’s troubleshooting list points the other way, because it covers a code shown on a screen rather than printed. Its advice is to “Make sure the screen showing the QR code is bright enough for the camera to see the code.”

That one does not transfer to a counter. Three of its other items do, and they are all the phone itself: a smudged lens, a tilted phone, and the wrong distance.

Size is arithmetic, and Denso Wave publishes the sum. Take a code carrying 50 alphanumeric characters at error correction level M. That needs Version 3, which is 29 modules across. Print it on “a printer with 400 dpi resolution” at 4 dots per module, and each module comes out at 0.254 mm:

25.4 mm/inch ÷ 400 dpi × 4 dots/module = 0.254 mm/module

The symbol is therefore 29 modules × 0.254 mm/module = 7.366 mm across. Add the margin and the printed area becomes 7.366mm + 0.254mm/module × 8 modules = 9.398mm (Denso Wave, retrieved 30 August 2026). Under a centimetre square, for fifty characters. If that will not fit the space available, the same page offers three ways out. Drop to a lower version, make each module smaller, or split the content across more than one symbol.

That margin is not decoration. Denso Wave states that “QR Code requires a four-module wide margin at all sides of a symbol.”

A code printed hard against a border, a coloured panel or the edge of a card may simply not read, and no amount of good light rescues it.

When a code stops scanning at a counter, this is the order to work through:

  1. Light first. Tap the torch, or move the code away from a window or a spotlight causing glare.
  2. Distance and size next. Pull the phone back until the whole square sits inside the frame.
  3. Then the margin. Check that the four-module margin survived whoever designed the sign.
  4. Then the printed condition. Scuffs, grease and fading eat into what error correction can recover.
  5. Last, the connection. A code can read perfectly and go nowhere if there is no signal at the counter.

Are QR codes safe for customers to scan?

The UK’s National Cyber Security Centre published its own risk judgement in February 2024, and it is a gradient rather than a verdict:

  • “The QR codes used in pubs or restaurants are probably safe for you to scan.”
  • “Scanning QR codes in open spaces (like stations and car parks) might be riskier.”
  • “The majority of QR code-related fraud tends to happen in open spaces (like stations and car parks), and often involves an element of social engineering.”
  • “we recommend that you use the QR-scanner that comes with your phone, rather than using an app downloaded from an app store”

The same post puts the category in proportion, calling this type of scam “relatively small compared to other types of cyber fraud” (NCSC, 2024). The guidance on that page is written for the person doing the scanning, not for the business displaying the code.

There is one figure worth having, with its scope attached. Which? reported “with reports to Action Fraud about all QR code scams, not just parking, more than doubling in 2024 to 1,386” (Which?, 2025). That is a count of reports made in one calendar year. It is not a rate, and it says nothing about how often a scan goes wrong.

The reason this reaches a venue at all comes from the same report. Which? reported North Wales Police saying that “dodgy QR codes are on the rise and have been found on restaurant menus, public transport timetables and car parks”. Menus put the problem indoors.

The mechanism is a sticker, and a local authority documented it on its own estate:

“Bogus QR code stickers have been found in council car parks, sending users to a fraudulent cloned website that requests credit card details and other personal data.” (Walsall Council, 2025)

What the council then told the public is the part an operator should sit with. Its advice was blunt: “Users are advised not to scan any QR codes or barcodes they see on parking machines or signage.”

The wording there matters. The advice was not to avoid the fake codes, which nobody can pick out by eye. It was to stop scanning codes on those machines altogether, and it points people to the parking app or to cash and card instead. That is the shape of the risk for any venue. A displayed code sits on an unattended surface, and one sticker can make the honest advice about every code on it “don’t”.

There is a public register that shows what the alternative costs. HMRC now publishes a page so recipients can check a code before scanning. It states: “Letters and leaflets from HMRC may contain a QR code which you can scan for further information or help.” (HM Revenue and Customs, 2026). The page’s own instruction is to “Check a list of letters with a QR code from HMRC to help you decide if it is genuine.”

Counted from that page’s contents list on 30 August 2026, it carries 36 entries: 35 name a specific letter or leaflet type, and the last is a catch-all. Reading every destination described on the page shows one consistent pattern.

Each destination is a public GOV.UK guidance page or an HMRC contact page. Even the two codes about the HMRC app go to guidance about it rather than to a download. Not one is a login, a payment page or a form asking for details. That includes the letters about paying a bill, which point at guidance on how to pay. That pattern is a rule any venue can copy.

The customers a QR code leaves out

A scan needs four things at the same moment: a phone, a working camera, enough sight to aim it, and a data connection once the address opens. Miss any one and the customer is standing at a counter with nothing to fall back on.

Those same failure modes are not spread evenly either. For someone with good eyesight and a new handset they are a minor irritation. For someone with neither, they are the difference between being served and giving up. The research records frustration and anger as a common result.

This is where the older methods keep earning their place. The hardware a pager system puts on the counter asks nothing of the customer’s phone, and calling a name asks nothing beyond hearing it.

Put it plainly: a QR code adds to a service, it does not replace one. A venue that removes the alternative has not saved anything. It has moved the cost onto the customers least able to carry it, and it will meet that cost again at the counter, one confused customer at a time.

Where do QR codes fit in customer service?

The useful question is not whether to use a code. It is what the code has to carry, and whether that thing will ever need to change.

The jobWhat the code carriesChanging it later
Sending someone to guidance or help, as HMRC’s letters doAn address for a public information pageFixed if a final address was printed, changeable only if a redirect was
Taking a payment, as parking machines doAn address for a payment routeSame rule, and this is where a swapped sticker does the most damage
Showing a menuAn address for the menu pageMenus change often, so the destination usually needs to be movable
Enrolling a customer in updatesWhatever the sending service encodes, often shown on a screen rather than printedA code shown on a screen is regenerated, so nothing needs reprinting

The first three jobs come from the sources cited above. The fourth is the one where the code is shown rather than stuck down, and it works differently.

Take the limits of that last row first. Upd8All is one app built this way, and what it cannot do matters more than what it can. Channels are one-way and messages are capped at 40 characters, so it suits an order-ready alert and not a conversation. The customer still needs a smartphone, a camera and a working connection, which is exactly the exclusion described above.

No phone numbers or email addresses are exchanged between the business and the customer. Pairing happens by scanning a QR code. There is more on the flow in what Upd8All does with a scanned code. The practical side sits in setting up a QR code to send updates. Anything that needs a reply belongs on a different route.

Where a code is the wrong shape for the job, the other routes to a customer’s phone set out what else is available.

Where the code stops being the point

The square is the cheapest component in the whole arrangement. Denso Wave waived the patent for standard codes, it takes seconds to generate, and the format was engineered to survive poor conditions. Nobody needs to worry about the code.

What decides whether it works sits entirely behind it. Which string was encoded. How large it was printed. Whether the margin survived the designer. Whether anyone can walk up and stick something over it. What is waiting at the other end when the customer arrives. Every one of those is a decision somebody made, and most were made before anything went to print.

A venue that gets the code right and the destination wrong has built nothing at all. The square scanned. The customer is still standing at the counter, holding a phone, waiting for somebody to help.

Frequently asked questions

Do customers need an app to scan a QR code?

On current phones, no. Apple documents two routes on an iPhone: the Camera app, and a scanner shortcut that can be added to Control Centre. Google states that you need Android 9 or higher to scan QR codes, in the context of signing in to its own accounts. The National Cyber Security Centre’s advice is to use the scanner that came with the phone rather than one downloaded from a store.

Can a QR code still be scanned if it is damaged or dirty?

Often, yes. Denso Wave states that “QR Code has error correction capability to restore data if the code is dirty or damaged.”

How much it survives was fixed when the code was generated, so a code already on the wall cannot be made more tolerant after the fact. Recovery has a limit too. A code torn across, heavily faded or partly covered still fails.

Can somebody change where my printed QR code goes?

Not if the final web address was printed into it. If a redirect address was encoded, whoever controls that redirect does. The catch is that nobody can tell which kind a code is by looking at it. The pattern gives no clue, so the only way to know is to check what was encoded before the print run goes out.

How do I know if a QR code has been tampered with?

Physically, by looking at whether the code is a sticker sitting on top of something else. A corner that peels, an edge that sits crooked, or printing showing underneath are all worth a second look. For an operator, the practical answer is a routine check of every displayed code, plus using the scanner built into the phone.

Sources

  • Denso Wave, QR Code Standardization, retrieved 2026-08-30, https://www.qrcode.com/en/about/standards.html
  • Denso Wave, Error correction feature, retrieved 2026-08-30, https://www.qrcode.com/en/about/error_correction.html
  • Denso Wave, How to create a QR Code, retrieved 2026-08-30, https://www.qrcode.com/en/howto/code.html
  • Denso Wave, Information capacity and versions, retrieved 2026-08-30, https://www.qrcode.com/en/about/version.html
  • IEC Webstore, ISO/IEC 18004:2024, retrieved 2026-08-30, https://webstore.iec.ch/en/publication/99495
  • National Cyber Security Centre, QR Codes – what’s the real risk?, retrieved 2026-08-30, https://www.ncsc.gov.uk/blog-post/qr-codes-whats-real-risk
  • Which?, Scam alert: bogus QR codes continue to target motorists, retrieved 2026-08-30, https://www.which.co.uk/news/article/scam-alert-bogus-qr-codes-continue-to-target-motorists-ansiE0h1LKF0
  • Walsall Council, Car parking QR code scam warning, retrieved 2026-08-30, https://go.walsall.gov.uk/newsroom/car-parking-qr-code-scam-warning
  • HM Revenue and Customs, Check if a QR code on a letter you’ve received from HMRC is genuine, retrieved 2026-08-30, https://www.gov.uk/guidance/check-if-a-qr-code-on-a-letter-youve-received-from-hmrc-is-genuine
  • Apple, Scan a QR code with your iPhone camera, retrieved 2026-08-30, https://support.apple.com/en-gb/guide/iphone/iphe8bda8762/ios
  • Google Account Help, Sign in using QR codes (Android), retrieved 2026-08-30, https://support.google.com/accounts/answer/9283368?hl=en&co=GENIE.Platform%3DAndroid
  • Phys.org, QR codes and other tech are frustrating older customers, retrieved 2026-08-30, https://phys.org/news/2026-04-qr-codes-older-customers.html
  • Petkovic, Nanu and Mistry, Unlocking loyalty: How digital ease of use shapes memorable experiences and satisfaction for older adults in hospitality, Journal of Hospitality and Tourism Insights, 2026, retrieved 2026-08-30, https://doi.org/10.1108/jhti-10-2025-1223

About the author

Ali Shahi

Ali Shahi is the founder and director of Upd8All Limited. He is a systems engineer with more than three decades in software, including nearly eight years building public key infrastructure systems. He started Upd8All in 2022 after watching customers crowd a fast-food counter waiting for orders, with no way to know when theirs was ready.