| Capability | Scantrust | BL.INK | Flowcode | QRCompliance.us |
|---|---|---|---|---|
| Identity & Registry | ||||
| Persistent Registered QR Identity | ◐ | ○ | ○ | ● |
| Registry-Backed QR Record | ◐ | ○ | ○ | ● |
| Identity-Level Dossier | ◐ | ○ | ○ | ● |
| Issuer / Company Association | ● | ◐ | ◐ | ● |
| Certification State | ◐ | ○ | ○ | ● |
| Registration State | ◐ | ○ | ○ | ● |
| QR Lifecycle State (Pending → Certified → Revoked → Archived) | ◐ | ◐ | ◐ | ● |
| State-Driven QR Routing | ◐ | ◐ | ◐ | ● |
| Security & Enforcement | ||||
| Real-Time Revocation / Lockout Logic | ● | ◐ | ◐ | ● |
| Geographic + Registry-State Control | ◐ | ◐ | ◐ | ● |
| Anti-Counterfeit Authentication | ● | ○ | ○ | ◐ |
| Tamper-Evident Label Support | ● | ○ | ○ | ◐ |
| Compliance Flags Bound to Identity | ◐ | ○ | ○ | ● |
| Enforcement-Triggered Alerts | ● | ◐ | ◐ | ● |
| Offline Verification Mode | ◐ | ○ | ○ | ◐ |
| Flexibility & Control | ||||
| Dynamic Destination / Redirect Control | ● | ● | ● | ● |
| Time-Based Routing | ● | ● | ● | ● |
| Location-Based Routing | ◐ | ● | ◐ | ● |
| QR Redirect Versioning Control | ● | ● | ● | ● |
| Operator / Authority Roles | ◐ | ● | ◐ | ● |
| Custom Jurisdiction / Compliance Logic | ◐ | ◐ | ◐ | ◐ |
| Data, Audit & Integration | ||||
| Scan / Event History Bound to Identity | ● | ◐ | ◐ | ● |
| Protected Audit History | ◐ | ● | ◐ | ● |
| Batch / Group Association | ● | ◐ | ◐ | ● |
| GS1 / External-System Interoperability | ◐ | ● | ◐ | ● |
| Scalable Enterprise Deployment | ● | ● | ● | ● |
| Operational Record After Scan | ◐ | ○ | ○ | ● |
Identity, not links
A registered QR identity has an owner, a lifecycle and a record. A link has none of those.
Validation, not marketing analytics
The question answered at scan time is whether applicable requirements are satisfied right now.
Evidence as a by-product
Every evaluation and state change is recorded, so audits read history instead of rebuilding it.