TL;DR Summary
Tech fragmentation is killing small business loyalty programmes. Here's why Toast, Square, Clover, and DoorDash don't talk to each other — and what to do about it.
Why Your Loyalty Programme Doesn't Integrate With Anything (And How to Fix It)
The modern small business runs on four to six separate technology platforms that share almost no data with each other. One restaurant owner described their stack with notable frustration: "Online orders one app. Delivery drivers another. POS totally separate. Loyalty programme yet another system. None of them talk to each other." This is not a niche complaint. It is the default state of small business technology — and it is why most loyalty programmes produce data that is functionally useless.
The Fragmentation Problem in Plain Terms
Walk through a typical independent restaurant's tech stack:
- POS: Square, Toast, Clover, or Lightspeed
- Online ordering: The POS's own platform, or a separate system like ChowNow or Slice
- Third-party delivery: DoorDash, Uber Eats, or both (each with their own tablet and app)
- Reservations: OpenTable, Resy, or a manual system
- Loyalty programme: Stamp Me, Loopy Loyalty, Fivestars, or a standalone app
- Email marketing: Mailchimp, Klaviyo, or something built into the POS
- Payroll and inventory: Usually something else entirely
Each of these systems has its own login, its own data model, its own customer IDs, and its own definition of what a "customer" is. They rarely communicate. When they do, it typically requires a paid integration, a developer to configure it, or a manual export-import workflow that somebody has to do every week.
The loyalty programme is usually the most isolated node in this graph.
Why Loyalty Data Stays Trapped
Loyalty platforms are built to capture customer engagement — visits, points, redemptions, contact details. But that data is only valuable if it can inform other decisions: who to email, who to target with a promotion, which customers are at risk of churning, which customers are your highest-value regulars.
If the loyalty platform cannot talk to the email tool, the POS, or the CRM, the data sits inside the loyalty dashboard and goes nowhere. The business owner can see that 340 customers are enrolled and that 23 redemptions happened last month. They cannot act on that information in any other system.
This is the practical reality behind the ROI measurement problem discussed in loyalty programme analytics conversations. The data exists — it is just locked inside a silo.
The POS Integration Trap
Most POS providers offer their own loyalty module. Square Loyalty, Toast's loyalty feature, Clover Rewards — these are convenient because they live inside the same system as your transaction data. No integration required. Customer spend automatically earns points.
The convenience is real. The constraints are also real.
Lock-in: POS-integrated loyalty means your loyalty data is owned by your POS provider. If you switch POS systems — which happens frequently as businesses grow or change — your loyalty history, customer profiles, and earned points are difficult or impossible to migrate.
Limited functionality: POS loyalty modules tend to be basic. They handle points and rewards, but rarely include push notifications, detailed cohort analytics, or the kind of customer segmentation that makes a loyalty programme strategically useful.
No cross-channel coverage: POS loyalty only captures in-person transactions. Online orders from a different platform, delivery orders from a third-party app, and any other non-POS transaction are invisible to the loyalty programme. Customers who order through multiple channels accumulate points in only one of them, which creates friction and confusion.
Geographic inflexibility: Multi-location businesses often run different POS systems at different sites — especially if they have grown through acquisition or partnership. A POS-integrated loyalty programme cannot span those locations without a complex setup that the POS provider may not support.
What the Integration Dream Actually Looks Like
In an ideal world, every customer transaction — regardless of channel — would trigger a loyalty event. A customer who visits in person, orders online, and orders delivery would have a single unified loyalty account that captures all three. They would receive communications through a single channel. Their points balance would be accurate regardless of how they last transacted.
This is achievable at enterprise scale. Starbucks does it. McDonald's does it. The technology exists.
For a £2m revenue independent restaurant, it is not achievable within a reasonable budget or complexity threshold. The integrations required are expensive, fragile, and require ongoing maintenance every time any of the involved platforms updates their API.
The practical question for small businesses is not "how do I build a unified system?" It is "how do I run a loyalty programme that works without depending on integrations?"
The POS-Agnostic Approach
The most practical solution for most small businesses is a loyalty programme that operates independently of the POS entirely.
Digital wallet cards — delivered via QR code to Apple Wallet or Google Wallet — are inherently POS-agnostic. The loyalty card lives on the customer's phone. Points or stamps are recorded when a customer scans at the counter or shows their wallet card to staff. This can happen regardless of what POS the business is using.
There is no integration to configure. The loyalty programme does not know or care whether you are running Square or Toast or a cash register with no software at all. It captures the visit data independently and stores it in its own dashboard.
This approach loses the automatic transaction-level data that POS integration provides — you know that a customer visited, but you may not automatically know how much they spent. For most small businesses running programmes based on visit frequency rather than spend amount, this is an acceptable tradeoff.
GPASS operates on this model: a QR code at the counter, 30-second signup to a digital wallet card, and visit data tracked in a dashboard that is independent of whatever POS, ordering system, or delivery platform the business uses. €39/month, no integration project, no developer required.
What to Actually Look For in a Loyalty Platform
When evaluating loyalty platforms, ask these five questions in order:
1. Does it require POS integration to function? If yes, evaluate whether that integration is with your specific POS, how much it costs, and what happens to your data if you change POS providers.
2. What is the customer signup flow? App download = 15% completion. Wallet card QR code = 95% completion. This single factor matters more than almost any feature comparison.
3. Does it support wallet push notifications? Email open rates average 12%. Wallet push notifications are comparable to SMS in visibility. Any loyalty platform worth paying for should support Apple Wallet and Google Wallet push notifications natively.
4. Who owns the customer data? Your customer list, contact details, and visit history should be exportable to a CSV at any time. Any platform that does not offer data portability is creating the same lock-in problem as third-party delivery apps.
5. What does the analytics dashboard show? At minimum: signup rate, active members, visit frequency per member, redemption rate, and lapsed member count. If the platform cannot show you whether enrolled customers are visiting more often than before, it cannot prove its own value.
The Practical Migration Path
If you are currently running a loyalty programme that is trapped inside a single POS ecosystem, here is a realistic migration path:
- Export your current customer list while you still have access to it. Even if the data is incomplete, names and contact details are valuable.
- Run a parallel programme briefly. For two to four weeks, run your old programme alongside a new wallet card programme. Tell existing loyalty members that the new system is faster and their balance has been transferred.
- Set your new baseline. Once you have moved most active members to the new system, you have a starting point for measuring improvement.
- Sunset the old system. Once redemption activity has moved to the new programme, close the old one. Running two simultaneously indefinitely creates confusion for both staff and customers.
The migration itself is not technically complex. The difficult part is communication — making sure regular customers know their loyalty history has been honoured, and making sure staff understand the new process.
The Broader Technology Lesson
The fragmentation problem in small business technology is not going to be solved by any single vendor in the near future. The number of relevant platforms, the pace of API changes, and the economics of building and maintaining integrations for a market of independent businesses with highly variable tech stacks all make a truly unified system unlikely at the price points small businesses can sustain.
The answer is to stop trying to build integrations and start choosing tools that work independently. A loyalty programme that requires no integration is not a compromise — it is a design choice that makes it more resilient, more portable, and more likely to still be running correctly in 18 months when you have upgraded your POS for the third time.