
Rolling out loyalty is easy in a slide deck. It gets messy the moment it hits a store.
When a program goes digital-first, you’re not just changing how customers earn points. You’re changing checkout behavior, staff routines, queues, messaging volume, and the basic question of “how do I prove I’m a member” under real-world conditions like weak connectivity and impatient lines.
This post isn’t a dunk on any one brand. It’s a set of lessons pulled from a very common rollout pattern: aggressive acquisition pushes at checkout, heavy email onboarding, and a program experience that assumes customers will happily install an app and use it every time. Some of those choices can work. Many of them backfire.
Here’s what loyalty teams can learn from rollouts like this and the specific traps to avoid if you want adoption without the operational pain.
Here’s the scene most loyalty teams don’t model. It’s Saturday, there’s a line, the customer already made a decision, and the cashier is trying to move people through. Then the loyalty rollout asks staff to do product marketing at the register.
That’s what early H&M Club-style rollouts can feel like: “join now, download the app, confirm your email, scan this, accept that.” Even if the program is good, the moment is wrong. The customer feels held hostage. The staff member feels like they’re being judged on signups instead of speed. Everyone loses.
What to do instead: move the join moment earlier, when the customer actually has time.
.jpeg)
Digital-first loyalty sounds clean until you watch it in the wild. Phone battery at 4%. App logged out. No signal in the store. The QR code won’t load. The customer knows they’re a member but can’t prove it fast enough, so they skip it “just this once.” Then the habit never forms.
With H&M-style digital loyalty, the tension is real: brands want app adoption, customers want a frictionless identifier. If “loyalty = open app + find card + hope the internet works,” you’ve created a sometimes-program.
What to do instead: make identity flexible and resilient.
A common H&M Club rollout vibe is: join today, get hit with a wave of emails tomorrow. The brand thinks it’s onboarding. The customer experiences it as noise.
Retail purchase cadence is not SaaS cadence. Most customers are not “active users.” They’re occasional shoppers. If you blast them like they’re in a 7-day activation funnel, they unsubscribe before they ever get to the part where loyalty becomes useful.
What to do instead: slow down and let behavior lead.

Points programs fail quietly when customers can’t answer two questions in five seconds:
Early-stage rollouts often hide rewards behind too many clicks, or make the value feel abstract. If customers can’t see progress while shopping, points become a number that never turns into behavior.
What to do instead: make rewards feel like a ladder, not a ledger.
A loyalty program doesn’t need to be generous. It needs to be legible.
This is the painful part of digital-first loyalty: you can launch a program in the app and website in a week, but stores are a different organism. Devices, training, staffing, scanning reliability, returns flow, edge cases. If the store experience is shaky on day one, customers remember that more than they remember any perk.
In rollouts like H&M’s, the first impression often happens at the register. If that moment fails, your “launch” becomes a long recovery campaign.
What to do instead: treat rollout like a production deployment.
You’re not just launching loyalty. You’re changing store operations.
H&M Club is a useful case study in how digital-first loyalty can go sideways during rollout. The main lesson is that loyalty isn’t a campaign once it hits stores: if you push signups at checkout, require an app in real-world conditions, spam new members, or hide the value of rewards, customers won’t build the habit. The fix is operational and systematic: move onboarding away from the register, make identification flexible, pace messaging to shopping cadence, make rewards obvious and reachable, pilot before scaling, and enforce consistent rules across app, web, POS, and support.