A regional burger chain with about 45 locations spent roughly $180K building a branded mobile app. Six months later, only a small single digit percentage of customers had downloaded it, and around 1% were active monthly users. The app sat in the App Store with very little use.
Then they launched a simple Apple Wallet and Google Wallet loyalty stamp card. Within 90 days, wallet pass use was attached to well over a third of transactions for enrolled guests. Among those customers, repeat visit frequency was close to 3x higher than the baseline, and average order value climbed by just over 20%, based on the chain's internal data.
This is not an isolated case. We and other providers see the same pattern across the QSR industry.
Quick-service restaurants are learning that the best digital loyalty strategy is not always an app. It is the one your customers actually use. This post explains why wallet passes often outperform app only strategies in QSR, shows typical lift ranges we see behind the repeat visit claim, and breaks down how brands are using wallet based loyalty and promotions to capture revenue they were previously missing.
The app fatigue problem: why QSR customers often will not download your app
The average smartphone user has 80+ apps installed but uses only about 9 or 10 daily. According to data from Adjust and AppsFlyer, roughly a quarter of apps are abandoned after a single use. Many QSR apps fall into this high churn, low usage bucket, similar to other single purpose apps people download for a one off need.
A typical funnel for a mid market QSR app might look like this:
- 100 customers are asked to download
- About 10-15 actually install
- About 4-6 create an account
- About 2-3 are still active after 30 days
In other words, only a small low single digit percentage of customers become retained app users. For a mid size restaurant chain spending six figures on app development, those numbers are brutal.
The problem is not the loyalty concept. The problem is friction. Customers search the app store, wait for a download, worry about storage space, create an account, set a password, grant notification permissions, then remember their login on the next visit. You lose people at every step.
Now compare that to wallet pass onboarding. A customer taps a link or scans a QR code. The pass is added to Apple Wallet or Google Wallet in a few seconds. No separate account creation or password is required for the pass itself. Storage impact is minimal. Friction drops, and in our experience, completion rates are often several times higher than an app download.
The business impact is clear. Unless you have the household name recognition of McDonald's or Starbucks, an app only strategy often creates a loyalty gap. The vast majority of your customers stay unreachable digitally. You build a loyalty program for a small fraction of your base and miss everyone else.
Why wallet passes fit the QSR customer journey
Think about a typical QSR visit. The decision is fast. The dwell time is short. Frequency is high. The average ticket is low. Customers spend 30 seconds to 3 minutes at the counter or drive through. There is no time to fumble with an app login, wait for a loading screen, or navigate menus to find a loyalty barcode.
Wallet passes reduce that friction. With Apple Wallet and Google Wallet, relevant passes can show on or near the lock screen based on location and time. There is no app to open and no separate login to manage for the loyalty card itself.
The loyalty stamp card mechanic fits QSR behavior. It is simple and visual: "Buy 8 burritos, get 1 free." There is no points math and no tier confusion. Wallet stamp cards copy the psychology of the classic punch card and remove the lost card problem that physical versions had for decades.
Wallet passes also create a push notification like effect. Both Apple Wallet and Google Wallet support pass updates that appear on the lock screen when offers change, stamps are earned, or rewards are ready to claim. This is a native capability of the wallet platforms. There is no separate app notification prompt for the pass itself, so you avoid the generic "Allow notifications?" dialog that many users decline.
Location based triggers add another layer. Passes can include store locations so they show automatically when a customer is nearby. This is a simple automatic reminder at the right time and place. That can drive incremental visits in ways that buried apps, email, and SMS often do not.
The mix of instant access, visual simplicity, native updates, and location awareness makes wallet passes a natural tool for the QSR use case.
The data: how wallet passes drive more repeat visits
Here are the numbers we see most often. Aggregated performance benchmarks from QSR wallet pass deployments, from internal data and industry reports where available, tell a consistent story. Exact figures vary by brand, but the direction is stable.
Visit frequency
In many programs we see, wallet pass holders visit roughly 2-3x more often than non enrolled customers. They also visit more often than app only users within the same brand. Part of this is self selection. More loyal customers are more likely to enroll. The format itself also lowers friction and keeps your brand visible.
Offer redemption
Wallet based promotional offers often see redemption rates in the mid teens to mid 20s. That is usually several times higher than many email offers. It is also above what many brands see from generic app push notifications. Because the pass is always present and can show near the point of decision, fewer customers forget to use the offer.
Average order value
Wallet pass users often show double digit percentage lifts in average order value. Two mechanics drive this:
- Customers add items to reach a stamp threshold. For example: one more purchase to earn a free sandwich.
- Dynamic offers on the pass itself, such as "Add a drink for $1 today", influence upsell behavior at the moment of decision.
Retention
Many QSR apps lose a large majority of users within 90 days of install. Wallet passes tend to sit in the wallet until a customer chooses to delete them. This passive persistence gives your program a structural retention advantage.
There is an important caveat. These lifts compare wallet pass holders to non holders or app users, and self selection bias exists. In controlled tests where wallet passes are offered at random to a subset of customers, we still see visit frequency lifts close to 2x for the exposed group versus the control. That points to a real causal impact beyond selection.
In practice, for many QSR programs, a statement like "around 3x more frequent visits among engaged wallet pass users versus non participants" is directionally supported by the data, even though exact lift varies by brand and offer.
Case study: a 60 location taco chain's wallet pass rollout
Consider a fast casual taco brand with about 60 locations across three states. Before the change, the chain used a third party, app based loyalty program that charged per transaction fees and controlled most of the customer data. Only about 6% of customers had enrolled, so about 94% of the base had no direct digital relationship.
Using a pass management platform, the team launched Apple Wallet and Google Wallet stamp cards. Customers could add the pass by scanning a QR code printed on receipts, table tents, and ordering kiosks. Staff used one simple prompt: "Want to earn a free taco? Scan this with your phone." No app download was required.
Over the next six months, according to the brand's internal reporting:
- Pass adoption reached roughly 31% of unique customers, up from 6% app enrollment
- Repeat visit frequency among pass holders was about 3.1x the baseline
- A "Free chips and guac on your 5th visit" campaign achieved about 27% redemption
- The brand saved an estimated $40K per year in third party loyalty platform fees
- The team owned 100% of the customer engagement data for the first time
One tactic stood out. The chain used dynamic pass updates to rotate a weekly "secret menu" item visible only on the wallet pass. This created a sense of exclusivity and gave customers a reason to check the pass regularly. On weeks when the secret item changed, the chain saw around a 14% incremental visit lift compared to baseline weeks.
Wallet pass versus branded app for QSR loyalty
| Branded QSR app | Wallet pass | |
|---|---|---|
| Enrolment friction | App Store visit, download, account creation | One tap from a receipt, SMS, QR code, or POS |
| Who it reaches | Your most frequent customers | Casual customers who will never download an app |
| Offer updates | App Store review cycle | Server-side pass update, live within minutes |
| Re-engagement surface | Push notifications, if permission was granted | Lock-screen pass notifications and location triggers |
| Ordering and payment | Full integration possible | Not supported, a pass is a credential rather than a checkout |
| Best used as | The deep-engagement layer | The top-of-funnel acquisition layer |
Read the table as complementary rather than competitive: the right QSR strategy usually runs both, which is exactly what the top-tier brands do.
Wallet passes as a complement to QSR apps
Top tier QSR brands like McDonald's, Starbucks, and Chick fil A have successful apps with ordering, payment, and loyalty tightly integrated. For these brands, wallet passes are not a replacement. They are a top of funnel acquisition layer for the many customers who will never download the app.
The hybrid strategy is simple:
- Use wallet passes to enroll casual customers into a light loyalty program.
- As engagement grows, use pass updates to promote app downloads with a clear incentive. For example: "You have earned 500 points. Download our app to access exclusive rewards."
This flips the traditional funnel. Loyalty comes first. The app comes later.
Wallet passes also work well for specific campaigns even for app first brands. Examples include limited time offers, event based passes for game day specials near a stadium, seasonal stamp cards, and new location launches. These use cases do not always justify app feature development. They are fast to launch as wallet passes.
There is also an important data link. Wallet passes can generate scan level engagement events. You can see when and where customers use them. You can send that data into your CRM or CDP. That enriches customer profiles even if a customer never downloads your app, and becomes more valuable as third party cookies and mobile tracking identifiers disappear.
Implementation playbook: launching a QSR wallet pass program
If you are ready to move forward, here is a practical five step framework.
Step 1: Define the mechanic
Choose between stamp based loyalty, points based accrual, or pure promotional offers.
- Stamp based programs are best for high frequency, low ticket QSR.
- Points work better for varied menus with upsell goals.
- Pure offers are ideal for new location launches or seasonal campaigns.
Most QSR brands find stamp cards an easy starting point. The psychology is familiar, the concept is clear, and setup is fast.
Step 2: Design the pass
Focus on strong branding, a clear value proposition on the front, minimal text, and a scannable barcode that works with your POS or staff workflow. Both Apple Wallet and Google Wallet have specific design guidelines and field structures. Following them helps your pass feel native next to boarding passes and tickets.
Step 3: Plan your distribution strategy
Use QR codes on receipts, table tents, drive through window stickers, and order confirmation email or SMS. In many pilots, a receipt QR code plus a simple cashier prompt has been one of the most effective channels, often driving adoption rates in the 20-30% range in participating locations. Training staff on a one sentence pitch gets you most of the way there.
Step 4: Integrate with POS and operations
Passes need to be scanned or validated at the point of sale. Integration options include API based scan validation, simple visual verification by staff, or NFC tap.
A key insight: lightweight implementations that use visual checks or a generic barcode can launch in days, not months. You do not need a full POS integration on day one. Start simple and automate later.
Step 5: Iterate with dynamic updates
The strength of wallet passes is real time updates on the customer's device. Plan a cadence of offer rotations, stamp milestone messages, and seasonal refreshes to keep the pass active.
For example:
- A lock screen update when a customer is halfway to a reward
- A new upsell offer each week
- Updated artwork for key seasons
Stale passes get ignored or deleted. Dynamic passes keep attention.
Where this leaves you
The QSR industry runs on repeat visits, speed, and simplicity. Wallet passes support all three in ways that dedicated apps often cannot.
Across many deployments we see, wallet passes deliver higher adoption, better retention, and more repeat visits than app only loyalty strategies. This is especially true for brands without the scale and name recognition of national giants. When programs reach close to a 3x repeat visit lift among engaged wallet pass users, it usually comes from three inputs. You reduce enrollment friction. You keep your brand present in the customer's wallet. You send timely, relevant prompts through lock screen updates and location triggers.
That holds whether you are a 10 location regional chain building your first digital loyalty program or a national brand trying to reach customers who will never download your app.
The QSR brands that win loyalty over the next few years will be the ones that meet customers where they already are, in Apple Wallet and Google Wallet, rather than the ones with the most advanced apps.
Passmint creates, distributes, and manages wallet passes for QSR loyalty and promotions, with no app development required.
Primary sources
Common questions
Technical content writer, Passmint
Julio is a technical content writer at Passmint. He writes about Apple PassKit, the Google Wallet API, and what breaks when wallet passes meet production traffic.
More from Julio Song →