The printed square stays; the destination behind it does not have to.
Guides
QR Code Guides
Operational guides for people who print QR codes in quantity — what you can change after the run, how big the code has to be, how to turn a spreadsheet into a managed batch, and what a scan number actually means.
Printing
Decisions to make before the press runs, and what you can still change afterwards.
When a printed code can be repointed, and when the press has to run again.
Independent but fixed, against managed but editable. Neither always wins.
Distance sets the size. Everything else decides whether that size survives.
Everything between the artwork and a code somebody can actually scan.
Bulk workflows
Spreadsheet to production batch, and keeping the batch under control.
Formula, add-on or CSV export — and what each one costs you later.
A spreadsheet with 300 rows is not 300 production-ready QR codes.
Creating 300 codes is easy. The job starts once they are on physical assets.
Pausing is reversible; the destination and scan history stay, and the redirect stops until you switch it back on.
Tracking
What a scan number actually is, and what it is not.
Per-code scan attribution, with the coverage and bot context left visible.
Two measurement layers, one taxonomy, and why the two numbers never match.
A scan event is not a person, and a coverage gap is not a zero.
Cost and plans
What a QR code costs once printing, reprints and staff time are in the same sum.
The square is free. The thing that has to keep working afterwards may not be.
Reliability
Why printed codes stop working, and which layer failed.
Six layers have to keep working. Which one actually broke?