Loyalty Cards: How Reward Cards Work for Retailers

Picture a fuel retailer with 120 stations, a plastic card programme that has run for a decade, and a CRM team that can tell you how many points were issued last quarter but not which customers stopped coming in March. That is the situation behind most of the loyalty card conversations I have. In the UK alone, "loyalty card" is searched over 13,000 times a month, and a good share of that comes from retailers rethinking the format.

If you run loyalty, CRM or digital for a retail, QSR, fuel or fashion brand with 50 or more locations, "plastic or app" is no longer the real decision. What you are really choosing is the mix of card formats that gives you a fast launch and clean data without burying your IT team. Physical cards, mobile wallet passes, standalone apps and SDK-based cards inside your existing app all do the same job. They just do it very differently.

Below I cover what happens behind a loyalty card, where the four formats differ, and how I would pick between them in markets as far apart as the UK, the UAE and Sri Lanka. If you want the wider picture on programme design first, start with our guide on what a loyalty programme is.

What happens when a loyalty card is scanned

A customer loyalty card links a shopper's identity to a balance (points, stamps or tier status) that you update at every transaction. At checkout the card is scanned or tapped, whether it's plastic, an app or a wallet pass. Your POS or e-commerce system sends the transaction to the loyalty engine, and the engine applies the reward rule in real time.

For that to work reliably, the system first has to recognise the customer. That happens through a barcode, a QR code, NFC or a mobile number. Then it applies the rule: points per euro spent, stamps per visit, or tier status based on spend. Finally it stores the transaction, because that record is what lets you personalise the next offer.

The mechanics matter less than people expect. What counts is whether customers feel the benefit. Programmes that reward clearly and consistently build stronger relationship quality with the retailer than programmes with complicated rules, according to research on loyalty program benefits and relationship quality. I've seen enough programmes with a 14-page terms document to believe it.

Physical, wallet, app or SDK

No single format suits every brand. That's not a hedge: the right choice really does depend on what you already have.

Physical cards, plastic or paper, are cheap to produce. They tell you almost nothing beyond the transaction itself, though, and a lost card means reissuing it, which annoys the customer.

Wallet passes in Apple Wallet or Google Wallet live on the phone without an app download. They update automatically and support push-style notifications. Personalisation is limited, and you feel that limit quickly once the programme matures.

A standalone app gives you the full screen: gamification, rich personalisation, your brand front and centre. The catch is that you need marketing budget to get people to download it.

An SDK-based card sits inside an app your customer already has installed. The download barrier disappears, and you keep the gamification and AI-personalisation layer. For brands with a well-used app, this is usually where I'd start.

NeoDay runs all four formats from one back end. A retailer can launch as a standalone app, as an SDK inside its existing app, or on the web, often in as little as 10 weeks, without rebuilding the reward logic for each channel. Our retail loyalty program examples show how different brands have played this.

So if you already have an app with real engagement, go SDK or wallet. If you don't, a standalone app is worth the download effort. Physical cards still have a place, mostly as a bridge.

Rewards and missions

A reward card structure is simply the rule set that turns behaviour into a visible benefit. Points are the default. They award a fixed rate per spend, which customers understand instantly, and which is also why they become a commodity: your competitor offers the same thing.

Stamp or visit-based programmes reward frequency instead of spend. That fits QSR and coffee chains, where basket size barely moves from one visit to the next. Tiers open up better rewards as spend or visits rise. They work well in fashion and fuel retail, where loyalty has an aspirational side.

Gamified missions are the layer I find most interesting. You put challenges on top of any of the above ("buy three times this month", "try a new category") to steer specific behaviour rather than just spend.

They are not a free win, though. A 2026 study on non-monotonic gamification effects found that mission-based mechanics increase repeat purchase intention, but badly designed missions or overly aggressive progress framing can backfire and reduce motivation. Separately, a field study of nearly 19,000 app users found that well-designed gamified mechanics measurably increase engagement over time (Driving Mobile App User Engagement Through Gamification).

My rule of thumb: keep it to two to four active missions per customer at a time. That's what works in most programmes we've seen. Rotate them. Don't stack them.

A question I get a lot is whether customers must link their card before missions work. Not necessarily, but it changes what you can measure. An anonymous scan can earn basic points. Missions ("buy X, get Y") generally need an identified customer, because the system has to track progress across visits. Most retailers ask for a quick sign-up at first use (name, mobile number, email) and then let the card do its work. That's a sensible trade between friction and data quality.

What a loyalty card actually earns you

The discount is the cost. The data is the return.

Every scan is a timestamped, SKU-level record of what someone bought, where and when. Basket composition shows you cross-sell opportunities. Visit frequency flags customers drifting towards churn before they actually stop coming. Segment-level trends let you send personalised offers instead of blanket discounts that eat margin.

How granular is that data? In UK food retail it has become a research tool in its own right. A 2025 narrative review found that supermarket loyalty card data is detailed enough to support dietary and public health research.

On retention, a meta-analysis spanning 40 years of loyalty programme research found that programmes reliably boost behavioural loyalty (repeat purchase) more than attitudinal loyalty (how much customers say they like the brand). The source is the Journal of the Academy of Marketing Science meta-analysis. This should shape your KPIs. Measure visits and basket size, not just satisfaction scores. We go deeper on this in our piece on customer retention and why it matters.

There is also a trust problem, and you should name it plainly. A 2024 UK survey by the National Centre for Social Research found that 97% of shoppers belong to at least one supermarket loyalty scheme, yet many remain sceptical about how loyalty pricing works (Attitudes Towards Supermarket Loyalty Pricing). Simple reward rules are more than good UX. They close a real trust gap.

For the IT lead: scale, integration and who changes campaigns

Can a platform handle millions of QR cards and plug into what you already run? Yes, if it is built API-first. A chain with 50-plus locations will normally have millions of active cards across hundreds of stores. The loyalty program card system has to issue and validate QR or barcode identifiers at that scale. It also has to talk to your POS, CRM, ticketing and marketing systems without custom integration for every store format.

NeoDay is cloud-agnostic and API-centric by design. It connects to the systems you already have instead of asking you to replace them, and data moves between your CRM and the loyalty platform over standard APIs, not batch file transfers. Minimal IT effort is not a slogan here. It is the difference between a 10-week launch and a 10-month one. Before you commit to any platform, insist on API-first integration with your POS, CRM and ticketing.

The other half of this is day-to-day control. In a modern platform, your loyalty and CRM managers should be able to create a mission, adjust a reward tier or launch a seasonal campaign from a dashboard, without waiting for a development sprint. That's what a ready-to-use front end is for. NeoDay is built around this split: the platform supplies the AI-driven personalisation and gamification logic, and your marketing team configures campaigns on top. The same reasoning explains why restaurant loyalty programmes and retail programmes increasingly share the same platform logic, even when the customer experience looks nothing alike.

UK, UAE and Sri Lanka: same platform, different first step

Market context decides which format goes first, even when the platform underneath is identical. Copying one global template rarely works.

In the UK, penetration is already high: 97% of shoppers are in at least one scheme. Getting people to enrol is not the hard part. Standing out is. Wallet passes and app-based gamification tend to outperform plain plastic here.

In the UAE, smartphone and wallet adoption is high across fuel retail and QSR. That makes an SDK-based or wallet-first launch a practical opening move, especially if your app is already on customers' phones.

Sri Lanka is more mixed. Digital maturity varies across regions, and physical and wallet-based cards often still sit alongside a digital rollout. Here I'd launch with a physical card plus wallet, and build the migration path to app or SDK in from day one, rather than going app-only.

FAQ

What is the difference between a loyalty card and a loyalty program card?

In practice they mean the same thing: the credential used to collect and redeem rewards. "Loyalty program card" is sometimes used more narrowly for programmes with structured tiers or missions rather than simple points.

Are customer loyalty cards still worth it if most shoppers already have several?

Yes, but only if yours stands out, through gamification, personalisation or rewards people actually find useful. The research on relationship quality is clear that well-communicated benefits drive loyalty to the retailer. Having a card in someone's wallet does not.

Do loyalty reward cards work better as physical cards or apps?

It depends on what you need from the card. Physical cards launch fast and cheap, but they capture little data. If data and gamification matter to you, and for most 50-plus location brands they should, an app or SDK-based card is the stronger choice. It just takes a bit more setup time.

Can a loyalty platform support both a physical card and an app at the same time?

Yes, and it is common during a migration. NeoDay runs physical, wallet, app and SDK formats on one back end, so you can phase out plastic gradually instead of forcing an abrupt switch.

How long does it take to launch a loyalty card program?

On a platform built for it, a standalone app, SDK or web-based programme can launch in as little as 10 weeks. Timelines stretch mainly when integration with legacy POS or CRM systems turns out more complex than expected.

What data should a loyalty rewards card capture at minimum?

Transaction value, timestamp, location and, where possible, basket composition. That is enough to build frequency-based retention alerts and basic personalisation without invasive data collection.

Does gamification always improve loyalty card engagement?

No. Well-designed missions increase repeat purchase intention, but poorly framed progress bars or overly aggressive challenges can reduce motivation instead. A small number of clear, rotating missions tends to beat a large, complex set.

Sources: Loyalty program benefits and relationship quality, 40 years of loyalty programs meta-analysis, Driving Mobile App User Engagement Through Gamification, Non-monotonic gamification effects, Attitudes Towards Supermarket Loyalty Pricing, Supermarket Loyalty Card Data for Dietary Interventions

More questions about retail loyalty? Find the answers in our loyalty FAQ.