One code on the table, a different offer every few hours
Lunch menu at noon, a seniors' afternoon, a students' early evening: smart routing by weekday and hour.
ExampleQR codesSmart routingHosted pageAnalyticsNeeds the Pro plan or above
The restaurant prints one code per table. What it opens depends on the day and the time, in the restaurant's own time zone.
| Time | Mon | Tue | Wed | Thu | Fri | Sat | Sun | The code opens |
|---|---|---|---|---|---|---|---|---|
| 11:00–15:00 | Lunch | Lunch | Lunch | Lunch | Lunch | Lunch menu — Two-course set lunch page | ||
| 15:00–17:00 | Seniors' | Seniors' | Seniors' | Seniors' | Seniors' afternoon — Page with the 65+ offer and its coupon code | |||
| 17:00–19:00 | Students' | Students' | Students' | Students' | Students' early evening — Page with the student offer and its coupon code | |||
| 10:00–14:00 | Weekend | Weekend | Weekend brunch — Brunch menu page | |||||
| Any other time | Full | Full | Full | Full | Full | Full | Full | Full menu — The everyday menu page |
- One dynamic link with routing rules on weekday and hour: weekday is Monday to Friday and the hour is between 11 and 14 → the lunch page, and so on down the list. Rules work in whole hours. The first rule that matches wins; anything else goes to the full menu.
- Each offer is a hosted page with a menu block and a coupon block: the offer, the code to show the waiter, the terms, the end date.
- Analytics' hour-by-day heatmap shows whether the seniors' afternoon is actually filling the quiet hours.
Worth knowing. The coupon is shown to the guest, not issued to them: the waiter checks the student or senior card at the table. Everyone sees the same code, and QRiva doesn't count who used it.
More use cases
Appliance repair
From repair ticket to the customer who calls you firstAir conditioning
Selling the second year: maintenance from a code on the unit
Try your own version
Start free with three codes, a page, a card and a form. Upgrade when the use case needs it.