In brief
A loyalty card app is one of three things: an app that stores other businesses' cards, an app a chain builds for its own program, or an app a loyalty provider hands its merchants. Most local businesses need none of them, because every install is paid for in sign-ups lost at the counter.
Three different questions, one phrase
“Loyalty card app” is searched by people who want three unrelated things, and the answer is different for each.
A card-storage app. A customer with eleven plastic cards in a drawer wants one place to keep them. These apps photograph or scan an existing barcode so it can be shown at a till. They are a filing cabinet, not a program.
A chain’s own app. Starbucks, Nando’s, Greggs. The app is the program: ordering, payment, and rewards in one place. It works because those customers visit weekly and the app does more than count.
An app a loyalty provider gives its merchants. You subscribe, your customers download the provider’s app, and your program appears inside it next to other businesses’. This is the option most local businesses are actually being sold.
Only the third is a decision you have to make, and it is really a question about friction.
What an install actually costs
Every step between “I’ll have that” and “I’m on the card” loses a share of customers, and those steps are paid at the busiest moment of the transaction.
| Format | What the customer does | Where people drop out |
|---|---|---|
| Browser card | Scans, taps once | Rarely — there is one step |
| Wallet pass | Scans, accepts a prompt | At the prompt, while a queue waits |
| Provider’s app | Store search, download, account, open | At every one of those four |
| Your own app | The same four, for one shop | The same four, plus “for a café?” |
Nobody has to be persuaded that an app is more capable. The question is how many people complete four steps while somebody is waiting behind them, and the honest answer is: fewer than complete one.
When an app is genuinely the right call
This is not a page that concludes “don’t build an app” for every reader.
When visits are weekly or more. Frequency is what earns an icon on a home screen. A customer who comes twice a year will delete it, and should.
When the app does more than loyalty. Ordering ahead, paying, booking, table service. Loyalty rides along on an app that already had a reason to exist — it does not justify one on its own.
When you have many locations. A chain has both the volume to amortize the build and a real problem the app solves: one identity across every site.
When you need a push channel. An app can notify freely. A browser card cannot at all. A wallet pass sits between the two — a changed stamp count can surface on a lock screen, but you cannot write a message into it — so if what you need is to send something you choose, an app or email and SMS with consent you collected properly are the real options.
If two or more of those describe you, an app is a reasonable investment. If none do, it is a cost with a conversion penalty attached.
What to check before signing up to a provider’s app
If a provider’s model is “your customers download our app”, the questions that matter are not on the feature list.
- How many taps from poster to joined? Have someone who has never seen it try, and time them.
- Does the customer need an account before the first stamp? A sign-up wall before any value is where most abandonment happens.
- Whose brand is on the app? In a shared app your program is one of many, and the download is being asked for on behalf of the provider.
- What happens on an old phone? A large download on a five-year-old Android is a real barrier for a real share of your customers.
- Can you export your customer list? Ask before you need it, in writing.
- What does the customer see if they decline the download? For many providers, the answer is nothing, and that customer is simply lost.
The mechanic does not depend on the format
A stamp card counts visits and pays a reward at a target. That works identically in a browser, in a wallet pass, and in an app. Nothing about the loyalty program itself requires a download.
What changes with format is only who is willing to start. So the format question is worth answering with the number that matters — how many of the people who were offered the card are now on it — rather than by comparing capability lists.
The NeoLoyal approach
NeoLoyal has no app, on purpose. The customer scans the QR poster at your counter and the card opens in their phone browser, where it stays in their NeoLoyal wallet alongside cards from other businesses. There is no store download and no account to create before the first stamp.
Customers who want the card closer to hand can add it to Apple Wallet or Google Wallet from a button on the card, and the pass updates itself as stamps are recorded. That is offered on top of the browser card rather than instead of it — see loyalty cards in Apple and Google Wallet for what the pass changes and what the extra prompt costs you.
Authorized staff issue every stamp and confirm every redemption, so the count records visits your team actually saw.
If you run a chain, need push notifications, or want ordering and payment in the same place as rewards, an app is the right shape of tool and NeoLoyal is not it.