The product · Digital Product Passport

The passport as a fact.
Ready today, while they are asking you for it.

The market is filling up with digital passports. There is only one line that divides them: behind the QR code there can be a page to be believed, or a signed fact that anyone — customer, authority, machine — checks on their own. TRUST-DAP builds the second kind: it is the direction European legislation points to — interoperability, machine readability, a common registry.

The picture, today

The passport is already working its way down the supply chain.

The digital passport is already being asked for in supply contracts, ahead of the legal deadlines: lead firms and buyers are asking suppliers for the data now. The European ecodesign regulation (ESPR) introduces it for progressively wider categories, with a European registry already governed by the implementing acts. Whoever answers today is prepared; whoever answers first turns up with a calling card the others are still waiting for.

Who is asking you

Your customer, ahead of the law

The formal obligation has its dates; the commercial request has already arrived. Automotive buyers, supply chain lead firms, large contractors: the passport is already in supply tender specifications.

What it contains

The verifiable history of the batch

Identifiers, composition, processing, conformity, provenance: signed data anyone can check, ready for the European registry and for your customers' systems.

How you get there · ②

From the bridge, automatically

The facts your production already generates become the passport: the DPP format is one of the languages of the translation engine. You attest once, the passport assembles itself.

The line that divides the market

A passport you look at is a document.
One you verify is a fact.

The five questions to ask anyone offering you a digital passport

  1. Who signed the data?The platform that displays it, or whoever actually generated it — the operator, the machine, the supplier?
  2. Can a machine read it?Behind the QR code, is there a page to look at, or structured data (JSON-LD, W3C and GS1 standards) that your customers' systems process on their own?
  3. Can it be verified independently?Does the platform check itself, or can anyone, with standard tools, check it for themselves?
  4. What happens if you change supplier?Do the data and the identities follow you, or do they stay where they were born?
  5. Does it speak tomorrow's languages?European registry, Catena-X, AAS: projections ready to go, or a single format — the vendor's own?
Ask them of everyone. Us included — us above all: here, every answer proves itself.
The languages we speak

One passport, every counterpart in their own language.

Digital Product PassportCompliant with ESPR

The native format towards the European framework: structure, identifiers and registry according to the implementing acts.

Catena-XDesigned for

SerialPart and Batch for the automotive supply chain: the format the German buyer expects to receive.

GS1Designed for

Digital Link and global identifiers: the language of distribution and retail, from the QR code to the database.

AASDesigned for

Asset Administration Shell (IEC 63278): the digital datasheet of the machine and the product for Industry 4.0.

UN/CEFACTAligned with

The vocabulary of international trade: traceability that crosses customs together with the goods.

GAIA-XCompliant with the Trust Framework

Identity and credentials following the rules of the European data infrastructure: the participant's passport, not just the product's.

Ready for supply chain exchange

The passport is born ready for the industrial web of data: signed, with selective views for each counterpart, with verifiable identities. Here, trust proves itself.

How the bridge that generates it works →
Is your supply chain asking you for it? Let's talk →