What is a QR code loyalty program in India?
A QR code loyalty program India brands use for dealers and retailers puts a unique code on every pack you ship. The partner scans it with the phone camera they already have, sends one pre-filled WhatsApp message, and points credit against a scheme you defined. There is no app, card or portal login. Codes are generated in print-run batches (quantity, product, scheme, redemptions-per-code — almost always one), exported as PDF, PNG or CSV, and placed under a scratch layer, inside a flap, or on the label. Single-use stops reuse; it does not stop warehouse scanning or photographed codes at volume — that needs location and a hold queue. This is channel loyalty, not café stamp-cards for shoppers. Ominiflow runs the official WhatsApp conversation; unique-code factories and printer files are a specialist engine beside the chat.
Last updated: 18 September 2026
A QR code loyalty program in India puts a unique code on every pack you ship, and pays channel partners for scanning it. No app, no card, no portal login. The dealer or retailer scans the code on the product, sends one WhatsApp message, and the points land against their account in the same chat.
This page is about the codes themselves: how they are generated, how they reach packaging, why each one should work exactly once, and how you read results afterwards. If you are looking for consumer stamp-cards — café visits, D2C VIP after Shopify checkout — that is a different earn event. Start at the WhatsApp loyalty program hub. What a QR code loyalty program India trade brand actually needs is unique-per-pack channel loyalty, not a static “scan for 10% off” poster. Scheme maths: dealer incentive program software.
1×
redemption per code is the sane default for channel loyalty
3
export jobs: PDF for printers, PNG for artwork, CSV for lines that render their own marks
Batch
redemption rate per print run — a 4% batch hides inside a 26% program average
Batch size caps and UI labels differ by vendor. Align batches to print runs so redemption data stays readable. Ominiflow is not the packing-line QR factory.
Start here if you are in a hurry
- A QR code loyalty program India trade brands actually need is unique-per-pack channel loyalty, not a static “scan for 10% off” poster.
- Generate in batches that match print runs: quantity, SKU, scheme, single-use. Keep the batch id for the life of the codes.
- The platform gives you a file. Your printer puts it on the pack. Anyone claiming they “print for you” is describing your converter’s job.
- Scratch or inner-pack placement is security. Open labels are cheap and photographable.
- Single-use logs the second attempt. Warehouse scanning still needs location and batch-speed checks — fraud prevention.
What a QR code loyalty program is, and who it is for
The mechanic is simple. Every pack carries a code that no other pack carries. When a partner in your distribution chain sells or stocks that product, they scan the code and earn points against a scheme you have defined. Points accumulate, thresholds get crossed, rewards get issued.
The reason brands choose codes over invoice uploads or self-declared sales is verification. An invoice can be edited. A sales claim can be inflated. A unique code on a physical pack can only be claimed once, by one partner, and only after the pack has actually moved — with the caveats in the fraud article.
In practice this suits FMCG, paints and chemicals, building materials, electrical goods and agricultural inputs, because they share a shape: the brand sells to a distributor, the distributor sells to a retailer, and the brand loses visibility after the first hop. Codes restore that visibility without asking anybody to file a report. They will not restore billed value or margin. Do not use them as a fake ERP.
How unique codes are generated in batches
Codes are produced in batches rather than one at a time, because packaging runs in batches. You specify four things:
- Quantity. How many codes this print run needs. Vendor caps vary; ten thousand in a single batch is a common ceiling. Prefer alignment with the actual print run over one giant number.
- Product. Which SKU the batch belongs to. Point values differ per product, so a premium pack can be worth several times an economy pack.
- Scheme. Which loyalty scheme the codes are attached to. A code generated against a festive scheme should not credit under a different scheme.
- Redemptions per code. For channel loyalty this is almost always one. The setting exists because some campaigns want a different rule. The sane default is single use.
You then pick an export format. PDF is the usual choice for a printer. A PNG archive suits a design team laying out artwork manually. CSV suits a packaging line that generates its own visual assets from raw code strings.
Every batch gets an identifier, and that identifier stays attached for the life of the codes. Months later you can still ask how a specific print run performed. That is the difference between a QR code loyalty program and a folder of images on someone’s desktop.
Getting codes onto your packaging
This is the part software vendors gloss over, so here is the honest version.
The platform generates the codes and hands you a file. Your printer or packaging vendor puts them on the pack. There is no magic integration that prints for you. Any vendor claiming otherwise is describing your printer’s job, not theirs. What the platform should do is make the handoff clean: a finished file, batch identifiers so a damaged or scrapped run is knowable.
Practically, brands place codes in one of three positions:
- Under a scratch layer — most secure, most expensive.
- Inside a carton flap or under a cap — cheap, works when the pack has to be opened to sell.
- Openly on the label — cheapest and weakest, because anyone who can see the pack can photograph the code.
Choose the position before you generate the batch, because it determines how much fraud pressure the codes will face. Then brief the field team: an app they will not install is not the claim path — why dealer loyalty apps fail.
Why every code should be single use
A code that can be claimed twice is not a loyalty mechanic, it is a leak.
Each generated code should be unique across the entire platform, not just within its batch. Once a code is claimed, it is spent. A second attempt should not credit points, and it should not silently fail either. It should be recorded. That recording matters more than the rejection. A single duplicate attempt is usually an honest mistake — someone scanning twice because the first scan did not seem to register. A pattern of duplicate attempts from the same partner is something else, and a pattern only becomes visible if the failures are logged rather than discarded.
Single use handles code reuse. It does not by itself handle the harder problems: a warehouse employee scanning a carton of packs before they ever reach a retailer, or codes photographed and shared in a group. Those need location verification and behavioural checks. Short version: a claim is checked against where the partner has actually been scanning from, and a claim from an implausible distance is held for a person to look at rather than auto-approved or auto-rejected.
What happens the moment a code is scanned
The partner uses their phone camera. No app is involved, because every smartphone sold in India for years has scanned codes natively.
The scan opens WhatsApp with a claim message already filled in (or a lightweight page that posts into WhatsApp). They send it. That is the entire interaction from their side.
Behind it, the ledger should check that the code exists, that it has not been claimed, that the scheme is currently running, that the partner is in a region the scheme covers, and that the scan location is plausible. If all of that passes, points credit and the partner gets a confirmation in the same chat with their updated balance. If something does not pass, the claim is held rather than rejected outright.
The reason this runs over WhatsApp rather than an app is adoption. Channel partners do not install brand apps, and programs that require one die quietly in the first quarter. Running the claim through the WhatsApp Business Platform removes the download entirely. Identity is the sending number; it cannot be borrowed without the phone. Official platform only — unofficial “WhatsApp API” on a personal number will get banned mid-scheme.
Credit confirmations are usually utility. “You are 200 points from a hamper” is marketing. Category mistakes are the expensive ones — India utility versus marketing on the live rate card, walked through in the hub.
Reading redemption data, batch by batch
A code that is generated and never scanned tells you something. Usually it tells you that stock is sitting somewhere, or that a region never got briefed.
Every batch should carry its generated count against its redeemed count, so redemption rate is visible per print run rather than as a single program-wide number. That distinction is the useful one. A program at twenty-six percent overall might contain one batch at fifty percent and another at four percent, and the four percent batch is the one worth a phone call. A batch that redeems in days when peers take weeks is the warehouse-scan signal.
Beyond batches, scan data should break down by scheme, by region and by product, and the daily trend should show what a festive push actually did rather than what the plan assumed it would do.
Fulfilment, and why it stays a human decision
Many platforms in this category promise instant automated payouts, straight to a UPI handle, the moment a threshold is crossed. Instant cash is a design choice, not a requirement, and it is the single fastest way to drain a channel loyalty budget. The moment value leaves the building without a person looking at it, every weakness in the program becomes a direct cash loss instead of a flagged claim.
Brands running large dealer schemes generally want the opposite: a list of who qualified, a record of who approved it, and a date. Qualification automatic, fulfilment deliberate. If instant cashback is a hard requirement — typical of mason/painter influencer programs — you are in a payments-rail product, not a dealer scheme recorder. Dealer vs influencer loyalty.
What it takes to run a QR code loyalty program in India (and what a QR code loyalty program India printer actually needs)
You need three things: approved message templates in the right category, a WhatsApp number connected through Cloud API, and a printer who can accept a code file. On your side, someone owns the review queue. It is not a large job. It is not a zero job. Programs that nobody watches drift.
Ominiflow provides the official number, chatbot, tags, shared inbox and Meta fees at published rates (0% markup on conversation fees). Unique-code generation, printer PDFs and GPS-learning fraud are a specialist channel engine connected by webhook. D2C points from Shopify orders do not need pack QR at all. We will say that on the demo so you do not buy the wrong layer. Get WhatsApp API · Pricing.
Related loyalty reading
- WhatsApp loyalty program — hub: D2C VIP + channel scan-and-earn
- Why dealer loyalty apps fail — seven steps vs three
- Dealer vs influencer loyalty — who you pay and how you settle
- Loyalty program fraud prevention — hold queues, warehouse scans
- Dealer incentive program software — tiers, mix, regional schemes
Print unique codes; claim them on the WhatsApp they already have
Start the official number on Ominiflow. Sit a QR batch engine beside it when the earn event is a pack, not a Shopify order.
Start free on Ominiflow Book a demo
Pricing · Loyalty hub · D2C guide
FAQ
How are unique QR codes generated for each product? expand_more
You specify quantity, product, scheme and redemptions per code. The platform generates that many unique codes in one batch and exports a print-ready file. Every code should be unique across the whole platform, not only within its batch.
Can a QR code be scanned more than once? expand_more
Not when redemptions per code is one, the normal setting for channel loyalty. The first valid claim spends the code. Later attempts credit nothing and should be recorded so patterns are visible.
What file format does my printer need? expand_more
PDF suits most printers. A PNG archive works when a design team places codes into artwork by hand. CSV works when a packaging line generates visuals from raw strings. You choose the format when you generate the batch.
What happens if someone photographs a code and shares it? expand_more
The first claim spends the code, so only one person is paid. Photographed codes become a real problem at volume; location and behaviour checks catch that. Scratch layers or inner-pack placement prevent it at source.
How do I know how many codes have been redeemed? expand_more
Each batch should show generated versus redeemed, so you get a rate per print run rather than one number for the whole program. Also break down by scheme, region and product.
Does Ominiflow generate 10,000 unique pack QR codes? expand_more
Ominiflow runs Cloud API messaging, chatbot, tags and inbox. Unique-code batches and printer PDFs belong in a channel-loyalty engine connected by webhook. D2C points from Shopify orders do not need pack QR. Last updated 18 September 2026. Ominiflow is the WhatsApp conversation layer. Unique QR generation is a specialist packing-line job beside the chat.
