Unit-level digital identity
A unique, signed identifier for each unit, with the minimal data that describes it: manufacturer or importer, product and presentation, origin and lot.
One layer of identity, traceability and verification for real products
Traza brings together three things that usually live apart: the identity of each unit, the record of its lifecycle, and a public, simple way to check both.
What the platform does
Six capabilities that combine according to the deployment. None of them requires replacing the systems an organization already uses.
-
-
Chain event recording
Every moment of the lifecycle — issuance, labelling, press proof, record activation, lookups and issuance closure — is recorded as an event with date, place and responsible party.
-
Public verification
Anyone verifies a unit from the browser, with nothing to install and no account to create. The result is explained by signals and in plain language.
-
Institutional control
Regulators and companies consult the registry, follow anomalies, coordinate field inspections and export information for audit.
-
Rules configurable per tenant
Each deployment defines its brand, its identity fields, its event types, its roles and the context the public sees when verifying.
-
Discrepancy reporting
Whoever verifies can report a difference between what they see and what the registry says, with minimal, optional data.
The identity of a unit
A Traza identity is a brief, signed record that answers four questions about the unit. It contains no personal data. It does identify the issuing company, including its tax identifier: the responsibility of whoever places the product on the market is public by design.
- Manufacturer / importer
- The organization that produced the unit or brought it to market, and that signs it as issuer.
- Product / presentation
- What it is and in what format: type, variant, packaging and declared content.
- Lot and expiry
- The production or import lot and the expiry date, to compare against what is printed on the container.
- Identifier status
- Whether it is issued, activated, under review or voided, and since when it has been looked up.
TRZ-7F2K-6C2A-84MZ
- Manufacturer / importer
- Cafetalera Monte Azul
- Product / presentation
- Café Monte Azul · medium roast · 500 g bag
- Lot and expiry
- COS-MA-26-07 · best before 09/2027
- Identifier status
- Activated · lookups recorded
- Checks
- Valid signature · active record · matching data · no alerts
Target architecture
The design principle is to separate three planes that talk to each other through events and never through cross queries: that way a bulk generation of identifiers never competes with one person’s lookup in front of a shelf. What follows is the architecture the platform is designed toward.
-
Issuance plane
Derives and signs identifiers per order. Keys are held in a hardware security module, derived per issuance: administering a key and using it are separate permissions.
-
Verification plane
The hot path: it resolves the public lookup, evaluates signature, registry, data match and signals, and returns an explained result. It must keep answering even while issuance is under maintenance.
-
Analytics and audit plane
Append-only: every issuance, download, activation and status change is recorded. No UPDATE, no DELETE — revoking is a new event, not a correction of the previous one.
-
Read-only mirror
The institution governing a deployment receives a read-only copy so it can audit without depending on the operator. It is the primary/secondary repository pattern of the European tobacco system.
-
Integration
Interfaces to issue and activate from existing management systems, and to export information back to them.
Target product architecture. Cryptographic and security controls are implemented and audited in each deployment.
What is checked when verifying
A verification does not give a single verdict. It evaluates four signals separately and explains them, so that whoever verifies knows what was checked, how much confidence it provides and what the next step is.
-
Signature
Whether the identity was issued by the expected issuer and has not been altered.
-
Registry status
Whether the identity is active, suspended or revoked, and which events are recorded for it.
-
Data match
Whether what the label shows matches what the registry says: product, presentation, lot and expiry date.
-
Anomalies
Whether there are signals worth reviewing: repeated lookups of the same code, inconsistent locations or events out of sequence.
A valid signature indicates that the identity was issued; it does not describe the physical content or prevent a label from being copied. That is why the result is never reduced to a single word: it is explained, it comes with a next step, and physical inspection remains necessary.
Co-brand and white-label per tenant
The master brand lives at traza.technology. Each deployment — by country, regulator or industry — can present its own visual identity and its own verification context, on the same platform.
- Co-brand lockup or own brand (white-label) in each deployment
- Configurable accent colors, context texts and next step
- Identity fields and event types specific to each sector
- Roles and permissions defined by each institution
- Public verification reads the tenant from the URL and adapts the result
Alcoholic beverages
Example co-brand for a pilot proposal. It does not imply an official relationship, approval or implementation.
The tenant lockup shown is a co-brand example included in a pilot proposal. Its use is subject to approval by the corresponding institution and does not imply an official relationship, endorsement or approval.
The example shown corresponds to the spirits use case: a typographic co-brand lockup included in a pilot proposal addressed to a regulator. It is subject to approval and does not imply an official relationship.
Integration with existing systems
The platform is designed to coexist with the management, warehouse and logistics systems organizations already use, without replacing them.
- Receiving events from management and warehouse systems (ERP, WMS) through documented interfaces
- Issuing identities in batches from production or import orders
- Exporting the registry for audit and analysis
- Issuer authentication and traceability of who reports each event
Integration capabilities are described generically and without naming products: each deployment agrees its own connectors.
See the platform in action
The three views show public verification, the journey of a unit and the institutional dashboard.