Strip the marketing away and a dynamic QR code is one idea: the code you print and the place it leads are two separate things, connected by a link you control. The grid on the poster encodes a short URL. That URL belongs to a redirect service. Where the redirect sends people is a setting — yours to change, any time, without touching the poster.
The mechanics, in one scan
A customer points their camera at the code. The camera reads the short URL out of the grid — say, go.qr-m.in/aB3xY9z — and opens it. A server answers with “the place you want is over there,” and the phone lands on your menu, your listing, your video. The whole detour takes an imperceptible fraction of the page load, and it happens at a network edge near the scanner rather than in one distant data centre.
What the redirect makes possible
Editability is the obvious win — fixing a broken link under ten thousand printed boxes is the story that sells the category. But putting a decision point inside every scan enables much more, and the rest is where the business value usually lives:
- Counting. Every scan can be recorded — when, which city, what device — which is where scan analytics come from. A static code can never tell you whether anybody scanned it.
- Routing. iPhones to the App Store, Androids to Play, one printed code. Schedules that switch a poster off after the event. Scan caps for contracted promotions.
- Gating. A passcode in front of a trade price list; the arrival still counts, the destination waits.
- Identity. The short URL is printed and human-readable, which makes it brand real estate — the reason branded domains exist.
What it costs — both kinds of cost
The money is straightforward: redirects are served infrastructure, so dynamic codes are what QR platforms charge for. Plans here are metered by how many dynamic codes you hold — never by scans, which matters more than it sounds, because several popular tools cap scans on lower tiers and a successful campaign becomes an outage.
The structural cost deserves equal billing: a dynamic code depends on its vendor. If the service behind the short URL disappears, printed codes stop resolving. This is not a reason to avoid dynamic codes — it's a reason to interrogate the vendor. What happens to live codes if you cancel? Can you get a machine-readable map of every printed URL and its destination on the way out? We keep our answers public, and the honest competitors will give you theirs in writing.
When you shouldn't use one
Anything that must outlive every vendor — equipment labels, emergency sheets, a Wi-Fi card taped inside a cabinet — should be a static code: the destination encoded directly in the grid, no service in the middle, working for as long as the paper survives. The full decision rule has its own post; the one-line version is things that inform change, things that identify don't. Static codes are unlimited and free on every plan here precisely because charging for them would push people toward the wrong choice.
Try the mechanics yourself
The fastest way to understand a dynamic code is to make one and repoint it while watching a phone: create one on a free trial, scan it, change the destination, scan again. Or start with the physics — the free generators make permanent static codes with the same renderer, and the size calculator shows why short URLs print better than long ones.