Blog
Product Updates
Why Large Retailers Struggle With Loyalty Software

Sophie Wilms

A loyalty programme that takes eighteen months to go live has usually already lost the marketing director who signed off on it. That is the pattern you see across food retail, fashion and fuel retail: budget approved, vendor picked, and then a slow grind through POS integration, legal review and app store approval that eats the momentum the programme was supposed to create. If you are weighing up loyalty software adoption for a retail group with 50 or more locations, the real obstacles rarely show up in the vendor demo. They show up six weeks into the integration project.
This is worth being blunt about, because most of the advice online treats adoption as a change-management problem (get staff trained, get customers to download the app) when for large retailers the first wall is technical and organisational, long before a single customer sees the programme.
The integration bottleneck nobody budgets for
Every retail loyalty programme has to talk to a POS system, and usually an ERP too, to know what was bought, when, and at what margin. For a chain running on a legacy till estate across 200 or more stores, that is rarely a clean API call. It is often a patchwork of POS versions by region, a few franchise locations on different software entirely, and an ERP team that has its own release calendar and does not prioritise a loyalty vendor's ticket.
This is where timelines slip. A vendor promises a go-live date based on an idealised integration, then discovers the retailer's POS vendor needs eight weeks' notice for any new data feed. NeoDay's approach is to keep the platform API-centric and cloud-agnostic, so it connects to whatever POS or ERP stack is already in place rather than requiring the retailer to standardise first. That does not remove the POS vendor's own lead time, but it removes the second delay: the loyalty platform rebuilding its own integration layer for every retailer's quirks.
If you are asking whether a platform can integrate with your POS and ERP, the honest answer from any serious vendor should include a timeline for your specific stack, not a generic yes. Ask for the names of the POS systems they have connected to before and whether that was through a standard connector or custom work.
SDK versus standalone app versus web, and what that does to your launch date
The decision between a standalone app, an SDK inside your existing app, and a web experience is not just a product choice; it is a timeline choice.
An SDK integration into an existing retail app sounds fast in theory, because you are adding to something that already exists. In practice it depends on how clean that existing app's codebase is, how often your mobile team ships releases, and whether you have iOS and Android teams that can both prioritise the work in the same sprint. A realistic SDK integration for a mid-sized retail app, with testing and app store review, tends to run six to ten weeks once development starts, not from contract signature. If your internal app team has a backlog already, build that queueing time into your go-live date before you promise anything to the board.
A standalone app sidesteps your existing app team's calendar entirely, which is why NeoDay can launch a loyalty programme as a standalone app, an SDK, or a web experience in as little as 10 weeks from kickoff. Web-based loyalty, accessed via a link or QR code at the till, is the fastest to launch and the easiest for petrol and fuel retail networks where customers do not always want another app, but it gives you less room for push notifications and native gamification.
Format | Typical launch time | Best fit | Main constraint |
|---|---|---|---|
Standalone app | 10 to 14 weeks | Chains without a strong existing app | App store review, customer download friction |
SDK in existing app | 6 to 16 weeks after dev start | Retailers with an active, well-used app | Depends on internal mobile team's release cycle |
Web experience | 4 to 8 weeks | Fuel retail, QSR counters, fast rollout | Fewer gamification and push options |
Why adoption stalls even after a successful launch?
Technical delivery is only half the problem. A programme can go live on schedule and still fail to get traction, usually for one of two reasons: the reward structure does not match how people actually shop, or the data stays locked in a dashboard nobody acts on.
A 2024 study in the Darpan International Research Analysis on loyalty programmes in retail found that personalisation drives retention but also flags a privacy trade-off: customers want relevant offers but are wary of how much data that requires. That tension matters more for large retailers than small ones, because a 200-store chain is collecting purchase data at a scale that makes customers more aware of being tracked, not less. Retailers that get this right tend to be transparent about what data earns what reward and keep the exchange visibly fair, a stamp for a coffee, points for a fuel fill, rather than vague personalisation that feels like surveillance.
The other failure mode is organisational. Loyalty data sits in IT's domain, campaign execution sits with marketing, and store-level incentives sit with operations. When those three do not meet regularly, the programme becomes a cost centre nobody owns. This is less about software and more about whether a CMO, a CCO and an IT lead agree on who reads the dashboard every week. For food retail chains, this often falls to a loyalty and CRM manager who has to chase buy-in from category teams who did not ask for the programme in the first place.
What happens to points when customers go quiet?
Inactive members are a real cost. Points sitting unredeemed on your balance sheet are a liability, and a member who has not engaged in six months is not generating the repeat-visit behaviour the programme exists to drive.
Most mature loyalty platforms, NeoDay included, let you set an expiry policy per programme: points can lapse after a defined inactivity window, with warning communications beforehand so it does not feel punitive. What you choose depends on your vertical. A QSR chain with frequent, low-value transactions can afford a shorter expiry window because customers who care will come back within months. A fashion retailer with seasonal purchase cycles needs a longer window, or expiry tied to a calendar year rather than days since last purchase, otherwise you penalise customers for buying coats once a winter. The point is to design the policy around real purchase frequency in your category, not copy a default setting from a vendor's template.
Pricing: what you are actually paying for
Pricing per store or per user is the question every finance team asks, and every vendor answers differently, which is part of why comparison is hard. Some platforms price per active member per month, others per location regardless of member count, and others bundle a flat platform fee with a separate implementation cost.
A realistic way to compare vendors is to ask for three numbers separately: the one-time setup fee tied to integration and configuration, the ongoing platform fee, and any cost per SMS, push notification, or email sent through the programme. A platform that looks cheap on the headline fee can be expensive once you add messaging volume for a 500,000-member base. NeoDay's pricing structure is published on its loyalty platform page, and the honest advice for any vendor's quote is to ask what is excluded, not just what is included.
Does gamification actually help, or is it a distraction?
Gamification gets pitched as a default feature in almost every loyalty platform demo now, and it does measurably lift engagement in many cases. A 2025 field study published in the Journal of Marketing Research tracking nearly 19,000 app users found that gamified mechanics increased engagement, though the effect varied by how the mechanics were designed.
But more isn't automatically better. A 2026 study in the Journal of Retailing and Consumer Services found that gamification can backfire past a certain point: badly framed progress bars or challenge tiers set too high make customers give up rather than engage. If you're evaluating a platform partly on its gamification features, ask how progress is framed for the customer, not just whether the feature exists. For more on how to judge gamification vendors specifically, see our comparison of gamification software for loyalty.
For large retail groups comparing platforms end-to-end, our scorecard of loyalty platforms for large retail groups and the broader list of enterprise loyalty platforms in Europe cover vendor-by-vendor detail that goes beyond adoption risk. And if you are still deciding whether to build this internally, our piece on build versus buy loyalty tech walks through the trade-off in more depth than fits here.
If you want to understand loyalty programme fundamentals before comparing vendors, our explainer on what a loyalty programme actually is and our piece on customer retention and why it matters are good starting points, as is our roundup of retail loyalty programme examples if you want to see what good looks like in practice.
FAQ
How do we know if our go-live date is realistic once SDK work starts?
Ask your mobile team for their actual release cadence, not the ideal one, and add testing and app store review time on top. If your team ships every two weeks and the SDK needs two release cycles to land cleanly, your floor is closer to eight weeks from development start, not from contract signature.
What is a reasonable setup fee compared to ongoing support costs?
Setup costs should reflect integration complexity, so a chain with one POS system pays less than one with five regional variants. Ongoing support costs should be transparent as a separate line from messaging and platform fees, and you should be able to see what support response time that cost buys you.
Why do loyalty programmes fail even when the technology works?
Usually because ownership is unclear across marketing, IT and store operations, so nobody acts on the data the platform produces. A programme needs a named owner checking engagement numbers weekly, not a dashboard that exists in theory.
Should a fuel retailer or QSR chain choose web over an app?
For transaction volumes that happen fast, at a pump or a counter, a web experience triggered by QR code often gets higher adoption than asking customers to download another app. An app makes more sense when you want push notifications and deeper personalisation, which fashion and food retail chains with longer consideration cycles tend to value more.
Photo: SpotOn POS on Pexels
More questions about retail loyalty? Find the answers in our loyalty FAQ.

