Dynamic QR code

Static versus dynamic

A static QR code has the destination encoded directly into the printed pattern. Scan it and the phone reads the URL out of the pattern itself. It is free, permanent, and works forever — and it can never be changed or measured.

A dynamic QR code encodes a short redirect URL you control. The phone hits that redirect, which forwards to wherever you currently point it. The printed pattern never changes; the destination can change any time.

That single difference is what makes a QR code a business asset rather than a printed guess.

What dynamic buys you

You can change the destination after printing. The seasonal promotion ends, the landing page moves, the booking system changes vendors — you update the redirect. Five hundred already-printed cards and three vehicle wraps keep working.

You get measurement. Scan counts, timing, rough location, device type. Without this, printed material is the last channel in your business with no feedback loop at all.

You can distinguish placements. A separate code for the counter, the truck, and the receipt insert tells you which one actually works — see physical-to-digital attribution.

Mistakes stop being permanent. A typo in a static code on a vehicle wrap is a reprint. In a dynamic code it is a two-minute fix.

The dependency you are accepting

Dynamic codes route through a redirect service. If that service disappears, raises prices, or goes down, every printed code stops working.

This is a real risk and it is manageable:

• Prefer a redirect on your own domain (yourdomain.com/r/truck) over a third-party short domain. If the provider changes, you repoint your own URLs and the printed codes are unaffected. This one decision removes most of the lock-in — see platform lock-in.
• Check what happens if you stop paying. Some providers disable codes entirely. Ask before printing five thousand of anything.
• Keep your own record of which code points where. Do not let that map exist only inside a vendor’s dashboard.

Practical rules for codes that actually get scanned

• Say what happens. “Scan to leave a review” outperforms a bare code substantially. People do not scan mystery squares.
• Size for scan distance. The rough working guide is a minimum width of about 1/10th of the scanning distance — roughly 0.8 in at arm’s length, and considerably larger on a vehicle or a sign read from across a parking lot.
• Keep quiet zone clear. QR codes need clear margin around them — about four modules’ worth. Crowding the code against other artwork breaks scans.
• Maintain contrast, and do not invert. Dark code on light background. Light-on-dark fails on many scanners.
• Test the printed piece, not the screen proof — on more than one phone, in the lighting where it will actually live.
• Send scans to a purpose-built QR landing page, not your homepage. Someone who scanned has already decided to act; give them one obvious thing to do.

What to measure

Scan counts alone are vanity. The number that matters is scan-to-conversion rate — the share of scans ending in the outcome you wanted.

A code with 40 scans and 12 reviews is outperforming one with 300 scans and 4. Without campaign tracking and conversion tracking wired through to the landing page, you cannot tell those two apart.