How to Build a Loyalty Program App: Points, Stamps, Rewards and Redemption
How to build a loyalty program app: points vs stamp cards, QR codes at the counter, rewards, redemption, fraud, and when a POS loyalty add-on is enough.
Mythex Team · · 6 min read
A loyalty program app rewards repeat customers: they earn points or stamps when they buy, and swap them for rewards. To build one you need customer accounts, a way for staff to add points or stamps at the moment of purchase (usually by scanning a customer's QR code), a list of rewards, a redemption flow that staff confirm, and a history of every change so balances can be trusted. For most small businesses a mobile-friendly web app is enough; customers do not need to install anything from an app store.
Choose the model first
| Model | How it works | Suits |
|---|---|---|
| Stamp card | One stamp per visit or item; a reward after a set number | Cafes, barbers, car washes, anything with similar-priced visits |
| Points | Points per amount spent; rewards cost different numbers of points | Shops, restaurants, businesses where spend varies |
| Tiers | Customers move up levels (for example Silver, Gold) with more spend and get ongoing perks | Businesses with frequent, high-value customers |
| Paid membership | Customers pay a fee for ongoing benefits | Businesses with loyal regulars and clear perks |
Start with the simplest model that fits. A digital stamp card can be built and understood in a day. Tiers and paid memberships add rules that are harder to explain and to build; a paid scheme is closer to a membership site.
Decide also:
- Earning rules. Per visit, per item, or per amount? Do discounted purchases earn?
- Expiry. Do points or stamps expire, and when? Check local consumer rules if you let rewards expire.
- Rewards. What can customers get, and what does each cost?
- Locations. One shop, or several sharing the same program?
What the app needs
Data
| Table | Key fields |
|---|---|
| Customers | Name, email or phone, QR code token, joined at, current balance |
| Transactions | Customer, type (earn, redeem, adjust, expire), points or stamps, purchase amount, staff member, location, created at, note |
| Rewards | Name, cost in points or stamps, active yes/no, description |
| Staff | Name, login, location, role (staff, manager) |
| Locations | Name, address — only if you have more than one |
The key rule: the balance is the sum of the transactions. Never let anyone overwrite a balance directly. Every earn, redeem and correction is a new row with a staff name and a reason. That history is what lets you answer "why do I only have 40 points?" and catch mistakes or abuse.
Pages
- Customer side: sign-up, a card page showing the QR code and current balance or stamps, available rewards, and history.
- Staff side: a scanner page (camera opens, scans the customer's code), then "add stamp" or "enter amount spent", and a redeem button that shows which rewards the customer can afford.
- Manager side: customers list, adjust a balance with a reason, manage rewards, and a simple report of points issued and redeemed.
Permissions
Customers only see their own card. Staff can add and redeem but not delete history. Managers can make adjustments, always with a note. Staff actions need a staff login; the scanner page must not be usable by anyone who finds the URL. See adding login to your app.
Decisions and trade-offs
How customers identify themselves
- QR code on their phone that staff scan. Fast and hard to fake if the code is a random token.
- Phone number typed in by staff. No phone needed, but easier to misuse and slower at busy times.
- Physical card with a printed code for customers who prefer not to use a phone.
Many small businesses support QR plus phone lookup.
Customer accounts
Asking for a password at the counter kills sign-ups. A sign-up with just a name and email or phone, followed by a sign-in link sent later, is much lighter. Collect as little personal data as you need, and say what you use it for.
Web app or native app
A web app opens from a QR code on the counter and can be added to the home screen. Native apps can add wallet passes, push notifications and location-based prompts, but come with app store costs, reviews and install friction. Our guide on mobile-friendly web apps covers this trade-off in detail.
Connection to your till
If your point-of-sale system has an API, points can be added automatically from each sale. If it does not, staff enter the amount in the loyalty app. Manual entry is fine for low volume but slows down a busy queue, so test it on your busiest hour before launch.
A first prompt that works
Build a digital stamp card web app for Bean There, a two-location coffee shop. Customers sign up with a name and phone number and get a card page with a QR code, their stamps (a grid of 10), and their history. Every coffee earns one stamp; 10 stamps earn a free drink, after which the card resets. Staff log in and use a scanner page that opens the phone camera, scans a customer's QR code and shows their card with Add stamp and Redeem free drink buttons. Every stamp and redemption is saved as a transaction with the staff member, location and time; the balance is always calculated from transactions. Managers can adjust stamps with a required reason and see a weekly report of stamps given and drinks redeemed per location. Mobile-first, warm design, large buttons for staff.
Build steps
- Customer sign-up and card page with a QR code.
- Staff login and scanner that finds the customer and adds a stamp or points.
- Transaction history as the source of every balance.
- Rewards and redemption, confirmed by staff.
- Manager tools: adjustments with reasons, rewards list, report.
- Expiry rules, if any, and the message customers see.
- Counter materials: a printed QR code that opens sign-up.
- Test at the counter. Scan in poor light, scan an old code, redeem with too few points, try adding stamps twice quickly.
Common mistakes
- Storing only a balance. Without transactions, errors and disputes cannot be traced.
- Scanner page without a staff login. Anyone could award themselves points.
- Guessable QR codes, such as the customer's ID number. Use a long random token.
- Too complex to explain. If staff cannot explain the program in one sentence, simplify it.
- Rewards that cost more than they bring. Work out the cost of each reward before launch.
- No plan for lost phones or merged accounts. Give managers a way to look customers up and move a balance, with a note.
When a ready-made loyalty product is the better choice
Many point-of-sale systems offer loyalty as an add-on that ties into every sale automatically, with no extra step for staff. If yours does, it is usually the easiest option. There are also standalone loyalty apps and digital stamp card services for small businesses, some with wallet passes and marketing messages built in.
Build your own when your POS has no loyalty option or charges more than the program is worth, when you want rewards that fit your business exactly, when you want the program tied to other things you run (bookings, online orders, a referral program), or when you want to own the customer list outright.
Building it with Mythex
On Mythex you describe the loyalty app in chat and try it in the live preview, including at phone size. The agent adds a dedicated Postgres database when stamps and transactions need saving (or type /database). Mythex builds web apps; native App Store apps are not available today, so this is a mobile-friendly web app customers open from a QR code. Staff and customer sign-in are added with your own auth approach (add login recipe), and any SMS or email messages go through your own provider.
For inspiration, the dog grooming website template includes a loyalty program alongside services and pricing.
Questions
Points or stamp card: which is better?
A stamp card (buy nine, get the tenth free) is easier for customers to understand and suits businesses with similar-priced visits, like cafes and barbers. Points suit businesses where spend varies a lot, because rewards can scale with how much someone buys.
Does a loyalty app need to be in the App Store?
No. A mobile-friendly web app that customers open from a QR code or add to their home screen works well for many small businesses and avoids app store review and install friction.
How do staff add points at the counter?
Usually the customer shows a QR code from their account, and a staff member scans it on a phone or tablet and enters the purchase amount or adds a stamp. Staff actions should require a staff login.
Can loyalty points connect to my till?
Only if your point-of-sale system offers an API or integration for it. Otherwise staff enter purchases in the loyalty app by hand, which is fine for low volumes but adds a step at busy times.