Software
Digital Product Passport software
A passport is an output; the software question is what produces it and keeps it true over years. The list below is what the texts imply a system has to do. Under each item is what Listrar does today — and where it stops.
One canonical record per product
The passport, the feed and the registry filing must agree. Listrar keeps a single record per product, at model, batch and item level, and renders every output from it. Nothing is copied into a second system to be published.
Fields that follow regulation
The delegated acts will add data points for years. Listrar's schema is regulation-driven: a requirement in the regulation registry maps to an attribute profile, and the record gains the field without a migration. Each fact sheet shows the current support status for its text.
Identifiers and a resolvable page
Every record has a GS1 Digital Link address at /01/{gtin}, with batch and item extensions, and resolves to a server-rendered page carrying Schema.org Product JSON-LD. The printed carrier does not change when the record does.
Access tiers and evidence
Every field carries a disclosure tier — public, customs, recycler, regulator — and the evidence behind it: source, verifier, validity, substantiation level. Suppliers contribute to the record directly; a supplier seat is free.
Machines as readers
Marketplaces, verifiers and AI agents read the same record through the feed and the MCP server, at the public tier, without scraping.
What Listrar does not do
Four limits, stated plainly.
- It does not certify products or grant conformity; it evidences what is recorded.
- It does not replace the delegated act's data set; it holds it.
- It does not give legal advice; the fact sheets summarise the texts and link to EUR-Lex.
- It is not the EU registry — see the registry page.