Your mandated QR code is a sensor. Start reading it.
The DPP QR code you are required to put on every product does something no compliance document has ever done: it phones home. Every scan — by a consumer, a repairer, a reseller, a customs officer — is a timestamped, located signal from a product that has left your control. PassPer scan analytics turns those signals into the post-sale distribution picture brands have never had, without tracking a single individual and without touching the compliance layer.
Last updated:
In one line: PassPer scan analytics reads the scans your mandated DPP QR code already generates — item-level counts, distinct devices, per-SKU geography — as aggregate, pseudonymous distribution intelligence, with the regulated data always served first and tracking-free.
What you see when the QR gets scanned
PassPer records each resolution of your passport links as a pseudonymous event and aggregates them into four views:
Item-level scan counts — how often each individual passport is opened, so a single unit that is scanned twenty times stands out from one scanned once.
Distinct devices — an estimate of how many different devices scanned an item, separating one curious owner from many hands touching the same unit.
Per-SKU geography — where in the world each product line is actually being scanned, at coarse regional resolution.
Grey-market concentration signal — a flag on SKUs whose scan geography concentrates somewhere your distribution wouldn't explain.
Data brands have never had
Everything most brands know about products after the point of sale is second-hand: distributor sell-through reports, retailer panels, warranty cards nobody returns. Scan analytics is first-hand. It is your own product, in the field, announcing where it is and that someone is paying attention to it. That answers questions that were previously unanswerable: which markets a SKU really penetrates, whether products sold into one region stay there, which lines get engagement deep into their life — the raw material for distribution, after-sales and anti-diversion decisions.
Compliance-safe by construction
ESPR requires the mandated passport data to be freely accessible and prohibits tracking consumers who scan it. PassPer's architecture makes that a feature rather than a constraint: the regulated data always loads first, tracking-free — no cookies, no consent wall, no scripts gating access. The analytics layer sits beneath it and is aggregate and pseudonymous by construction: coarse location only, no personal data, no individual profiles, nothing to serve a consent banner about. You get distribution intelligence; the person scanning gets exactly what the regulation promises them, untouched.
No integration, no extra ink
The sensor is the QR code the law already requires. PassPer issues your GS1 Digital Link QR as part of the passport itself, so analytics is on from the first scan of the first unit — no SDK, no app, no separate marketing code competing for label space. If your passports don't exist yet, that is the place to start: run the free readiness check to see what your products need, or explore the wider Living Passport concept to see where the channel goes from here.
Frequently asked questions
Is scan analytics compatible with the ESPR ban on tracking consumers?
Yes, because of how it is built. The mandated passport data is served first, tracking-free, with no cookies and no consent wall. The analytics layer records aggregate, pseudonymous scan events with coarse location only — it counts scans and estimates distinct devices without identifying or profiling anyone.
Can I see who scanned my product?
No, deliberately. There are no identities, no profiles and no precise locations in the system — that would breach both ESPR's consumer-tracking prohibition and data-protection law. What you see is the shape of activity: which items and SKUs are scanned, how often, on roughly how many devices, and in which regions.
What can scan geography actually tell us?
Where your products physically are after they leave your control. Per-SKU scan maps reveal which markets a product line really ends up in — which is how grey-market diversion shows up: a SKU sold into one market that keeps resolving scans in another. See our grey-market detection page for that use case.
Do we need extra hardware or a special QR code?
No. The same GS1 Digital Link QR code that ESPR requires on the product is the sensor. Any phone camera scanning it resolves through your PassPer passport, and the analytics come from those resolutions — nothing extra printed, embedded or installed.