QR code copyable at will
Counterfeit scans the original and prints the same QR. Without an audit binding, the trail is not verifiable.
Case study · Manufacturer
Product authenticity from the factory.
Manufacturers register product batches with serial code and audit event. Multi-scans expose counterfeits, end-customers get a measurable trust signal.
Pilot pattern · Audit event per batch · Webhook for recalls
Compliance & hosting
Starting point
QR codes without cryptographic binding are counterfeit magnets.
Before SigID, the factory shipped products with a QR code that only pointed to the company website. Counterfeiters could copy the QR — end-customers had no way to tell.
No knowledge about first-scans
When was a product scanned first? Where? Nobody knows — multi-scans stay invisible.
Service tickets on authenticity questions
End-customers call support asking whether their product is genuine. Manual effort, no reliable proof.
How SigID helps
Four steps — product code with cryptographic audit event.
Production stays in the factory, SigID provides the audit binding and the end-customer signal.
Register batch via API
Manufacturer registers batch + serial code + manufacturer signature. Audit event is created at production time.
Print code
QR or NFC tag with the Audit-ID. Readable by any Trust App.
End-customer scans
Trust App returns trust level, first-scan date, number of past scans. Multi-scans flag counterfeit suspicion.
Webhook on recalls
On a batch recall, SigID emits a webhook — service can notify end-customers directly.
Outcome
47 counterfeit attempts detected per quarter, NPS +18.
Pilot pattern from the manufacturer program. All values are architecture targets for the GA phase, not representative customer data.
- Counterfeit attempts detected
- 47 / quarter
- NPS uplift
- +18
- Authenticity service tickets
- −72 %
vorher: 0 detected
vorher: Base 42
vorher: Base 100 %
Pre-launch — architecture targets from pilot patterns, no comprehensive customer data yet.
Example scenarios
How manufacturers use SigID concretely.
Register batch at the factory
“Production line calls the SigID API. 5,000 units are registered with manufacturer signature and batch ID. QR printing happens immediately after.”
Example scenario · Consumer goods manufacturer · 300 employees
- Codes per batch
- 5,000
- Per unit
- Audit event
Example scenarios based on module functionality. SigID is pre-launch — no representative customer data yet.
Manufacturer FAQ
Answers for production and anti-counterfeit.
Can the SigID API keep up with production speed?
Yes. The verification API targets p95 below 500 ms, batch endpoints register thousands of codes per second. Idempotency keys prevent double registrations.QR code or NFC tag?
Both work. The Audit-ID can be printed into a QR or written into an NFC chip. NFC is more robust against line-of-sight loss.Do end-customers need an app?
Trust App uses the smartphone camera or NFC. Optionally, a web fallback can be offered via QR resolver — with reduced trust level.What data ends up at the end-customer?
Only trust level, first-scan date and scan count. No personal data — data minimization is the default.
Test product code with audit binding?
Free plan, no credit card. Register the first batch in under 10 minutes.
- DSGVO-konform
- eIDAS-bereit
- Made in Germany