A tea estate in Sri Lanka's hill country, season by season
One code on the pack opens whichever season's tea is current, the factory-visit form and the estate's story: changed in the editor, never reprinted.
An example of how a business like this could use QRiva — not a customer story.
A small estate grows, withers and rolls its own tea, and sells packs at its factory shop and to a few shops abroad. The packs are printed once a year; the tea in them changes through the year.
- January
The new packs
Each pack design carries one dynamic code. It opens a page about the estate: the elevation, how the tea is made, and the current season's tea at the top.
QR codes - February
The season's first picking
When the new tea is ready, the top of the page changes: tasting notes, the picking month, how to brew it. Packs already on the shelves show it the same day.
Hosted page - April
Factory visits
A form on the page for visits to the factory: date, number of people, language of the tour. The estate gets an e-mail with each request.
Forms - June
Where the packs are opened
Analytics shows the countries and cities packs are scanned in: the factory shop, and the shops abroad that stock them.
Analytics - August
Another season, the same pack
The page changes again for the next tea. The pack doesn't.
Hosted page - October
Requests to follow up
Leads holds the visit requests and trade enquiries, each with a status and a follow-up date. A CSV export goes to whoever handles the shops abroad.
Leads - December
Before the next print run
Each pack design has its own code, so Analytics compares them before the packaging is reordered.
QR codes
What it takes to set up
- — One page for the estate, with the current season's tea at the top (Starter: up to three pages).
- — One dynamic code per pack design, printed with the pack (Starter: 25 dynamic codes and print-ready PDF files).
- — A visit-request form; every response lands in Leads.
- — Starter shows 90 days of analytics, enough for one season at a time; Pro shows a full year side by side.
More use cases
Bookshop
A bookshop in Kyoto: a playbook for an author eveningCeramics studio
Three codes at a ceramics studio in Fes
Try your own version
Start free with one dynamic code, a page, a card and a form. Upgrade when the use case needs it.