Skip to content

A craft brewery in Ghent: one coaster code for the whole week

The tap list in the evening, tour bookings on Saturday morning, and a closed-day page that still shows the hours and the bottles.

ExampleQR codesSmart routingHosted pageBookingsAnalyticsNeeds the Pro plan or above

An example of how a business like this could use QRiva — not a customer story.

A small brewery runs a taproom beside the brewhouse, open four days a week. Its coasters and table cards carry one code; what it opens depends on the day and the hour, in the brewery's own time zone.

What the code opens, by day and time
TimeMonTueWedThuFriSatSunThe code opens
16:00–23:00TapsTapsTapsTaps tonight — Page with the beers on tap, each with its style and strength
10:00–13:00ToursTours on Saturday — The brewery tour booking form
13:00–22:00TapsTapsTaps this weekend — The same tap list page
Any other timeClosedClosedClosedClosedClosedClosedClosedClosed now — Page with the opening hours, the bottle list and directions
  • One dynamic link with routing rules on weekday and hour, in the order above: Wednesday to Friday with the hour between 16 and 22 → the tap list; Saturday between 10 and 12 → the tour booking; and so on. Rules work in whole hours, the first one that matches wins, and anything else goes to the closed-day page.
  • The tour booking is a form with a booking field: Saturdays only, hour-long tours from 10:00, with a capacity per tour. Booking fields come with Pro.
  • The tap list is a hosted page with a menu block. When a keg runs out, its line comes off; the coaster stays the same.
  • Analytics' weekday-by-hour heatmap shows when people actually scan, which is worth a look before changing the opening hours.

Worth knowing. Routing follows the clock, not the taproom: if the taproom closes early on a quiet Wednesday, the code shows the tap list until 23:00 unless someone changes the rule. Changing it takes a minute, and nothing is reprinted.

More use cases

Try your own version

Start free with one dynamic code, a page, a card and a form. Upgrade when the use case needs it.