Greggs Rewards works for Greggs because it sits on top of roughly 2,500 UK shops, a pre-existing app install base, and a marketing budget that can absorb the 30 to 40 percent of customers who drop off at the app download screen. The mechanics underneath it, categorised stamps, a welcome reward on first use, and a birthday treat timed to the highest-churn window, are genuinely transferable. The infrastructure is not. This teardown separates the two so you can take what is useful and leave what would break at your scale.
- Key takeaway 1: Greggs' strongest loyalty mechanics are behavioural, not technological. Category stamps and welcome rewards work at any scale.
- Key takeaway 2: The app download requirement is a structural conversion killer for independents. Greggs can absorb the drop-off. A 12-seat cafe cannot.
- Key takeaway 3: The welcome drink and birthday treat target the two moments customers are statistically most likely to churn: after visit one, and after a long gap.
- Key takeaway 4: Greggs rewards are identical for every customer in every city. An independent can personalise at a level Greggs structurally cannot match.
- Key takeaway 5: Wallet-native loyalty (Apple Wallet, Google Wallet) removes the download barrier while keeping the digital mechanics that make Greggs work.
What Greggs Actually Gets Right (And Why Scale Is Doing Half the Work)#
Three mechanics inside Greggs Rewards are doing the real work. First, category-based stamps: customers earn stamps per transaction rather than per item, which keeps the scan fast and the reward logic simple for staff. Second, the welcome reward issued on first app use, which converts a download into an immediate second visit. Third, the birthday treat, which re-engages customers who have gone quiet. These are not accidental features. They target the two highest-churn moments in any food business: the gap between visit one and visit two, and the long tail of customers who visited a few times and stopped.
Marketing Week's analysis of Greggs' loyalty performance notes that the programme has measurably increased visit frequency, not just basket size. That distinction matters. A loyalty scheme that only rewards spend per visit is a discount mechanism. One that increases how often someone walks through the door is a retention mechanism. Greggs is running the latter.
What scale is doing, though, is covering the cracks. Greggs can afford a 30 to 40 percent drop-off at the app download screen because 60 percent of a very large number is still a very large number. It also benefits from pre-existing brand recognition: customers already want to download the app before they are asked. Neither of those conditions applies to an independent bakery in Shrewsbury or a specialty coffee shop in Bristol.
The App Download Problem: Why Greggs' Model Breaks for Independent Operators#
The app download requirement is not a minor inconvenience. It is a structural conversion barrier. A customer at a busy independent cafe has roughly 90 seconds at the counter. Asking them to find the App Store, download an app, create an account, and verify their email in that window produces predictable results: most do not bother. The ones who do are already your most loyal customers. You have not acquired anyone new.
"completely unable to upload any of my gift cards"
That review, pulled from the Greggs App Store listing, points to a second problem: a loyalty scheme that does not connect to your other revenue streams (gift cards, pre-orders, subscriptions) is leaving retention on the table. Greggs has this problem at scale and has not solved it. Independents can sidestep it entirely by choosing simpler tooling that does not require a separate app ecosystem to maintain.
The friction compounds for multi-site operators. If your loyalty programme is tied to an app that requires a specific POS integration, every new site is a deployment project. Reporting across sites becomes a separate problem. The independent review of the Greggs app notes that scan reliability at point of sale is inconsistent, which is a manageable problem when you have a dedicated IT team and is an unmanageable one when you do not.
The Mechanics Worth Stealing: Categorised Stamps, Welcome Rewards, and Birthday Treats#
Strip away the app and three mechanics remain worth copying directly.
- Category stamps per transaction, not per item. This keeps the interaction at the counter to a single scan and makes the reward feel achievable. Customers who can see progress on a stamp card return to complete it. This is the completion effect, and it works whether the card is paper or digital.
- A welcome reward on first use. The gap between visit one and visit two is where most independent cafes lose customers permanently. A reward issued immediately on signup, redeemable on the next visit, converts a one-time visitor into someone with a reason to return. See first-visit rewards that bring customers back a second time for specific mechanics.
- A birthday treat with a defined redemption window. The window matters as much as the reward. A birthday treat redeemable for 30 days around a customer's birthday creates urgency without pressure. It also re-engages customers who have gone quiet, because the trigger is personal rather than promotional.
Independent reviews of the Greggs scheme consistently cite the welcome drink and birthday treat as the features that feel most valuable to users. The behavioural logic is straightforward: both rewards arrive at moments when the customer has the least existing reason to return. That is precisely when a prompt is most effective.
What Greggs Cannot Do That You Can: The Personalisation Gap#
Greggs Rewards is identical for every customer in every city. The stamp card for a customer in Newcastle is the same as the one for a customer in Exeter. That is a structural constraint of operating at national scale with a standardised menu and a centralised app. It is not a constraint you share.
An independent bakery can issue a reward tied to a specific product. A specialty coffee shop can run a stamp card for filter coffee separately from one for espresso drinks, because the customers are different and the margin is different. A multi-site operator can run location-specific promotions without rebuilding the entire programme. None of this requires AI or predictive analytics. It requires a loyalty tool flexible enough to support more than one card type and a team that knows its customers well enough to use that flexibility.
This is the competitive moat Greggs cannot close. A customer who feels that a loyalty programme was built for them specifically, not for a generic bakery customer, is harder to poach. Competitors can copy your menu faster than they can replicate that relationship.
How to Run a Greggs-Style Loyalty Programme Without Forcing a Download#
Wallet-native loyalty removes the download barrier entirely. Instead of asking a customer to find an app in the App Store, you give them a short link or a QR code. They fill in a brief web form, verify their contact details, and the loyalty card saves directly to Apple Wallet or Google Wallet. No app. No account creation beyond what you need. The card is already on their phone the next time they walk in.
This is how running a loyalty programme without asking customers to download anything works in practice. The staff scanner is a separate tool, role-based, used only at the counter to add stamps or redeem rewards. The customer never needs to open anything other than their existing wallet app.
Carrott is a wallet-native loyalty platform built on exactly this model. Cards live in Apple Wallet and Google Wallet with real-time updates when card data changes. Customers join via a short link (joinpass.co) or a custom web form, with SMS or email verification. Staff use a QR-based scanner app to add stamps and redeem rewards. There is no customer-facing app to download and no POS integration required, which means it works alongside whatever till system you already use.
Carrott supports four card types: stamp cards (visit, spend, manual, or product-based stamps), points cards with flexible reward tiers, membership cards (free, paid monthly or yearly via Stripe, or invite-only), and coupon or voucher cards. For a bakery wanting to replicate the Greggs model, a visit-based stamp card with a welcome reward and a time-bound birthday campaign covers the core mechanics. For a multi-site operator, the multi-tenant structure handles subaccounts and franchises without requiring separate logins for each location.
Real Numbers: What Repeat Visit Rates Look Like Without an App Barrier#
The benchmark question for any loyalty programme is not how many people signed up. It is how many people came back. For independent cafes, a healthy repeat visit rate sits between 20 and 40 percent of first-time visitors returning within 90 days, depending on location, category, and average transaction value. See what a healthy repeat visit rate actually looks like for independent cafes for a full breakdown by business type.
The app download barrier suppresses that number before the programme has a chance to work. If 40 percent of customers decline to sign up because of friction, your effective loyalty programme reach is 60 percent of the customers who were already willing to engage. Removing the download step does not guarantee higher repeat rates, but it removes the ceiling on how many customers the programme can reach in the first place.
| Feature | Greggs Rewards (app) | Wallet-native loyalty (no app) |
|---|---|---|
| Customer join flow | App Store download, account creation, email verification | Short link or QR code, web form, SMS or email verify, card saves to wallet |
| Estimated signup drop-off | 30 to 40% at download screen | Significantly lower: no store visit required |
| Welcome reward | Yes, issued on first app use | Yes, configurable on card creation |
| Birthday treat | Yes, 30-day redemption window | Yes, via time-bound campaign push to wallet |
| Category stamps | Yes, per transaction | Yes, visit, spend, product or manual stamp types |
| Personalisation | Identical across all customers and locations | Per-card, per-location, per-product configurable |
| POS integration required | Yes (Greggs proprietary) | No (standalone staff scanner) |
| Multi-site reporting | Centralised (Greggs IT) | Subaccount structure, per-location data |
| Gift card / subscription link | Partial (known friction in reviews) | Membership card type supports paid tiers via Stripe |
Building Your Own Loyalty Programme: Where to Start This Week#
The fastest path to a working programme is to copy the three Greggs mechanics that translate, drop the app requirement, and add one layer of personalisation Greggs cannot offer.
- Set up a visit-based stamp card with a clear reward at a realistic threshold. Eight to ten stamps for a free item is the standard range. Lower thresholds feel cheap; higher ones feel unachievable.
- Issue a welcome reward redeemable on the next visit, not the current one. This is the mechanic that closes the gap between visit one and visit two. See first-visit rewards that bring customers back a second time.
- Add a birthday campaign with a 30-day redemption window. Collect date of birth at signup. The campaign fires automatically and re-engages customers who have gone quiet.
- Remove the download barrier. If your current loyalty tool requires an app, you are losing customers before the programme starts. Consider why punch cards keep getting lost and what to use instead as a starting point for the alternatives.
- Add one personalisation layer Greggs cannot match. A product-specific stamp card, a location-specific promotion, or a membership tier for your regulars. Start with one and measure it before adding more.
Is the Greggs Rewards app worth copying for an independent bakery?
The mechanics are worth copying: category stamps, a welcome reward, and a birthday treat are all transferable. The app delivery model is not. Greggs can absorb the 30 to 40 percent of customers who drop off at the download screen. An independent with lower footfall cannot afford that loss.
What is the biggest mistake independents make when setting up a loyalty programme?
Choosing a tool that requires customers to download an app. Signup conversion drops sharply at the download step, and the customers who do not sign up are invisible to your programme from that point forward. Wallet-native loyalty removes this barrier entirely.
How does a birthday reward actually increase repeat visits?
It targets the long tail of customers who visited a few times and then stopped. A birthday treat with a defined redemption window (typically 30 days) creates a personal, time-bound reason to return that is not tied to a promotion or discount campaign. The trigger feels personal rather than transactional.
Can a small cafe realistically compete with Greggs on loyalty?
On volume, no. On personalisation, yes. Greggs rewards are identical for every customer in every city. An independent can issue rewards tied to specific products, run location-specific promotions, and remember what a regular customer orders. That is a structural advantage Greggs cannot replicate at scale.
Do loyalty programmes work for specialty food and drink retailers with younger customers?
Yes, but the join mechanism matters more. Younger customers are comfortable with digital loyalty but resistant to downloading a dedicated app for a single retailer. A card that saves to Apple Wallet or Google Wallet fits the behaviour they already have, which is checking their wallet app for boarding passes, tickets, and payment cards.