Why Most Mall Loyalty Programmes Become Discount Databases
Two lakh members. Points issued up. Redemptions up. Then the CEO asks whether any of it made people visit more or spend more, and the room goes quiet. Why most mall loyalty programmes quietly become discount databases, and how to tell if yours has.
It is annual review week. The loyalty programme has two lakh members, up from one and a half. Points issued are up. Redemptions are up. The slide is green.
Then the CEO asks one question. Did any of this make people visit more, or spend more than they would have anyway?
And the honest answer, if the team is being honest, is that nobody knows.
Issuance is not loyalty
Look closely at what a typical mall loyalty programme actually measures. Members enrolled. Points issued. Coupons redeemed. Every one of those is an activity number. Not one of them is a behaviour-change number.
A shopper who was going to buy the shirt anyway swipes the card and collects points. That is recorded as a loyalty event. It was a discount. The programme cannot tell the two apart, so it counts both as success.
This is how a loyalty programme quietly becomes a discount database. It runs for years, issues millions of points, and never once proves it changed what a shopper did. It rewards the visit that was already happening.
The villain is the missing context, not the team
It is worth being precise, because the loyalty team is not the problem and neither is the vendor who built the engine.
A points engine is built to do two things well: issue and redeem. It sees a point go out and a coupon come back. What it cannot see is the context that would turn those events into meaning: the shopper's visit before this one, the size and spread of the basket, and the visit that did not happen because the reward was not worth returning for.
Strip the context away and loyalty is just discount distribution with a membership card on top. The team is asked to prove retention using a tool that was only ever designed to move points.
What the discount database costs
The programme budget is not the cost. The cost is what the budget buys, which is often nothing that would not have happened anyway.
- Margin, given away to the already-loyal. Your most frequent shoppers are also your biggest redeemers. They were coming regardless. The programme pays them to do it. Think of it as a discount on revenue you already had. Label that honestly as illustrative, then go and check who your top redeemers actually are. The pattern usually holds.
- An unprovable case. Because the programme cannot show incremental visits or spend, it is defended on the one number that always goes up: member count. That is a vanity metric, and a sharp CFO knows it.
- Co-funding brands see nothing. Tenants who put money into the programme get no attribution back. That weakens the next ask, and the renewal after it.
- The reckoning at review. When the CEO asks what loyalty changed, "we added fifty thousand members" is not an answer. It is a deflection, and everyone in the room can feel it.
Six signs your programme is a discount database
Read these against your last quarterly report.
- The headline success metric is member count or points issued.
- Nobody can state the difference in visit frequency between enrolled members and comparable non-members.
- Almost every reward is a discount. Nothing is access, recognition, early entry, or experience.
- Your biggest redeemers are your most frequent shoppers, the ones who would have come anyway.
- Tiers exist, but nobody can say what moving a shopper up a tier did to their spend.
- When leadership asks what loyalty changed, the answer is a number of members.
Three or more, and the programme is distributing discounts, not building loyalty. The team is not failing. The engine was never asked to measure the thing that matters.
What good looks like
A loyalty programme that can defend itself measures behaviour, not issuance:
- It compares enrolled members against similar non-members: do they visit more often, spend more, shop across more categories.
- It rewards the behaviour the mall actually wants more of, like a second visit this month, not the visit that was already booked.
- It connects the card to what the shopper discovered and did across the mall, not only to what they redeemed at the till.
- Its report to the board reads: members visited this much more and spent this much more, and here is the incremental part.
None of that asks the loyalty team to work harder. It asks the programme to see the context it is currently blind to.
Where Portcart fits
Portcart is built to give malls and airports one view of the shopper journey: discovery, engagement, and commercial activity. For loyalty, that means the card is connected to visits, to what the shopper found, and to what they redeemed, in one place. The programme can then be judged on behaviour it changed, not points it issued. That is the difference between a loyalty programme and a discount database.
The meeting before the renewal
Before the loyalty budget is renewed for another year, put one question on the table: what behaviour did our loyalty spend change last quarter, and how do we know?
If the honest answer is member count and a redemption chart, book a Loyalty Leakage Review with us. It is a working session on your own programme: where the spend is going to shoppers who would have come anyway, what the engine can and cannot prove today, and what it would take to reward the behaviour you actually want. Bring last quarter's report. That is enough to start.