How it works
The code is fixed. The schedule isn't.
Everything below is the whole product. If you've set an alarm on a phone you already understand most of it.
1 · The code
A permanent short link, as a QR.
Each code has a name, a short slug, and a fallback destination. The slug is what's encoded in the QR, so it's chosen once and then locked. The fallback is where people land when no rule applies, and it can't be empty, because a printed code has to point somewhere.
Download it as SVG for print, which scales to any size without going soft, or as a 2048-pixel PNG. Error correction is set high, so a logo in the middle or a smudge on the corner doesn't stop it scanning.
2 · Rules
Where it points, and when.
A rule is a destination and a time. The time can be a simple window with a start and an end, or no end at all. It can repeat every day between two times, or only on certain days of the week. A window that ends before it starts, like 11pm to 2am, crosses midnight, and that's fine.
When two rules are active at the same moment, the higher priority wins. When none are, the fallback does. If two rules overlap at the same priority the app tells you, because that's the one case where nobody can predict the answer.
Rules are checked at the moment of the scan, in the timezone you set on the rule. A code printed in Austin and scanned in Tokyo still does what Austin meant.
3 · Scans
Not just how many. Where they went.
Every scan records which rule was active, so you can answer "what were people actually sent to in March" rather than only counting them. You also get scans per day, by device, and by country when that's known.
There's a preview, too: pick any date and time and see where the code would send someone. It's the same calculation the scan uses, so it's never a guess.
Also
Teams, domains, and leaving.
Codes belong to a workspace, so a team can share them. Owners invite by email; members can do everything with codes and nothing to the workspace.
A workspace can verify its own hostname with two DNS records and print codes under it. Until both records check out, the app keeps printing with its own host, so a QR never carries a hostname that resolves to nothing.
If you leave, your codes are archived rather than deleted. Anything already printed shows a short retired message instead of an error page.