Step 1
A library that scales with the roster
Folders nest, codes move between them in bulk, and the library filters to whatever you're working on. A new client is a new folder and a CSV import — their whole first campaign stood up in one pass.
Solutions · For running codes on behalf of clients
QR codes for agencies & franchises
Running codes for clients means two audiences at once: the client wants a clean number every Monday, and your team wants the library not to become a junk drawer by the third campaign. Both are organisational problems before they are QR problems.
The structure that works: a folder per client, subfolders per campaign, campaign tags on every code so scans attribute to the placement that earned them — and the scan report as a PDF that goes straight into your Monday email, unedited, because it was designed to be read by someone without a login.
The playbook
Step 2
Attribution the client can read
Tag each code with source, medium and campaign; the statistics slice by those tags, and the tags snapshot per scan — so retagging next quarter never rewrites this quarter's report.
Step 3
The Monday PDF
The scan report covers any period the plan allows, per folder — scans, unique visitors, cities, devices, hours, and which codes moved. It's a document, not a dashboard invite, and it forwards without you exporting anything by hand.
Built with:FoldersScan reportsCSV importAll features →
Questions this buyer asks
Can my team share access without sharing a password?
Yes — invite teammates with roles (admin, editor, or view-only) on Scale and above. Everyone gets their own login, and viewers can see everything without being able to repoint a client's printed code.
Can each client have their own branded domain?
A workspace carries one branded domain (Business and Enterprise), so an agency printing under one house brand fits today. Per-client domains would mean a workspace per client — tell us if that's your shape and we'll say honestly where that sits on the roadmap.
Nearby jobs
For labels that outlive vendors
Manufacturing & field equipment
A machine label is printed once and read for fifteen years. That code cannot depend on anyone.
Built with:Static codesDynamic repointingPrint-ready exports
See the playbookFor the menu on the table
Restaurants & cafés
The laminated code on every table keeps working while the menu behind it changes daily.
Built with:Dynamic repointingStatic codesFoldersScan analytics
See the playbookPrint it once. Change it whenever.
Unlimited static codes on every plan. Dynamic codes you can repoint after printing, and every design feature on every tier.