How Indian Retail Chains Should Measure Branch-Level Loyalty Programme Redemption

A loyalty programme can look healthy at chain level while individual outlets are losing money on redemptions or failing to recognise customers who shop across branches. The measurement problem is not simply counting points used. It is separating the branch that issued a reward, the branch where it was redeemed, and the branch that funded the offer. Those are three different business events.

Use three branch fields, not one

Store the originating branch, redemption branch and financial owner as separate fields. A customer might earn points at a Surat outlet, redeem a reward in Ahmedabad and have the discount funded centrally. If the reporting system attributes all three actions to the redemption branch, the branch manager appears to have created a cost they did not control. If it attributes everything to the originating branch, the outlet that fulfilled the reward disappears from operational analysis.

At minimum, the transaction record should preserve a stable customer identifier, transaction ID, earn location, redemption location, reward type, discount value, funding owner and reversal status. Avoid putting personal information into marketing URLs or unprotected spreadsheets. Limit customer-level exports to staff who need them.

Worked example

Imagine Branch A issues 800 rewards worth ₹100 each. Of those, 260 are redeemed at Branch A, 190 at Branch B, 70 online and the remainder expire. Report issuance separately from redemption. Then reconcile the actual discount cost against the finance ledger. Do not treat issued reward face value as realised cost, and do not count a reversed transaction as a completed redemption.

A useful scorecard includes redemption rate by earn cohort, cross-branch redemption share, average basket with and without reward, margin after discount, expiry rate and reversals. Compare like-for-like cohorts and promotion periods; raw redemption counts favour larger branches.

Governance questions before launch

• Can a branch refuse or restrict a centrally issued reward, and under what published terms?
• Who pays when a reward is redeemed away from its issuing outlet?
• How are refunds handled if the reward-funded transaction is reversed?
• Does the loyalty platform use stable branch IDs that match finance and point-of-sale systems?
• Who approves a report that attributes reward cost differently from the ledger?

Do not use a Google Business Profile metric as a proxy for loyalty redemption. Profile interactions and loyalty transactions represent different stages of the customer journey. Join them only where the measurement design, consent and available identifiers genuinely support it.

Monthly reconciliation

Finance should reconcile redemption value and funding entries; CRM should investigate missing earn/redemption locations; branch operations should validate exceptions such as offline billing; marketing should assess whether a campaign produced incremental margin rather than merely moving a planned purchase forward. Publish the exceptions, not only the headline redemption rate.

Source notes

• Internal editorial framework: Proposed loyalty economics workflow; validate against relevant contracts, policies and applicable law..