How-To Guide

How to implement a loyalty program: from approved design to live scans

The board has approved the scheme; now someone has to put a serialised QR on ten million packs, capture PAN from forty thousand retailers, and make sure the first UPI payout lands in seconds. This is the execution half of the story that most guides skip — serialisation at the print line, SKU-to-points mapping, KYC, enrolment drives, helpdesk and hypercare. For the strategy half — objectives, budgets, pilot selection — start with the 90-day launch playbook; this article assumes those decisions are made.

Key takeaways

  • Serialise a unique, non-guessable QR on every unit via pre-printed labels (₹0.15–0.40 per code), inline digital printing (₹0.10–0.20 at scale) or concealed scratch codes for high-fraud categories.
  • Map SKU points from dealer price and role — commodity SKUs at 0.5–1% of value, premium at 1.5–3% or 2–3x — in a version-controlled master trade marketing can edit.
  • PAN capture is mandatory for Section 194R (10% TDS above ₹20,000 per PAN a year); progressive KYC lets users scan first and hold redemptions above ₹500–1,000 until PAN and UPI verify.
  • Run 200–500 paid end-to-end test scans before go-live, then four to six weeks of hypercare, exiting only when payout success is stable above 98%.

Serialisation: getting a unique QR onto every unit

Serialisation puts a unique, non-guessable QR on every unit through pre-printed labels (₹0.15–0.40 per code), inline digital printing (₹0.10–0.20 at scale) or concealed scratch codes; start with the two or three fastest-moving SKUs that generate 60–70% of scans.

Everything downstream — scan verification, fraud detection, secondary-sales visibility, anti-counterfeit checks — depends on each unit carrying a unique, non-guessable code. Three application routes, in rising order of integration effort:

  • Pre-printed serialised labels, applied manually or by applicator on the packing line. Fastest to start (2–3 weeks), costs ₹0.15–0.40 per code applied, and lets you begin with just your top SKUs. The weakness is application discipline — labels applied crooked, doubled or skipped need line-level QC sampling.
  • Inline digital printing — variable-data QR merged into the existing label, pouch or carton artwork at the print vendor. Cheapest at national scale (₹0.10–0.20 per code) and tamper-consistent, but requires artwork revision, printer coordination and 3–6 weeks of lead time per SKU family. Cylinder-printed flexible packaging needs a hybrid: static artwork gravure-printed, variable QR inkjetted in a reserved white window.
  • Concealed codes — under scratch panels, inside lids, on the inner flange of a wire coil, behind the label. Mandatory in high-fraud categories, because a visible outer code can be photographed and claimed by anyone in the supply chain before the genuine buyer ever opens the pack. Many brands run a dual-code design: outer code for authentication and track-and-trace, inner code for the reward.

Practical sequencing: serialise the two or three fastest-moving SKUs first — they generate 60–70% of scans and let the program go live while slower SKUs follow. Plan for the un-coded pipeline: stock already in the channel takes 4–8 weeks to sell through, so the field script must explain why some packs earn and some don't during the transition. Cost the whole exercise honestly with the QR cost estimator — code generation, printing, application, and wastage of 2–4% on line rejects.

SKU-to-points mapping: the master file that runs the program

Map each SKU's points from its dealer price and strategic role — commodity SKUs at 0.5–1% of value, premium and focus SKUs at 1.5–3% or 2–3x multipliers, launch SKUs boosted for 90 days — in a version-controlled master trade marketing can edit without a development ticket.

Every serialised SKU needs a point value, and the mapping is strategy expressed as arithmetic. Work from dealer price and strategic role:

  • Traffic / commodity SKUs (the 1L economy paint pack, the standard house-wire coil): 0.5–1% of unit value. On a ₹1,050 coil that is ₹5–10 — enough to make scanning habitual, cheap enough to sustain at volume.
  • Premium / focus SKUs: 1.5–3% or a 2–3x multiplier. A ₹4,200 premium FR-LSH coil at ₹60–100 per scan tells the electrician exactly which product the brand wants specified.
  • Launch SKUs: boosted rates for 90 days with an automatic sunset date configured upfront, so the boost dies without a second decision.

Keep the mapping as a version-controlled master with effective-from dates, owned by trade marketing but changeable without a development ticket. In copper-linked or price-revised categories, unit prices move quarterly; a points table frozen in code becomes wrong within one cycle. Worked check before freezing: expected monthly scans per SKU × point value, summed across the catalogue, must land within the always-on share of budget — typically 55–60% of a total spend held at 1–2% of secondary revenue (thin-margin categories) or 2.5–4% (high-margin). If the model breaches, cut commodity rates before premium ones.

KYC: mobile, PAN and bank — with the friction engineered out

Engineer KYC friction out with mobile OTP as identity, PAN capture validated against the name in real time for 194R aggregation, and progressive KYC that lets users scan first while holding redemptions above ₹500–1,000 until PAN and UPI verification complete.

KYC is where programs quietly lose a third of their audience. The stack that works for trade users:

  • Mobile OTP as identity — the phone number is the account. One number, one account, enforced.
  • PAN capture with real-time validation. Non-negotiable, because Section 194R aggregation is per PAN: once cumulative benefits cross ₹20,000 in a financial year, 10% TDS applies, and without PAN the brand cannot track the threshold or file correctly. Validate the PAN-to-name match at entry, not at payout time when a mismatch blocks money and creates a helpdesk ticket. Explain it in one honest vernacular line — "sarkari tax niyam ke liye" — because "why does the company want my PAN" is the single most common enrolment objection in every category.
  • Progressive KYC. Let users register with mobile alone and start scanning; hold redemptions above ₹500–1,000 until PAN and bank/UPI verification complete. This converts KYC from an entry barrier into a motivated task — the user finishes it because money is waiting.
  • UPI verification by penny-drop and name-matching against the PAN, which doubles as the first fraud control against mule handles.

The rollout machine: training, enrolment, onboarding, helpdesk

1

Field-force training that ends in a live payout

Run half-day sessions per region: the why (30 minutes), the demo (every salesman enrols himself and scans a live code on his own phone), the objection-handling drill (PAN, TDS, "where is last scheme's pending money"), and the enrolment target handed out in writing. The moment that converts a sceptical salesman is ₹10 arriving in his own UPI account mid-session. Train supervisors separately on the dashboard so they manage by data — which counters enrolled, which never scanned — from week one.

2

Dealer and retailer enrolment drives

Sequence dealers first — a dealer who feels bypassed will quietly tell his retailers the scheme is a data-collection trick. Then ride the existing beat plan: each salesman enrols 5–8 counters per day on his normal route, assisted enrolment on the salesman's phone where the retailer's own phone is basic. Push activation, not just registration: an enrolment drive that signs 1,000 counters of whom 200 ever scan has produced 200 members and 800 sceptics. Set the drive target as "enrolled AND first scan within 14 days". Influencer enrolment — electricians, painters, plumbers — works best through meets hosted at enrolled counters, detailed in our influencer loyalty pages.

3

WhatsApp-first onboarding flows

For trade audiences, a WhatsApp onboarding journey beats an app download decisively: no store visit, no storage anxiety, vernacular by default. The flow that converts: poster QR → WhatsApp opens with a pre-filled "Hi" → language selection → name, shop, mobile-OTP → first scan tutorial as a 30-second video → PAN and UPI capture staged after the first earning. Every subsequent scan, balance query and redemption happens in the same chat thread. Brands moving from app-only to WhatsApp-first onboarding typically see enrolment completion roughly double.

4

Helpdesk before the first scan, not after the first complaint

Stand up three lines of support before go-live: an AI assistant on WhatsApp for the 70% of queries that are balance checks, scan failures and "kab milega paisa"; a vernacular human tier for KYC and payout disputes; and an internal escalation desk with a 24-hour SLA on blocked payouts. Publish the helpdesk number on every poster and pack insert. Track tickets by type from day one — the ticket mix is your best early-warning system: a spike in "invalid code" means a printing batch problem; a spike in "payout pending" means the rail or the TDS logic is misfiring.

5

Data migration from the old spreadsheet scheme

Most brands are not starting from zero — there is a legacy scheme living in Excel with claimed balances nobody fully trusts. The clean migration: announce a freeze date; audit balances against invoices and payout records; publish each participant's opening balance over WhatsApp with a 2–3 week dispute window; credit accepted balances as opening points in the new platform. Be generous on small disputes — fighting a retailer over ₹500 costs more goodwill than it saves — but cap and investigate outliers, because legacy books hide both honest errors and old gaming. Never launch with "old balances will be settled later"; unpaid history is the fastest way to poison a new program.

6

Payout rail proving and TDS wiring

Before any public go-live, run 200–500 real end-to-end transactions: scan → validation → points → redemption → UPI credit → TDS ledger entry. Verify the 194R machinery specifically: cumulative benefit tracking per PAN, the ₹20,000 threshold trigger, the 10% deduction (or gross-up, if the brand absorbs it — decide and document which), and the quarterly filing extract for finance. Gifts distributed at launch meets count toward the same threshold, so they must be logged against PANs too. A payout that fails in testing costs an engineering ticket; one that fails in launch week costs the program its reputation.

Hypercare: the six weeks that decide the year

Hypercare is four to six weeks of deliberately over-resourced operation — a daily stand-up on five metrics, a 24-hour SLA on blocked payouts, and an exit judged on evidence such as payout success above 98% and flattened tickets, not the calendar.

Go-live is not the end of implementation; it is the start of hypercare — four to six weeks of deliberately over-resourced operation. The rhythm: a daily 30-minute stand-up (trade marketing, platform success manager, finance, pilot RSMs) reviewing five numbers — enrolments, first-scan activation rate, payout success rate, tickets by type, fraud flags. A 24-hour SLA on any blocked payout. Weekly structured field feedback: what are counters actually saying, which objection is trending. A fortnightly steering review empowered to change point values, KYC steps or comms without a committee cycle.

Watch fraud patterns from the first week, not the first month: dealer bulk-scanning shows up as one device claiming 50 codes in an evening from a single location; code harvesting shows up as scans of units that primary data says are still in a warehouse. Act on the first confirmed case visibly but proportionately — a warning and clawback communicated through the sales team teaches the channel the platform is watching, without turning launch month into a policing exercise.

Exit hypercare on evidence, not on the calendar: payout success stable above 98%, ticket volume flattened, activation trending up week-on-week, and the fraud-flag rate below 2–3% of scans. Then hand over to the steady-state cadence described in our guide to loyalty program KPIs — and start planning the scale-up from pilot districts using the pilot-to-national decision gates.

Frequently asked questions

Where in the packaging process are loyalty QR codes applied?

Three common points: pre-printed serialised labels applied on the packing line (fastest to start, ₹0.15–0.40 per code), inline digital printing integrated into existing label or carton artwork (cheapest at scale, ₹0.10–0.20, but needs printer coordination and 3–6 weeks lead time), and scratch-covered codes inside the pack or under the lid for high-fraud categories. Most brands start with labels on 2–3 fast-moving SKUs and move to inline printing once volumes justify it.

Why is PAN capture necessary in a loyalty program?

Section 194R requires 10% TDS once a participant's cumulative benefits cross ₹20,000 in a financial year, and the aggregation is per PAN. Without PAN at enrolment the brand cannot track the threshold, cannot deduct correctly, and carries the tax liability itself. Capture PAN with a one-line vernacular explanation, validate it against the name in real time, and let low-value users start earning before PAN by holding redemptions above a small threshold until KYC completes.

How should SKU-to-points mapping be structured?

Map points from each SKU's dealer price and strategic role, not a flat rate: commodity traffic SKUs at 0.5–1% of unit value, premium and focus SKUs at 1.5–3% or 2–3x multipliers, and launch SKUs boosted for 90 days. Keep the mapping in a version-controlled master where trade marketing can change values with an effective date, because copper cycles and price revisions will force updates within the first quarter.

How do you migrate balances from an old spreadsheet scheme?

Freeze the old scheme on a announced date, audit claimed balances against whatever records exist, publish each participant's opening balance over WhatsApp with a dispute window of 2–3 weeks, then credit accepted balances as opening points in the new platform. Honour generously in doubt — the goodwill cost of disputed ₹500 balances is far higher than the payout — but cap and investigate outliers before crediting.

What does a good hypercare period look like?

Four to six weeks after go-live with named owners and daily rhythm: a stand-up reviewing enrolments, first-scan activation, payout success rate, helpdesk tickets and fraud flags; a 24-hour SLA on blocked payouts; weekly field feedback from pilot RSMs; and a fortnightly steering review that decides reward or process corrections. Hypercare ends when payout success is stable above 98% and ticket volumes flatten, not on a calendar date alone.

Do implementation costs attract TDS too?

The rewards themselves do: under Section 194R, any benefit — UPI cash, redeemed points, gifts distributed at enrolment meets, free demo kits — counts toward the ₹20,000 per-PAN annual threshold, after which 10% TDS applies. Even launch gifts like branded tool kits must flow into the same per-PAN ledger, which is why benefit tracking has to be centralised in the platform from day one.

Implementation, minus the nine-month build

Unotag ships serialisation, SKU-points engines, progressive PAN KYC, WhatsApp onboarding, instant UPI payouts and 194R automation as configuration — your team runs the rollout, not a software project.

Related reading