yellow3 / Digital Product Passport / Supplier Register

Supplier Register data

Digital Product Passport software comparison

Digital Product Passport providers grouped by what each publicly states it supports. Every name links to a profile where each finding has its source page and date. There is no score and no overall winner: the right provider depends on your products, the rule that applies to them and your requirements. For a requirement-by-requirement comparison against your own programme, the yellow3 Buyer Platform keeps provider statements and independent evidence separate.

114providers with findings
10capability areas
51capabilities
How this is built ↓Stated / shown, sourced, dated

Digital Product Passport role

What the provider says it is: a full passport platform, a resolver, a data layer or an assurance body.

Certification, assurance or verification body

18 providers with a published finding

Show all 18

Product data layer

1 provider with a published finding

Standards supported

The identification, data and exchange standards the provider says it supports. Six of the eight European Digital Product Passport standards are cited in the Official Journal; see the executive report.

Other

1 provider with a published finding

Data carrier technology

The physical carriers the provider says it works with.

UHF RFID

3 providers with a published finding

Digital watermark

1 provider with a published finding

Product identification

The identifier schemes the provider says it supports.

Decentralised identifier (DID)

2 providers with a published finding

Batch or lot identity

1 provider with a published finding

Other

1 provider with a published finding

Systems integration

The enterprise systems the provider says it connects to.

Traceability capability

The traceability the provider says it offers.

Lifecycle events such as repair, resale or recycling

1 provider with a published finding

Material tracking

1 provider with a published finding

Provenance records

1 provider with a published finding

Lifecycle and continuity

What happens to passport data over time, and if the provider changes or stops.

Audit trail

7 providers with a published finding

Data export and portability

5 providers with a published finding

Passport availability after insolvency or end of service

1 provider with a published finding

Registration

Registration with the EU Digital Product Passport Registry.

EU Digital Product Passport Registry

2 providers with a published finding

Digital Product Passport service provider

1 provider with a published finding

Registration on the customer's behalf

1 provider with a published finding

Implementation capability

Implementation help the provider says it offers.

Managed service

5 providers with a published finding

Implementation services

1 provider with a published finding

Onboarding support

1 provider with a published finding

Data collection approach

How the provider says it collects product data.

API ingestion

1 provider with a published finding

Automated ingestion from enterprise systems

1 provider with a published finding

Document extraction

1 provider with a published finding

Supplier data collection or questionnaires

1 provider with a published finding

How this page is built

Every entry comes from the yellow3 Digital Product Passport Supplier Register, researched independently from public sources. Each supplier's headquarters is recorded with its source and date. Each capability finding is either stated (the supplier says it on a public page) or shown (a buyer can inspect something concrete that demonstrates it), and links to that page.

There is no score and no ranking, and suppliers cannot pay to appear, rank higher or change a finding. Order is alphabetical. A supplier missing from a list has not published that statement in a form yellow3 has recorded; it does not mean the supplier lacks the capability. A statement that a provider supports a standard is not a conformity claim unless the provider says so, and is not a presumption of conformity unless the standard is cited in the Official Journal.

Register data last generated 28 Jul 2026. Found an error? Every profile has a correction route, and corrections are logged publicly on the Register method.