Technical standards & interoperability
The standards our platform is built on
Built on the open standards of the DPP ecosystem
A Digital Product Passport only works if it is interoperable — with the EU registry, with GS1 identifiers and with your partners' systems. WIARA's platform is built on the open standards of the ecosystem, so any system can read your passports, not only the platform that published them.
See what it looks like in practice on the platform and what the Digital Product Passport →
What do technical standards mean for your digital product passport?
A passport built on open standards can be read by market surveillance authorities and by your customers' systems, not only by the platform that made it. For manufacturers that means no lock-in: the data is readable outside any one vendor's system, and you can export all of it at any time. For importers collecting passports from suppliers, it means data in a format they can check.
Every DigitalProductPassport by WIARA passport opens from its own GS1 Digital Link QR code, carries JSON-LD you can inspect and is also available through a REST API. Try it on a demo passport. To see whether your product needs a passport yet, run the check.
Key capabilities
Technical standards & interoperability
We publish what we cannot do yet
The table below has three states: ✅ supported today, ◐ partly there — in preparation or not yet complete, and 🔜 on the roadmap. We publish all three — including the things we cannot do yet.
“Full compliance” is a sentence a buyer has no way to check. A table broken down by standard, with a date on it, can be checked in minutes. That is why we keep ours this way — and why it is worth asking the same of every provider you are looking at: a separate status per standard, and the date it holds good.
The criteria worth comparing them on are set out separately.
Standards & interoperability
Which standards and capabilities the platform supports today.
EU DPP Registry
◐ In preparation — The registry has been live since 20 July 2026 under Implementing Regulation (EU) 2026/1778. The platform produces passports in the registry’s format; the production connection is being built, and registration also requires a qualified electronic seal.
GS1 Digital Link
✅ Supported — A standard data carrier — a QR code that opens the passport and stays valid for the product's whole life.
GTIN
✅ Supported — Global Trade Item Number as part of the product's identification.
REST API
✅ Supported — Full programmatic access for integration with your ERP and PLM systems.
CIRPASS-2
✅ Aligned — Built to the CIRPASS-2 reference architecture and data models.
Per-field access levels
✅ Supported — every field and file is classified as public, professional or authority, and the public passport shows only the public fields. ◐ Authenticated access for professionals and authorities (eIDAS) is in development; it also depends on the European Commission completing its implementing rules.
EN 18216–18223
◐ Built to them — The platform implements the technical decisions the six standards lock in: GS1 identifiers, the QR code as the carrier, REST APIs, JSON-LD, long-term retention. A full conformity assessment has not been carried out.
EPCIS 2.0
🔜 On the roadmap — Supply-chain event traceability — coming on the roadmap.
How to check each of these
Every row above is a claim. Here is what each one rests on and where you can verify it yourself — the standard it follows and the page that shows it working.
Unique product identifier (EN 18219) — every passport is identified by a UPI built on the GS1 GTIN and opened through GS1 Digital Link, with a resolver conforming to ISO/IEC 18975. See it working in a demo passport or on the API page.
Data carrier (EN 18220) — The standard makes QR the primary carrier, with NFC and RFID as secondary; the platform outputs the QR code. Every demo passport opens from its own QR code.
Machine-readable content (EN 18223) — every published passport carries JSON-LD and Schema.org, not a proprietary format. View the source of a demo passport, or read the API page.
Programmatic access (EN 18222) — over a hundred operations documented to OpenAPI 3.0.3; the dashboard is a client of the same interface you are given. Details on API and integrations.
Long-term availability (EN 18221) — published passports stay reachable for the product's lifecycle plus ten years as our own commitment, with a full change history. Stated on pricing and security.
Legal status — the six standards EN 18216–18223 were cited in the Official Journal on 15 July 2026 and give a presumption of conformity with ESPR Articles 10 and 11. CEN-CENELEC published EN 18239 and EN 18246 on 16 September 2026, but neither is cited yet, so no presumption covers access rights or data authentication, ours or anyone else's. What citation means and where each of the eight standards stands: DPP harmonised standards.
Information security — ISO/IEC 27001:2022, certificate BG2026030401, issued by INCERT, valid to 3 March 2029. Verify it independently in the IAF global database.
EU registry — live since 20 July 2026 under Implementing Regulation (EU) 2026/1778. Our production connection is in preparation, and registration additionally requires a qualified electronic seal for your legal entity.
Who is responsible for what. WIARA answers for the platform: availability, data integrity, the passport format to EN 18216–18223, the audit trail and full export of your data in open formats. The manufacturer answers for the accuracy of the declared data and the conformity of the product — under the ESPR and the CPR that responsibility does not pass to a software provider. More on security.
How DigitalProductPassport by WIARA uses this
Interoperability is decided by the boring parts: which identifier, which carrier, which data format, which access tier.
DigitalProductPassport by WIARA is a cloud platform built by WIARA, a software company. It builds each passport around the identifier you already use, issues a GS1 Digital Link URL with a permanent QR code for the label, and serves the same data as JSON-LD for machines and as an accessible page in 24 EU languages.
The free plan covers 3 passports in total. What the platform does is set out on the product page, and the plans and their limits are on pricing.
Technical standards
Frequently asked questions
GS1 Digital Link is a standard way for a single QR code to point to a product's passport. We use it so the data carrier is interoperable and valid for the product's whole life.
EPCIS 2.0 (supply-chain traceability events) is on our roadmap. The basic passport does not require EPCIS; for traceability-heavy sectors we plan it as an extension.
Every field and file is classified to an access level, and the public passport shows only the public fields, so data meant for authorities stays out of the public view. Authenticated access for professionals and authorities (eIDAS) is in development; it also depends on the European Commission completing its implementing rules.
Yes, we offer a REST API for programmatic access, so passports connect directly to your ERP, PLM or production systems.
