QR Code Coupons: Tracking Redemptions From Shared Codes to the Till
A cafe prints 500 flyers with a QR coupon for 10 percent off. Three weeks later the owner knows two things: the flyers are gone, and a few customers mentioned a discount. Everything in between is guesswork. Coupons are the QR use case where the tracking design you pick before launch decides what you will ever be able to know.
Shared code or unique codes
A shared code is one QR pointing at one coupon page, printed everywhere. It is cheap and instant, and with a dynamic code behind it you learn how many people scanned, when, and on what devices. What it cannot do is enforce. It cannot limit one redemption per customer, cannot tell redeemers apart, and if the offer escapes to a bargain forum, you can only kill the whole campaign, not the one leaked copy.
Unique-per-customer codes invert the trade. Each recipient gets a personal code by email, by SMS, or as a numbered print run (bulk generation exists for exactly this). Single use becomes enforceable, every redemption has a name attached, and one abused code dies alone. The price is operational: you need a channel that reaches people individually, and a till process that validates codes instead of glancing at them.
| One shared code | Unique per customer | |
|---|---|---|
| Limit one use per person | No | Yes |
| Know who redeemed | No | Yes |
| Revoke a leaked copy | Whole campaign only | Just that code |
| Effort to launch | Print and go | Individual delivery plus till validation |
| Natural home | Flyers, posters, table tents | Email lists, loyalty members |
Most small campaigns should start shared and graduate to unique codes when a specific abuse actually appears in the numbers. Enforcement you do not need yet is just friction at the till.
Redemption at the till: three models
Show the screen
The customer displays the coupon page, staff applies the discount, nothing is recorded. Zero setup, zero training, and honest leakage: the same screenshot works every day and staff cannot tell. Acceptable when the discount is small, sits inside your margin, and the goal is foot traffic rather than precision.
Staff marks it used
The coupon page carries a redeem button that staff taps at the moment of redemption, or a short staff code typed into the page. With a shared code this produces a redemption count; with unique codes it enforces single use. It costs about 5 seconds per redemption and one line of staff training, and it is the cheapest route to a real redemption number.
POS integration
The coupon carries a promo code that the till scans or staff keys in, so the discount lives in the POS with exact revenue attribution. This is the only model that connects coupons to basket size, and the most work to launch, because the promo codes must exist in the POS first and staff need a script for mismatches.
Expiry that creates urgency without arguments
Short deadlines move people. "This weekend only" outperforms "valid until December", because December reads as never. But expiry is also where coupons produce their angriest till moments.
Three practices keep the urgency and drop the arguments. Print the expiry date on the coupon page itself in large text, not in fine print on the flyer. Use windows of 2 to 4 weeks for print, long enough to be seen, short enough to stay urgent, and shorter windows for email. And give staff a quiet grace policy that honors anything a few days past the date; the goodwill costs less than the argument. A dynamic code adds one more option: extend a deadline by editing the hosted page while the printed QR stays exactly the same.
Screenshot leakage, and when to care
Any coupon shown on a screen will eventually be screenshotted and forwarded. The useful question is not how to stop it but whether it costs you anything.
Often it does not. If the offer is 10 percent off and your margin absorbs it, a forwarded screenshot is a free flyer with better targeting than the ones you paid to print. People you never reached walk in and buy something.
Care when the economics flip: free-item offers, discounts that stack with other promotions, limited stock, or a first-order discount that regulars farm week after week. The fix ladder matches the models above: shared code with a staff tally, then unique codes, then POS validation. Climb one rung when a number tells you to, not because leakage feels vaguely wrong.
The two numbers that matter
Scan rate of the placement: scans divided by the people who plausibly saw it. A typical flyer gets scanned by 1 to 3 percent of the people who see it, while a table tent in front of a seated customer does considerably better. This number judges the placement and the offer's face value.
Redemption rate of scanners: redemptions divided by scans. Everyone in this pool already showed intent, so the rate runs far higher, and 10 to 30 percent is a common range for a decent offer with a store people can actually reach. This number judges the offer's substance and the friction of redeeming.
The gap between the two is the diagnosis. 500 flyers, 10 scans, 3 redemptions reads as: weak placement (2 percent), sound offer (30 percent of scanners redeemed), so fix distribution, not the discount. The reverse pattern, plenty of scans and almost no redemptions, means the coupon page overpromises, the store is too far away, or the deadline already passed.
Getting both numbers takes a dynamic QR code for the scan side and any till model above show-the-screen for the redemption side. QRolling's coupon QR code pages hold the offer, the expiry and the redeem flow in one editable place, and the wider retail context sits in QR codes in retail.
Start with the tally
Today, put a paper tally sheet at the till with one instruction: one mark per coupon shown. Within a week you have your first real redemption rate, and next to your scan count it tells you which half of the campaign needs the work.
