How Do You Build an Evidence Trail for Every Sustainability Claim with a Digital Product Passport?

Executive Summary

A Digital Product Passport (DPP) can create an evidence trail for sustainability claims by connecting each claim to its underlying product data, source information, supporting evidence, calculations, and verification records. This creates a traceable link between a product’s sustainability attributes and the data used to substantiate them.

For manufacturers, this evidence trail makes sustainability claims easier to validate, monitor, and update across the product lifecycle. It also helps organizations trace changes in supplier data, product composition, certifications, or calculations back to the claims and products they affect.

Environmental claims are no longer something businesses can treat as isolated statements in product descriptions or marketing systems. The UK’s Competition and Markets Authority’s January 2026 guidance makes clear that environmental claims need to be accurate and supported by appropriate evidence, and that businesses may need to obtain information from other organizations across the supply chain to verify those claims.

At the same time, the UK government is exploring Digital Product Records as a potential way to improve how product and sustainability information moves across supply chains. Its 2026 call for evidence identifies transparency, traceability and improved access to product information as potential benefits, although the government has not yet determined a domestic DPR framework for Great Britain.

Take a claim such as “40% recycled material.”

The DPP may display one number. Behind that number, however, could sit supplier declarations, material composition data, certificates, component relationships, production records and calculation logic.

If one of those inputs changes, can you identify the affected products?

If a certificate expires, can you identify the claims that depend on it?

If a customer, auditor or regulator challenges the claim, can you trace it back to its source?

Publishing a sustainability claim is a data-output problem. Defending it is a data-lineage problem.

That is where DPP implementation becomes more than creating a digital record. It becomes a question of how product data, evidence and dependencies are structured and maintained.

Make the Claim Traceable 

Once a sustainability claim is treated as a derived data point rather than static product copy, its implementation requirements become clearer.

This does not mean turning the DPP into a document repository.

It means creating enough structured relationships around the claim to make its provenance and status discoverable.

That distinction matters at scale.

Imagine a manufacturer with 8,000 SKUs and 120 suppliers. A single supplier changes the composition of a component used across several product families.

The useful DPP system is not the one that can update a field quickly.

It is the one that can identify which claims depend on that component and which DPP records need to review. 

The DPP Is the Last Mile of the Evidence Trail

The DPP is often treated as the destination for product information.

In practice, it is closer to the last mile.

The information displayed through the passport may originate across an enterprise landscape that includes:

→ ERP systems

→ PLM and PIM platforms

→ MES and manufacturing systems

→ supplier portals

→ material databases

→ testing systems

→ certification repositories

→ lifecycle assessment tools

→ spreadsheets and structured supplier submissions

The challenge is therefore not simply connecting these systems to a DPP platform.

It is deciding which system is authoritative for each data element and how that information is validated before it becomes a published product claim. 

Automation: Reduce the Work, Not the Accountability

Evidence management becomes difficult when teams have to inspect documents, check dates and update product records manually.

Automation can handle many of the repetitive controls.

Instead of teams repeatedly checking every product, they can focus on exceptions generated by the system.

A practical workflow might be:

Where AI Can Strengthen the Evidence Workflow

AI can make evidence onboarding more scalable, particularly where suppliers continue to submit information through semi-structured documents.

An AI-assisted workflow could extract fields from supplier declarations or certificates, classify documents and compare extracted values against existing product data.

For example, it could flag:

→ Certificate expiry date is missing.

→ Supplier declaration conflicts with existing material data.

→ Required evidence was not found.

→ Recycled-content value differs from the previous submission.

→ Document appears to reference a different component.

But AI should remain an assistive layer.

It can accelerate extraction, classification, comparison and exception handling. It should not become the authoritative source of the sustainability claim.

The original evidence and governed enterprise data remain the source of truth.

Start With the Claim, Not the Document

A practical way to design the evidence model is to work backwards from the sustainability claims the DPP needs to support.

Take:

“40% recycled material.”

First define the claim and metric.

This approach gives the DPP implementation a concrete starting point.

Rather than asking:

“What documents should we put into the DPP?”

the better question is:

“What claims must the DPP support, and what information is required to substantiate them?” 

Design the Product Data Model for Change

The evidence model becomes especially important when products have complex bills of materials or frequent configuration changes.

A manufacturer may have one material used across:

→ Multiple components

→ Several product families

→ Regional variants

→ Different generations of a product

A change to that material should not require manual investigation across every affected DPP record.

Different Products, Different Evidence Challenges 

The implementation pattern will vary by manufacturing sector.

A consumer electronics manufacturer may need to connect material composition, component suppliers, battery information and product-level sustainability data.

An automotive manufacturer may need to manage evidence across complex bills of materials and multiple supplier tiers.

A textile manufacturer may need to connect fiber composition, recycled content and certification information across large numbers of product variants.

A furniture manufacturer may need to trace timber, coatings, materials and component-level information.

The technology challenge is different in each case.

But the underlying principle is consistent:

The claim appears at product level, while the evidence often originates somewhere else.

The DPP implementation needs to connect those two layers without creating unnecessary manual work.

The Real Test of a DPP Isn’t “Can It Publish the Claim?”

A DPP that displays “40% recycled material” has completed the visible part of the job.

The harder questions are underneath it.

→ Where did the 40% come from?

→ What evidence supports it?

→ How was it calculated?

→ Which products depend on the underlying data?

→ What happens when the evidence expires?

→ What happens when the supplier changes the material?

→ How quickly can affected DPP records be identified?

→ And can the business demonstrate the supporting information without reconstructing the evidence manually?

These are not simply questions about the passport interface.

They are questions about product data, integrations, governance and implementation.

For manufacturers moving toward enterprise-scale Digital Product Passport adoption, that distinction matters.

The long-term value of a DPP will not come from creating another place to publish product information.

It will come from creating a product-data environment where sustainability claims can be substantiated, changes can be traced and affected products can be identified without starting the investigation from scratch.

That is what turns a Digital Product Passport from a digital record into a traceable product-data system.