Loyalty programme
A loyalty programme you can explain at the counter
A loyalty programme for a local business defines which action counts, how many visits are needed and what reward customers receive. Iterum lets you configure a stamp card, target and reward, display a QR code for enrolment and have staff confirm visits. Start from your own margins and actual customer frequency: the software records the journey but cannot guarantee more repeat visits.
Updated by Radman Sattari, Founder of Fidus
Choose a rule customers understand
One possible structure is a stamp for each valid visit and a reward at a set target. Describe the reward clearly so customers and staff know when it applies and how it is redeemed.
Do not copy another business's target. A coffee shop and a salon have different margins and visit patterns. Try the rule with staff before displaying it.
Make enrolment easy
The QR code opens a short form with a required checkbox relating to the privacy notice; name and recovery contact are optional. After confirmation customers see the web card without installing an app. At their next visit authorised staff scan it and record the visit.
A clear reward is not enough if counter staff cannot explain the journey. Give staff one simple sentence and check QR readability where customers enrol.
Read the recorded activity
The panel stores visits and redemptions; aggregate analytics depend on the selected plan. Use the records to assess whether target and reward fit your business, without treating every enrolment as a returning customer.
Iterum manages a stamp programme. It does not replace a till or POS and does not attribute new revenue to the campaign by itself.
Frequently asked questions
- Can I change the reward and target?
- Owners configure card rules in the designer; check in the panel how changes affect cards already in use.
- Must customers fill out a form?
- Yes. The enrolment form includes a required checkbox relating to the privacy notice. Name and recovery contact are optional.
- How do I judge success?
- Review confirmed visits and redemptions against your own history; do not infer revenue automatically.