Print the code once, change where it points forever.
A QR code goes on a van, a leaflet, a site board. Once it is printed it is fixed forever. But where it should point is not fixed at all. Offers change, pages move, campaigns end.
Reach for a free QR generator and you have quietly handed control of that redirect to someone else. The owner of the generator can drop an advert in front of your destination, start charging, or simply let the code expire once your leaflets are already out in the world. The print is permanent, and so is the dependency.
I built an in-house redirect system. The printed code never changes. Where it points can change as often as you like. Nothing sits between the scan and the destination: no holding page, no advert, no third party. The redirects are temporary by design, so a phone never caches an old destination and keeps sending people somewhere you have moved on from.
It outputs in vector and raster for any print size, with high error correction so a code still scans when it is scuffed or small. Scans are counted with a daily hash, so you get real numbers without identifying anyone. And it is host-aware from the first line, so a code can be served from your own domain rather than mine.
One detail I am glad testing caught: the quiet zone, the white border around a code, had been built to a quarter of the width the specification calls for. On screen it scanned perfectly. On a printed leaflet it would have failed. The kind of defect that only shows up in the real medium, fixed before anything went to print.
The system is live and in use. Codes already out on physical materials can be repointed at any time, from one place, without reprinting a thing. Control of where every code leads stays with the practice, for the full life of the print run.
Honest scope: an internal build for my own practice. The result to point to is control retained, not a headline conversion number.
The easy read is that you need a QR code. The real question is who controls where it points once the thing is printed and out of your hands. That is the friction worth solving, and it is why I built it owned, not borrowed.
The other half of the job was testing against the real medium, not the screen. A code that works in a browser and fails on a leaflet is worse than useless once ten thousand are in the post. Building it solo, AI-leveraged, is what made a system this specific worth doing rather than settling for a generator that owns your codes.