Loyalty Is Not a Program. It's an Operating System.
For thirty years, retailers have called their loyalty work "programs." That word is the problem.
A program has a beginning, a middle, and a discount. You enroll. You earn. You redeem. Then you wait until the next email tells you to come back. The program is something a customer participates in occasionally. It runs alongside the business, not inside it.
That model is dead, even if its budget is still funded.
Customers don't want to participate in your program. They want their actual life to be easier. The household needs chemicals every two weeks. The dog needs food on a schedule. The car needs an oil change every five thousand miles. The printer is out of toner. The customer's question is not "what discount do you have today?" The question is "who has my back on the recurring stuff?"
The companies that win the next decade of retail will treat loyalty not as a program but as an operating system. The OS for the customer's recurring relationship with the category.
Let me draw the line.
What program-era loyalty looks like
Program-era loyalty was an industrial-age idea ported into retail. Score the customer on transactions. Reward them for showing up. Punish them mildly for absence (drop a tier, lose points). It is a scoreboard sitting on top of the business.
The unit of measurement is the transaction. Did they spend? How much? How often? The KPI tree looks like this:
Active member rate
Spend per member
Points redeemed
Email open rate
These are activity metrics. They tell you the program is alive. They do not tell you the customer is being served.
Most retailers have stopped here. Their loyalty function reports to marketing. Marketing reports to the CMO. The CMO reports to the CEO. The customer is somewhere down the org chart, on a slide that says "engagement." The loyalty platform is a vendor SaaS. The data sits in one warehouse. The decisions sit in another. The merchandising team doesn't talk to the loyalty team. The store team gets a script. The customer gets a punch card.
This is the program era. It is sunsetting.
What operating-system loyalty looks like
Operating-system loyalty starts from the customer's actual life. Not their transactions. Not their cohort. Their recurring rhythm of ownership in your category.
If you sell pool care, the customer's rhythm is: water tested, chemistry adjusted, equipment checked, season opened, season closed.
If you sell pet supplies, the rhythm is: food restock, flea and tick season, vet milestones, lifecycle stage transitions.
If you sell automotive parts, the rhythm is: oil interval, brake interval, seasonal tire change, registration renewal.
In each category, the customer has a cadence you can know. The opportunity is to score members not on transactions but on cadence. Are they replenishing on schedule, or have they fallen out of the rhythm? When they fall out, the system should notice and reach.
The unit of measurement shifts.
From "active member rate" to "replenishment cadence adherence."
From "spend per member" to "share of household need captured."
From "points redeemed" to "auto-ship attach rate."
From "email open rate" to "next-cycle conversion."
Same data assets. Different operating thesis.
Three signals you've crossed from program to operating system
One. Your KPI tree is recurring-rhythm shaped, not transaction shaped. When the CFO asks how loyalty is doing, the answer is "seventy percent of replenishment-eligible members are on cadence," not "we issued four million points this month."
Two. Cross-functional teams own the customer rhythm jointly. Loyalty isn't a marketing sub-function. The merchandising team plans inventory by cadence. The store team is briefed on which customers in their zip code are off-cycle. The supply chain plans by replenishment forecast, not by promotion.
Three. The customer experiences the OS, not the program. They notice that you anticipated. The chemicals arrived before they ran out. The seasonal package was offered before they remembered to ask. The store associate knew which question they were about to ask. The OS is invisible when it works. The program is visible because it's interrupting them with email.
Why most CMOs miss this
Three reasons.
First, incentives. The CMO is measured on quarterly marketing KPIs. Operating-system loyalty pays back in customer LTV, which compounds over years. The CFO and the Board reward the wrong shape of work.
Second, the org chart. Loyalty is housed in marketing. Marketing optimizes for campaigns. Campaigns are episodic. Operating systems are continuous. The CMO who wants to build OS-grade loyalty has to negotiate authority over functions she doesn't formally own: merchandising, supply chain, store operations, ecommerce P&L. Most CMOs won't fight that fight.
Third, vendor stacks. The big loyalty platforms are program-era products. They were built to issue points and send emails, not to sense customer rhythm and orchestrate replenishment. Migrating off them is a real engineering decision the CMO often doesn't have the authority to make.
The CMOs who beat this are usually the ones who took an ecommerce P&L into their portfolio. Once you own the replenishment economics, you own the leverage.
What I'd build first
If I sat down at a specialty retailer with recurring-purchase economics and a tired loyalty program, here is what I'd test in 90 days.
One. Re-score members by cadence, not transactions. Run the segmentation on adherence. Identify the off-cycle members. Reach.
Two. Pilot one auto-replenishment lane. Pick the highest-frequency SKU in the category. Convert one-off buyers into scheduled subscribers using their own usage data. Target a 20 percent attach within 12 months in the pilot market.
Three. Reframe seasonal moments as packaged products. Find the two highest-leverage decision windows in the customer's year. Rebuild them as fixed-price bundles, not discrete services. Sell them in advance, not in the moment.
Four. Tighten brand voice around the lived problem. Move creative, store signage, and email voice from product-led to problem-led. Measure with one NPS question: "I trust this brand to take care of my [category]."
Five. Lock the new KPI tree as the enterprise scoreboard. Loyalty cadence metrics belong on the same page as revenue and EBITDA, in front of the Board. Otherwise the program-era KPIs will quietly survive in a side deck and absorb attention.
The next decade
The retailers who survive the next decade will not be the ones with the cleverest brand campaigns or the slickest ecommerce sites. They will be the ones who treat their customer's recurring relationship with the category as an operating system the whole company runs on.
The CMO who builds that wins. The one who builds another loyalty program does not.
I have spent twenty years inside companies that ran the program. The ones that compounded value were the ones that quietly stopped, and started building the operating system instead. The customer never noticed the rebrand. They only noticed that life got easier. That is the whole point.
---
Satya Sivunigunta is a former CEO and CDO who has built and operated consumer brands and direct-to-consumer P&Ls at Nike, Microsoft, Ogilvy, JCPenney, Chico's FAS, Conn's HomePlus, and SelectBlinds. He writes at satya.me.