A scan is a conversation, not a lookup.
Most QR platforms stop when the page loads. Ours keeps going: the people scanning your products send things back, some of it needs a decision from you, and a code can refuse a scan outright.
You have their attention. Most platforms spend it on a verdict.
A verification scan is one of the few moments a customer starts a conversation with a brand while holding the product, usually minutes after unboxing, already wanting an answer. There is no attention to buy here. You have it. What opens the scan is yours to author — a page of your own before the result, and an action after it.
Your page, before the answer
The item’s name, the brand line, a sentence about it — in your words and your type, a beat before the verdict. The proof then reads as confirmation of something already framed, instead of being the whole experience.
Harder to imitate
A counterfeiter can copy a bottle and a label. A scan that opens on a composed brand page is expensive to fake convincingly and obvious when faked badly. Raising the quality of the genuine experience raises the cost of copying it.
A reason to scan the next one
Most scanners are curious rather than suspicious, and a bare verdict gives that person nothing. An opening worth reading, and an offer after it, is what turns a one-off check into a channel you own.
The opening page belongs to the print run, not the product — so a festive run, a market-specific line or a collaboration edition can each open differently while the product record stays identical. No new content to maintain, and no reprint.
Your codes collect, they don't only tell.
Everything a scanner sends lands in one inbox, newest first, tied to the individual unit it came from. Some of it is waiting on an answer from you. The rest is simply a record of what happened.
Ownership registrationNeeds a decision
The holder registers themselves against the item. Confirm or reject it — and you now know who has your product.
Warranty registration
One row per item: who registered, when, and against which policy. Most arrive on their own when a customer scans and registers.
Warranty claimNeeds a decision
Raised against a registered unit, with its full scan history already attached to the case.
Counterfeit report
A scanner tells you something is wrong. You author the questions they are asked, per record.
Ticket check-in
Appears the moment someone is admitted at the door, against the individual ticket.
Form & poll responses
What people sent back from your engagement pages — facts, not requests.
An alert is the beginning of the job, not the end of it.
A counterfeit report, or a code scanned somewhere its registered owner cannot plausibly be, opens an investigation. You work it through to a decision, and what you decide is recorded against the code — so the next person to look at that unit sees the outcome, not just the alarm.
Something does not add up
A report, a clone, or an impossible journey between two scans.
Opened against the individual code
With that unit's scan history already attached.
Worked through to an outcome you choose
Not an automatic verdict.
The code carries the result
Including into recall or revocation.
Patterns surface alongside the individual cases: authentication failures over time, and where suspect scans come from — by country, and by town when the phone shares its location. See the analytics →
A code can refuse.
Verification is not always a yes. The same per-unit identity that confirms a genuine item can decline one — recalled, revoked, quarantined, expired, or already used. The scanner is told, on your branded page, rather than shown a result that quietly pretends everything is fine.
Put an identity on every unit.
Tell us what you make and we'll size it with you.