After the scan

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.

What comes back

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 registration

The holder registers themselves against the item. Confirm or reject it — and you now know who has your product.

Needs a decision
🧾

Warranty registration

One row per item: who registered, when, and against which policy. Most arrive on their own when a customer scans and registers.

Recorded
🛠️

Warranty claim

Raised against a registered unit, with its full scan history already attached to the case.

Needs a decision
🚩

Counterfeit report

A scanner tells you something is wrong. You author the questions they are asked, per record.

Recorded
🎫

Ticket check-in

Appears the moment someone is admitted at the door, against the individual ticket.

Recorded
💬

Form & poll responses

What people sent back from your engagement pages — facts, not requests.

Recorded
What you decide

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 states 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.

SignalA report, a clone, or an impossible journey between two scans.
InvestigationOpened against the individual code, with its scan history attached.
DecisionWorked through to an outcome you choose, not an automatic verdict.
On the recordThe code carries the result — including into recall or revocation.

Patterns surface alongside the individual cases: authentication failures over time, and counterfeit hotspots by city.

When the answer is no

A code can refuse.

Verification is not always a yes. The same per-unit identity that proves an item is genuine can also decide whether this scan, right now, is allowed — which is what turns a code into a ticket, a membership or a licence rather than a label.

🎟️

Admit once

A ticket is checked in at the door and recorded. Scanned again, it is no longer a valid admission.

📅

Expire per person

A membership card carries its holder’s own expiry, not the batch’s. When the date passes, the scan refuses.

🙋

Grace for late payers

Grace days keep a late renewal valid for a few days, so nobody is turned away mid-visit over an invoice.

🔢

Limit the scans

Cap how many times a single code may be used, for entitlements that are meant to run out.

Who has it now

Find out who actually owns your product.

The first scan of a product code is recorded as its baseline. If that scanner registers as the owner, the claim comes to you to confirm or reject. Most brands never learn who is holding their goods after they leave the distributor — this is a direct line to that person, on a code you were printing anyway, and it is what makes the later warranty and recall steps land on a real individual rather than a batch.

Want your codes to report back?

Every plan includes these — they are what the scan actions do, not an add-on.

Talk to Us
?🧭Guide me

Your session has expired

You were signed out for inactivity, so that action was not saved. Sign in again to carry on — anything already saved is safe.