We didn't invent this pattern — we noticed it was already how several of our features had to work to be trustworthy.
A code is created with intent behind it — this offer, for this campaign, valid until this date, unique to whoever it's for.
Someone scans it, and the system checks it in real time — valid? already used? within the rules? — before approving anything.
Whatever happened gets logged — who, when, approved or rejected — so nobody has to take anyone's word for it afterward.
None of this is hidden or proprietary magic — it's a short, ordered list of checks against one record. Here's roughly what happens between a scan and an answer:
// A scan comes in for code ID CPN-88213
1. Does this ID exist in our records? → yes
2. Has it already been redeemed? → no
3. Is today within its valid date range? → yes
4. Is this the location/merchant it was issued for? → yes
Result: APPROVED — logged at 14:32:07, marked redeemed
// The same ID, scanned again five minutes later
1. Does this ID exist in our records? → yes
2. Has it already been redeemed? → yes, at 14:32:07
Result: REJECTED — logged at 14:37:52, reason: already redeemed
Both outcomes get written down. That's the part that's easy to skip when you're just generating an image — and the part that makes the difference between "we think the promotion worked" and "here is exactly what happened." We go a level deeper into the serialization and scan-history mechanics in what actually stops a QR code from being copied.
These aren't hypothetical — they're existing QRTRAC features already built around issue, redeem, and prove.
One-time-use discount codes that can't be duplicated or reused.
Learn more →Product registration tied to a serialized code, checked once at activation.
Learn more →Passes verified at the door, with entry logged and duplicates rejected.
Learn more →Rewards issued and tracked per customer, redemption logged over time.
Learn more →Every scan along a supply chain adds to a single traceable record.
Learn more →Checkpoints logged per batch so a failed inspection is never silent.
Learn more →Standardized product identifiers that resolve to a verifiable record, not just a webpage.
Learn more →Every approval and rejection rolled up into reportable, exportable data.
Learn more →Window and door manufacturers scan a QR code at each station to log real-time production status.
Learn more →One-time-use redemption and scan logging aren't a premium add-on — they're part of what a dynamic QR code already does in QRTRAC, on every paid plan, with unlimited scans and no per-redemption fees. See what's included at each tier on our pricing page, or read more about how we build on our about page.
The serialization and scan-history mechanics behind Redeem, explained in depth.
What Proof looks like once it reaches your dashboard — scans, location, device, timing.
Applying Issue → Redeem → Proof to real coupon and promotion campaigns.
QRTRAC's dedicated anti-counterfeit verification flow — Redeem, taken to its strictest form.
What this is, what it isn't, and how it works today.
No — it's the pattern several QRTRAC features already follow (issue, redeem once, log proof), given one name so it's easier to talk about. Any QR code you create today can already be set up this way; there's nothing extra to buy.
Each code is issued with its own unique ID, not a shared code reused across a campaign. When it's scanned, the system checks that specific ID's redemption history before approving it — a second scan of the same ID is rejected, not just discouraged.
A timestamped log of every scan attempt against a code — approved or rejected, when, and which code — that you can look back at afterward instead of relying on someone's word for what happened. See our analytics guide for what that log looks like in the dashboard.
Fraud-resistant coupons, warranty activation and product registration, event passes, loyalty tracking, and batch/lot track-and-trace are all built around issue-once, redeem-once, log-everything today.
No. One-time-use redemption and scan logging are part of generating a dynamic QR code in QRTRAC on every paid plan — see pricing for what's included at each tier.
No. The same Issue → Redeem → Proof shape applies anywhere a code stands in for something with a rule attached: a warranty claim, an event ticket, a batch quality checkpoint, a GS1-linked product record, or a loyalty reward.
Start free — no credit card required.