Loyalty formats guide
Loyalty App, Wallet or Card for Your Restaurant?
A loyalty app makes sense when guests need your own interface with several actions and content, while a Wallet card covers showing membership and checking program data. A physical card remains an option for guests who want membership without a phone. Base the choice on how a guest joins, how staff recognise them and how a reward is applied to a bill. Whatever you choose has to match your till and your reward rules.
Separate the card format from how the program works
Make the decision through a concrete visit. How does a guest access the program, how do staff recognise them and how is the reward applied to the bill? Showing a card on a phone answers only part of that.
A membership card displays a member's identity or data. The loyalty system holds the rules, balance and activity. The POS processes the purchase. These roles can be connected in different ways, depending on the supplier and the agreed scope.
In a simple setup, an employee may record the visit separately. In a connected setup, the data comes from the till. Check what a specific offer includes: automatic purchase calculation, manual perks or a combination of the two.
It also matters whether the system can recognise a refund. A nicely designed card will not correct points after a voided bill on its own.
Compare a physical card, a Wallet card and your own app
| Format | When to consider it | What to check before ordering |
|---|---|---|
| Physical card | A guest needs identification without a phone, or you want an alternative to digital membership. | The type of tag or code, the reader, how the card links to the member, and how a lost card is issued or replaced. |
| Wallet card | A guest needs a membership badge and selected program data available in their phone wallet. | Adding and updating the card, supported devices, how it is read, and how it connects to the till. |
| Branded app | You need your own interface for several screens, content and agreed guest actions. | Sign-in, features, app store accounts, release, updates and support. |
These are criteria for a conversation with a supplier, not a complete list of what each product can do. An app and a Wallet card can be part of the same solution when there is a reason and the technical support for it.
Ask for a demonstration of what you actually need. If you need a points balance, a reward list and a way to sign in, walk through those actions. Do not base the choice on a feature screen you never intend to use in the restaurant.
What can Wallet do without a separate app?
A guest can add a card to Apple Wallet without installing a companion app. Apple supports distribution over the web and email, as its official Wallet guide explains.
Google's documentation for loyalty cards likewise describes issuing through an app or a link, for example on the web and in email. That lets you offer card adding without building a separate screen in your own app.
You still need to agree who issues the card, where the balance lives and how it is updated. Ask what a guest sees when they change phones, delete the card or lose access to their membership account.
Do not compare offers by whether the word "Wallet" appears. Check whether they include administration, reward rules, purchase processing, support and the maintenance of links to your systems.
QR scanning and NFC need different checks
A QR code is shown to a scanner or camera. With NFC, data is passed by tapping the device on a compatible reader. Contactless payment at a terminal is not sufficient proof that the terminal will process your loyalty card.
Google Smart Tap requires a compatible terminal and a configured card. For Apple's contactless loyalty implementation, check the terminal's VAS support, the POS software and the integration terms.
Before an offer, record the device model, POS supplier and reading method. Test on the equipment staff will actually use, including the guest's phone screen and the real lighting behind the bar.
If the process fails, it must be clear whether staff may find the member another way or should call a manager. Agree the fallback procedure in advance, together with who is authorised to intervene manually.
Ask for a demonstration of the whole transaction
For the test, prepare one qualifying bill, a bill with an excluded item and a bill with a reward. Then add a refund and a dropped connection. This is a practical scope test, not a demand that every supplier run the same internal model.
| Step | What you need to see or clarify |
|---|---|
| Guest identification | How staff confirm they are working with the right member. |
| Purchase record | Which transaction, location and items enter the calculation. |
| Reward accrual | When the balance changes and where the confirmation appears. |
| Reward redemption | Which conditions apply and how the benefit links to the bill. |
| Interrupted payment | What happens to a reward that was prepared but not used. |
| Refund or void | How accruals are corrected, including partial refunds. |
| Duplicate purchase message | How the same transaction is prevented from being recorded twice. |
Also check a purchase at another location. It needs to be clear whether the same benefits apply everywhere, and who resolves a mismatch between the member's view and the till.
Automation depends on the data available, permissions and supplier access. These are questions for an integration review of your business systems, before you confirm a price and a timeline.
Rollout covers staff, data and maintenance
Decide who in your team approves the rules, who maintains the content and who reports errors. Give staff a short instruction for a typical purchase and the few exceptions that appeared in testing.
In a limited pilot, record failed scans, manual interventions and bills that were not linked correctly. Before scaling, align the reward display with the purchase examples you selected. That way you can assess the system and the clarity of the offer for guests separately.
For data, decide what you need and for which purpose. GDPR governs the legal basis, transparency, data necessity and guest rights. An operating system's notification permission is a technical setting; do not treat it as the legal basis for every marketing use.
The offer should also clarify administrator access, data export, integration maintenance and the process if the relationship ends. For a branded app, agree who is responsible for releases and updates. The wider process is covered by the guide to mobile app development for businesses.
Compare cost through an equal scope. Does the quoted price cover only the card, or also the connection, staff onboarding, support and later changes? Without those answers, two monthly prices may represent different services.
Check the format against your own till
For Balance Brunch & Bakery in Zagreb, Novero delivered a branded iOS and Android app with points, rewards and a Remaris POS integration. That does not confirm compatibility with any other till. Wallet and physical cards are assessed as a separate possible scope.
For a first conversation, prepare your POS name, the number of locations, the identification method you want and a list of guest actions. Book a Novero Loyalty demonstration and walk through one purchase with a reward and its refund.