The real cost of a bad in-store experience
When the experience breaks at the shop floor, the bill arrives later – in three places:- Basket abandonment in-store. [Salesforce State of the Connected Customer] reports that around [60%] of consumers have walked out of a store without buying because of a poor experience, long queues, confused staff, broken promotions.
- NPS decline. [Qualtrics XM Institute] benchmarks show NPS in retail drops sharply after even one negative service interaction, with recovery taking 3–5 positive interactions to offset.
- Repeat visit drop-off. In categories where store visits are the main retention signal, a single bad experience reduces the likelihood of a repeat visit within 90 days by [30-40%].
Why is fixing it traditionally painful?
The reason most retailers don’t fix it is that the obvious fixes are all expensive, slow, or both:- POS migrations take 9-18 months and risk every revenue dollar in the meantime.
- Custom retail apps cost [$500K–$2M+] to build and a similar amount per year to maintain.
- Download friction means even when the app exists, only a fraction of customers will install it and a fraction of that fraction will keep it open.
- Staff retraining on a new digital flow is an ongoing line item, not a one-off project.
Mobile wallets as the frictionless alternative
Apple Wallet and Google Wallet are native on every modern smartphone. No download. No login. No app store search. Customers add a pass with a single tap, and it lives on the lock screen, surfacing automatically when relevant near a store, before an expiry, or when a tier changes. This is what Litecard turns into an ‘in-store engagement channel ’- loyalty cards, vouchers, event tickets, member passes, and order tracking, all delivered through the wallets your customers are already using at a fraction of the cost of an app build. The contrast with a custom app is stark:- Adoption: a wallet pass takes one tap to install. An app takes an app store visit, a download, a sign-up, and a notification permission prompt.
- Retention: a pass sits on the lock screen indefinitely. An app needs to be reopened to matter.
- Visibility: passes can push to the lock screen with no inbox to fight through.
- Cost: a wallet program goes live in weeks for a fraction of what a custom retail app costs to build and maintain.
How Litecard fits any in-store timeline
Most retailers we talk to are in one of two camps:
Camp A – mid-loyalty migration: you’re already replatforming loyalty or POS, with 12–18 months left on the project. Wallet passes run in parallel now they don’t depend on the new stack being live. You start capturing in-store engagement signals immediately, then plug them into the new platform when it lands.
Camp B – no app plans, no replatforming on the horizon: Litecard is the lightweight digital channel. You get the in-store engagement benefits of an app without the build, the maintenance, or the retention problem. The wallet pass is the digital surface.
The core message either way: you will never get 100% of your customers actively using your app. But a meaningful share of them already have Apple Wallet or Google Wallet on their phone right now. Meet them there.
Concrete in-store impact
Specific places wallet passes change the shop-floor experience:
- Geo-triggered push at the POS. Customer walks past or into a store; the relevant pass surfaces on the lock screen with the current offer or member tier. No staff intervention needed.
- Members pass scanning at checkout. Customers taps their pass at the register. Staff scan the QR/barcode the same way they’d scan a printed loyalty card. No “what’s your phone number?” conversation that slows the queue.
- Real-time tier updates. Customers cross a threshold mid-shop their pass updates instantly to reflect the new tier, the new offer, the new entitlements.
- Dwell time uplift. Engagement at the lock screen during the shop offers, recommended add-ons, store-specific events adds measurable minutes to the average visit in the categories we’ve measured.
- Recovery from queue and stock-out moments. When the experience does break a long queue, an out-of-stock SKU – a pass – can push a recovery offer in the moment, rather than three days later in an email.
What you don’t have to do
The reason mobile wallets land cleanly inside an existing retail operation is the list of things you don’t have to change:
- No new POS hardware. Wallet passes scan on any QR/barcode-capable POS scanner.
- No staff retraining beyond “scan the customer’s phone.”
- No new login or password for the customer.
- No download. No app store gate.
- No new CRM wallet passes are issued from triggers in the CRM you already run (Klaviyo, Salesforce Marketing Cloud, Braze, Emarsys, etc.).
Related reading
If a lot of your voucher and reward flows already exist in your CRM but aren’t branded as a loyalty program, you might be running a hidden loyalty program without realising it and mobile wallets fix most of its redemption issues.
And if your CRM is heavily email-dependent and your customer base skews younger, it’s worth re-examining whether email is still effective for Gen Z – or whether you need to diversify the delivery channels.
