Data audit
We check which DPP-relevant information already exists and where it sits: ERP, PIM, technical data sheets, EPDs, LCAs, supplier data or internal product databases. We assess which data is usable as it stands and which has to be added.
CORE SERVICE DIGITAL PRODUCT PASSPORT
The Digital Product Passport structures your LCA and supply chain data
We build DPP data models for construction products that bring EPD life cycle indicators, ERP master data and supply chain information together in one consistent schema. Implementation is possible as the EU CPR and ESPR take effect from 2027.
Module · Live LCA data
Module · Live EPD modules
Module · Live Materialcomposition
Module · Draft Supply chain tracing
Module · Draft Recycling data
Module · Draft Repair index
Module · Draft Substances / SCIP
EU 2027
What the Digital Product Passport is, and why it is worth preparing now
A construction product is not only made of material. It is also made of information. Which raw materials went into it? Which environmental figures exist? How can the product later be separated, reused or recycled? What evidence is already available? And which data does a customer, planner or public sector client need to be able to assess the product at all?
This is where the Digital Product Passport, or DPP, comes in. It is a structured digital collection of data about a product. Think of it as a digital identity document for the product: all the relevant information gathered in one place, clearly ordered and presented so that it can be read by people and processed by software systems alike.
That includes information on material composition, environmental indicators from LCA or EPD, details on recycling and deconstruction, technical product data, certificates and selected supply chain information. The DPP does not make this data better on its own, but it does make it findable, comparable and usable elsewhere.
For construction products the Digital Product Passport is becoming more relevant through new European rules. The EU Construction Products Regulation and the Ecodesign Regulation matter most here. Both aim to make product information more transparent and usable digitally. From 2027 the roll-out becomes concrete step by step. At the same time many lead planners, public sector clients, large processors and customers subject to the CSRD are already asking for more detailed product data today.
The pressure often comes not directly from an authority but along the supply chain. A large client needs data for a project. The lead planner asks the manufacturer. The manufacturer asks its own suppliers. The requirements travel downwards step by step until smaller and mid-sized manufacturers have to deliver too.
Anyone who only sets up the Digital Product Passport once it becomes mandatory will be working under time pressure and facing considerable cost. Data sources have to be found, responsibilities clarified, ERP systems connected, missing environmental figures added and product data structured. All at once. Starting the preparation earlier lets you build that process under control.
We therefore do not treat the DPP as an isolated IT project. A useful Digital Product Passport starts with one question: which data already exists, and which still has to be built up so it holds? Often the important information is already there, in EPDs, LCAs, technical data sheets, ERP systems, bills of materials, formulations or supplier documents. What matters is assigning and structuring that data cleanly, and not maintaining it twice.
That is exactly where ecoverity comes in. We map existing EPD data points, LCA results and ERP master data onto a DPP structure. In a DPP project we show concretely which data is already usable, what is missing, which interfaces will be needed and what a Digital Product Passport looks like for your product range.
A coming obligation then turns into an orderly start on digital, reviewable and reusable product information rather than a rushed data project. We create clarity before the requirements become binding, and lay the groundwork together so that later DPPs take less effort and stay more consistent.
Your DPP project in 5 steps
The route to an integrated Digital Product Passport
-
-
Mapping
We map the future mandatory DPP fields onto your existing data sources. That builds the bridge between sustainability data, product master data and technical information. The aim is to link existing data cleanly rather than maintain it twice.
-
Building the data model
We develop a first DPP data model for your product. It defines which information the passport should hold, which fields are mandatory, optional or can be added later, and how the data can be structured technically. The model stays compatible with formats such as JSON or XML and with the EU requirements still to come.
-
Implementation
We put the DPP process into practice on the chosen product. We populate the data model with product data, test how usable it is day to day and show how the passport can later be made available to customers, planners or internal teams, for example through a QR code or a system export.
-
ERP connection & data maintenance
We define how the DPP can be maintained over time. We establish which data can be taken automatically from ERP or PIM systems, which information has to be added manually and how updates run when the product changes.
- 01
Data audit
We check which DPP-relevant information already exists and where it sits: ERP, PIM, technical data sheets, EPDs, LCAs, supplier data or internal product databases. We assess which data is usable as it stands and which has to be added.
DeliverableData overview, data sources, priority list for missing data
- 02
Mapping
We map the future mandatory DPP fields onto your existing data sources. That builds the bridge between sustainability data, product master data and technical information. The aim is to link existing data cleanly rather than maintain it twice.
DeliverableMapping table, field logic, data source assignment
- 03
Building the data model
We develop a first DPP data model for your product. It defines which information the passport should hold, which fields are mandatory, optional or can be added later, and how the data can be structured technically. The model stays compatible with formats such as JSON or XML and with the EU requirements still to come.
DeliverableDraft DPP schema, data structure, field definitions
- 04
Implementation
We put the DPP process into practice on the chosen product. We populate the data model with product data, test how usable it is day to day and show how the passport can later be made available to customers, planners or internal teams, for example through a QR code or a system export.
DeliverableDigital Product Passport, QR code and access concept
- 05
ERP connection & data maintenance
We define how the DPP can be maintained over time. We establish which data can be taken automatically from ERP or PIM systems, which information has to be added manually and how updates run when the product changes.
DeliverableDPP pipeline, update process, interface concept
What you actually receive
ecoverity's service promise
- JSON · XML · COMPLETE
DPP data model
A complete DPP schema in JSON and XML, ready to connect to the EU CPR and ESPR requirements as soon as the implementing acts are final.
- XLSX · INTERNAL
ERP mapping sheet
A mapping table linking DPP fields ↔ ERP fields ↔ EPD data points, the bridge between master data and sustainability data.
- JSON-LD · ILCD+EPD-XML · QR CODE WITH GS1 DIGITAL LINK
Digital Product Passport
A DPP for your product, including QR code and data flow diagram.
- PDF · XLSX · INTERNAL
Data audit report
An overview of all DPP-relevant data from ERP, PIM, EPDs, LCAs and supplier documents, including data source assignment and a priority list.
What the DPP makes possible
Services that build on the DPP
A structured DPP brings LCA and EPD data together, ready to feed a well-founded CO₂ reduction strategy.
STEP 01 Methodology
STEP 02 Documentation
STEP 03 Strategy
Common questions about DPP
When does the DPP become relevant for construction products?
The Digital Product Passport is becoming steadily more relevant through the new EU Construction Products Regulation. There is not yet a blanket obligation for all construction products from a fixed date. What matters is when the technical rules, data requirements and implementing acts for each product group are in place. What is clear is that the DPP will be introduced for construction products step by step, and that it will make product information available digitally, in a structured, machine-readable form. Manufacturers who start early avoid high costs and long waiting times.
Can we pilot the DPP before the implementing acts are final?
Yes, and that is exactly the sensible move. Even though not every mandatory field is settled, the building blocks are already foreseeable: product master data, material information, environmental indicators, recycling notes, technical evidence and supply chain information. A DPP project therefore creates clarity today. Which data do you already hold? What is missing? Which information comes from ERP, PIM, EPD or LCA? And what would a data model look like that can be adapted to the final requirements later?
What is the interface between our EPD and the DPP?
An EPD already supplies a great deal of environmental information that becomes relevant for the DPP, for example life cycle indicators, environmental impacts, material information and details of the life cycle stages covered. The DPP does not replace the EPD. It makes specific information from it usable digitally. Our mapping assigns existing EPD data points to the DPP data model, so environmental information does not have to be maintained twice.
How much effort does this take on the ERP or PIM side?
That depends on how well your product master data is maintained today. In many cases a lean data structure with selected fields from ERP, PIM, technical data sheets and existing EPD or LCA data is enough for a pilot. It takes more work when material compositions, variants, supplier data or recycling information are not yet kept systematically. That is exactly what we establish together in the data audit: which data exists, what is missing and which interface is realistic for a later roll-out.
What happens to confidential supply chain and formulation data?
Not all information in the DPP is public. The Digital Product Passport can be designed with different visibility levels: public data for customers and planners, access-restricted data for testing bodies or authorities, and internal data that stays with the manufacturer. We therefore model separate data layers from the outset. The aim is to supply the information regulation requires without exposing sensitive formulations and supplier relationships.
What makes a DPP pilot with ecoverity different from a pure IT solution?
We do not treat the DPP as a software or QR code project. The real work comes before that: product data has to be found, checked, structured and assigned correctly in technical terms. ecoverity combines sustainability methodology with data structuring. We map EPD, LCA and product master data onto a DPP-ready data model and establish which information can later be taken automatically from ERP or PIM. The result is not an isolated data container but a data logic that connects to your later products.
Do we need all the data in place before starting the DPP?
No. A DPP project with ecoverity exists precisely to make data gaps visible. Often a lot of information is already there but scattered across ERP systems, technical data sheets, EPDs, LCAs, supplier documents or internal product lists. We bring these sources into one structure and show which data is usable straight away, which has to be added and which information only becomes relevant once the final DPP requirements for your product group are set.
Act before the DPP becomes mandatory and expensive to produce.
In one conversation we establish which product data you already hold, where the gaps are and what project scope is realistic.