Routing by Time and Place: Making One Code Do the Work of Ten
A printed code does not have to be dumb. With a few rules behind it, the same square can show the right thing depending on the hour, the day or the date, without anyone lifting a finger.
A printed code does not have to be dumb. With a few rules behind it, the same square can show the right thing depending on the hour, the day or the date, without anyone lifting a finger.
There is a moment every business with a code eventually hits. The code works, people scan it, and then you realise the thing it points to is only right some of the time. The breakfast menu is wrong by lunch. The event page is stale the day after. The holiday hours are misleading in January. You could keep changing the link by hand, and remembering to, or you could let the code change itself.
A dynamic code leads to a destination you control. The next step up is a destination governed by rules: not a single fixed answer, but a small set of conditions that decide where a scan goes at the moment it happens. Scan before eleven and land on breakfast; scan after five and land on dinner. The rule does the choosing, every time, forever.
The printed square is exactly the same in every case. There is nothing different about the ink at nine in the morning and nine at night. All the intelligence lives behind the code, in the rules, which is precisely where intelligence belongs: in the part you can change, not the part you already committed to paper.
The most useful conditions are the most ordinary ones: the clock and the calendar.
The point is not that a code can change. It is that it can change on schedule, so you set it once and stop thinking about it.
You could achieve some of this manually, swapping the destination each morning and evening. The trouble is that manual work is work, and work gets forgotten. The morning you are ill, or busy, or away, is the morning the code shows the wrong menu to every customer. A rule does not call in sick.
There is a deeper benefit too. Routing lets you prepare the future in advance. The code for an event next month can already know what to show on each day of it, set up once, weeks ahead, while you think about other things. You are not reacting to time passing; you are instructing the code once and letting it handle the calendar on your behalf.
Yes, with a dynamic code governed by rules. You can set it to show a breakfast menu in the morning and a dinner menu at night, or a weekday page and a weekend one, and the code chooses the right destination automatically at the moment of each scan.
Most usefully the time of day, the day of the week and specific dates, with a default destination underneath for when no rule applies. That lets one code serve mealtimes, weekends, launches or the stages of an event, all on schedule.
Manual switching is work, and work gets forgotten; the morning you are away is the morning the code shows the wrong thing. A scheduled rule runs on its own, and it lets you set up future dates in advance rather than reacting as they arrive.
No. The printed square is identical at every hour of the day. All the logic lives behind the code in the rules you set, so the ink you committed to paper never has to change.
Free while in beta, with no card required. Design a branded QR code, route each scan by day or time, and never reprint.
Get started free