Restaurant loyalty: a reason to come back.
A guest who visits once does not always return. With Vuelvy they save a benefit for their next visit in Apple Wallet or Google Wallet, your staff validate it and you measure who comes back.
Google shares your name, email and profile picture, if available, to verify your identity. This does not subscribe you to marketing. Privacy policy
Notification and update availability depends on each Wallet platform’s capabilities and policies.
- 01The second visit as the goal
- 02QR enrolment without slowing the till
- 03Simple validation by staff
- 04Apple Wallet and Google Wallet
One main goal: the second visit
A programme that chases more spend, more visits and more reviews at once ends up without a clear rule. We start with the behaviour that matters most in a restaurant: getting someone who came once to return. Spend per visit is reviewed afterwards as a secondary outcome.
- Benefit for the next visit
- Stamps per validated visit
- Conditions visible before payment
- One conversion defined before activation
Two illustrative examples: café and restaurant
These cases show how the mechanic changes with visit frequency. They are design examples, not clients or measured results: the reward and its validity are set around your margin and operations.
- Café (example): stamps per validated purchase and a reward reachable at the usual visit frequency.
- Restaurant (example): a benefit for the next meal, with validity adapted to less frequent visits.
The journey from the first visit to the second
Guests scan a QR code on the receipt, table, counter or booking confirmation and save the pass compatible with their phone. They see the benefit and its conditions. On the next visit they show it, staff validate it and the pass reflects the new status.
- QR code per acquisition point
- Pass with benefit and conditions
- Validation on the next visit
- Source preserved with UTM
Validate without slowing service
We define who confirms a visit and which system is the source of truth: QR or code scan, guided action, POS, bookings or CRM. A POS integration is not always needed; guided validation can be enough to start and keeps the observed action traceable.
- Short staff script
- Verifiable code or QR
- Integration only when it adds value
- Rules for duplicates and errors
Proximity as a reminder, not a guarantee
A saved pass can become relevant again near the venue. Apple decides when to surface it on the Lock Screen and Google can present a nearby alert when permissions and its criteria are met. The activation uses a useful benefit and never promises a guaranteed impression.
- Relevant restaurant location
- Benefit understood on approach
- Separate setup per Wallet
- Permissions and limits explained
How to measure whether they return: window and cohorts
Before launch we set an observation window that fits your visit frequency and group guests by the week or month of their first identified visit. We only compare cohorts that have had the same time to return. An observed redemption does not prove on its own that the programme caused the visit: estimating incremental return needs a comparable group or period.
- Second visit: guests in the cohort who return within the window ÷ guests in the cohort with the full window observed.
- Days to return: time between the first validated visit and the next one.
- Incentive cost: the real cost of redeemed benefits, not their menu price.
- Spend per visit as a secondary outcome, reviewed with margin: more spend is not always more profit.
How we do it at Vuelvy
We analyse your visit frequency, the margin available for the reward and what your staff can validate during service. We configure the pass, enrolment and validation, test it with the team and review results by cohort. Select “Start Wallet Marketing”, tell us about your case and we will contact you by email.
- Frequency, margin and operations analysis
- Reward and journey design
- Launch and validation with the team
- Results reviewed by cohort
FAQ
Frequently asked questions
Which loyalty card works best for a restaurant?
It depends on visit frequency, margin and the team's ability to validate usage. With the second visit as the goal, Vuelvy helps choose stamps or a next-visit benefit and keeps its conditions visible on the pass.
Does the diner need to download an app?
They do not need a proprietary restaurant or Vuelvy app. They open a link or QR code and save the compatible pass in Apple Wallet or Google Wallet, subject to their device availability and configuration.
Where should the enrolment QR code appear?
It can appear on the receipt, table, counter, booking confirmation, takeaway order or landing page. Each source should be measured separately without adding steps at the busiest point in the service.
Does the restaurant POS need an integration?
Not in every case. Guided code or QR validation can support a complete initial operation; the POS, booking system or CRM is connected when it reduces manual work or improves a conversion that is already defined.
Can the card appear when a customer is nearby?
Yes, using relevant locations. Apple and Google control final presentation based on permissions, settings and their own criteria, so Vuelvy verifies the use case without guaranteeing every nearby event becomes a viewed alert.
How do you prove the programme brings customers back?
We measure the share of each cohort of identified first visits that returns within a window set before launch. A recorded redemption proves a visit, not that the programme caused it; estimating the incremental effect requires comparison with an equivalent group or period.
Let’s discuss your case
Does Wallet make sense for your business?
Tell us about your case and we will contact you by email to review integrations, the activation plan and the next step. No generic deck and no commitment.
Google shares your name, email and profile picture, if available, to verify your identity. This does not subscribe you to marketing. Privacy policy