Units without a verifiable identity
Control is usually done by lot or by document. Without a per-unit identity, it is hard to tell a legitimate product from a copy with the same label.
Control by unit and public verification carrying each institution’s brand
For regulators and control agencies that need to know which units are on the market, where they come from and whether what is sold matches what is registered.
Common challenges
Regulated markets share similar problems, regardless of the product. These are the ones Traza sets out to solve.
-
-
Inspection that is hard to prioritize
Field teams are limited. Without signals from the registry, there is no way to decide where to inspect first.
-
Scattered records
Production, import and oversight record their data in different systems that can rarely be cross-checked.
-
No public verification channel
The public has no simple way to check a product or to flag it when something does not match.
Our approach
We propose an identity and registry layer with institutional rules, public lookup and inspection. Integrations and permissions are agreed and validated for each deployment.
-
Signed unit-level identity
Each unit receives an identifier signed by its issuer, under rules defined by the institution.
-
Auditable registry
The design provides for recording issuance, labelling, activation, lookups, signals and closure, with the responsible party and date for audit.
-
Field inspection within the deployment
Inspectors verify on site, check against the registry and record what they observe.
-
Co-brand by country and regulator
Public verification can show the institution’s brand alongside Traza’s, always with its approval.
-
Public verification
Anyone can query a unit and prepare and download a local report. This website does not send it or change the registry; it must be handed to the responsible organization.
How it is deployed
An institutional deployment advances in well-defined stages. The usual order is as follows.
-
Define the framework
The institution establishes which products are identified, which data describes a unit, which events are recorded and who can consult them.
-
Issue identities
Manufacturers and importers issue signed identities for their units according to the rules of the framework.
-
Label and activate
The issuer confirms printing and, once production has finished and the record is complete, activates the codes of the units produced.
-
Open public verification
The public queries from the browser, under the institutional brand if approved. On this website they can download a local report to hand over through an organization’s channel.
-
Inspect and act
The proposed deployment provides for reviewing signals, recording actions and closing cases. Reports downloaded on this website do not automatically enter that view.
Expected outcomes
What a deployment of this kind sets out to achieve, expressed without figures.
- Per-unit visibility over what circulates in the regulated market
- Better-targeted field inspections thanks to signals from the registry
- Public lookup and local report preparation with no installation or account
- An auditable registry that supports control and accountability
- An institutional brand present at the moment of verification
Expected outcomes are qualitative. No figures or measured results are presented.
See it in the platform
-
Institutional view
Explore sample units, signals and inspections. This view illustrates oversight work; it does not receive reports downloaded from public lookup.
-
Public verification
See what the public would see when verifying a unit, with the co-brand example from the medicines use case.
-
Unit lifecycle
Follow a unit from its issuance through its lookups and see which events are recorded.
Nothing above claims a relationship with governments or agencies, certifications or measured results. The medicines use case is a pilot proposal.
Let’s talk about a well-scoped pilot
A pilot starts with one product, one framework of rules and a small group of actors. We can help define it.