How I make a QR code sign for a local business

A QR code sign looks simple until it is on a counter, window, table, or wall. I judge it from the distance where the customer stands.

I start with the destination and the physical location. If either one is fuzzy, the sign usually turns into a generic square that people ignore.

Pick one job for the sign

A sign needs one destination

I make the sign do one job: open the menu, collect a review, show a booking page, load a form, or send someone to a product page. If the sign needs five instructions around it, I split the workflow into separate signs.

For a permanent sign, I usually use a dynamic QR code. The printed square can stay in place while the destination changes from a menu to a seasonal offer, updated intake form, or new review page.

For a temporary event sign, static can be fine. I still use a short destination URL because a dense QR code is harder to scan on a glossy poster, window cling, or signboard.

Design around scanning distance

The viewing distance decides the print size

A counter sign can be smaller because the phone is close. A wall sign, window sign, or queue sign needs a larger code because the customer scans from farther away and may be moving.

I keep the code away from folds, frames, screws, reflections, and busy backgrounds. DENSO WAVE documents the quiet zone as a clear margin around the QR symbol. I treat that margin as part of the design.

I also avoid putting the code at the bottom edge of a sign. People crop files, trim boards, tape corners, and put holders in front of the lower edge. The code needs room to survive the real installation.

Use plain copy

Say what the scan opens

The text next to the code should answer one question: what happens after I scan this? I use lines like Scan for today's menu, Scan to book your appointment, or Scan to leave a Google review.

I let the sign carry the message. The QR code still needs a headline, a short instruction, and enough contrast for someone walking past it.

If I need campaign reporting, I put UTM parameters on the destination URL before generating the QR code. Google Analytics documents custom campaign URLs for identifying campaign traffic. I keep the final encoded URL short enough that the QR code stays easy to scan.

Proof the installed sign

The final test happens on location

I print or proof the sign at final size, then scan it from the likely customer position. For a counter card, that is arm's length. For a window sign, it might be outside the glass in daylight.

I test with mobile data too. A QR sign on a storefront or event wall has to work for customers outside the business Wi-Fi.

If the scan opens slowly, lands on the wrong page, or needs pinching before the next action is clear, I fix the destination before printing more copies.

A good QR code sign has one clear job, enough margin, a readable instruction, and a destination that still makes sense after the customer scans it.