Imagine a customer, service technician, distributor, or regulatory authority scanning a code on a product and gaining access to organized information about its origin, composition, specifications, repairs, or recycling options. There is no need to search for documentation on the manufacturer’s website or request another file. The information is available in a digital passport assigned to a specific product.
This is the idea behind the Digital Product Passport (DPP). The European Union is developing this system as part of its efforts to promote more sustainable products, supply chain transparency, and a circular economy.
For many businesses, however, this will mean more than a new way of presenting information. DPP entails the need to organize product data, define responsibility for keeping it up to date, and ensure cooperation between IT systems.
That is why it is worth taking an interest in this topic now, even if the specific obligations for a company’s products have not yet come into force.
What is the Digital Product Passport?
The Digital Product Passport is a digital set of information about a product, its components, or materials. It is intended to provide access to data relevant to use, durability, repair, reuse, recycling, and compliance with applicable requirements.
The information covered will not be identical for all products. It may include, among other things:
-
the manufacturer and product identification;
-
origin and material composition;
-
information about substances relevant to safety and the environment;
-
technical and environmental specifications;
-
instructions for use, maintenance, and repair;
-
information on durability, reuse, and recycling;
-
data on the components and materials used in production.
The information required is defined by the regulations applicable to each specific product group. You should therefore not assume that every passport will include all the data listed above.
The passport is intended to be accessible via a digital data carrier linked to the product. This could be a QR code, for example, but the final requirements for the data carrier and its placement will depend on the regulations for the relevant product category.
The most important change is that product information must be organized, readable by different systems, and available to authorized recipients throughout the required period.
Will the Digital Product Passport be mandatory for all products?
No. This is one of the most important points to emphasize clearly.
The basis for the EU DPP system is the ESPR, or the Ecodesign for Sustainable Products Regulation (EU) 2024/1781. It establishes the framework for introducing digital passports, but detailed requirements are being defined gradually, separately for individual product groups. Some sectors are also subject to separate regulations.
Batteries are the first specific area. From 18 February 2027, passports will be required for certain categories: electric vehicle batteries, light means of transport batteries, and industrial batteries with a capacity exceeding 2 kWh.
Further product groups are to become subject to the requirements in the coming years. The European Commission’s plans include iron and steel, textiles, tyres, aluminium, furniture, and mattresses, among others. However, the schedule for publishing sector-specific regulations is indicative. The stated year for adopting an act does not mean that all products in a given category must already have a passport from that year onward.
For delegated acts adopted under the ESPR, businesses are to receive a transition period of at least 18 months before the new requirements begin to apply, in accordance with the rules set out in the regulation.
In practice, this means that companies should monitor the regulations covering the specific products they manufacture, import, or place on the EU market. General information that DPP is coming is not enough.
DPP is not just an ordinary QR code on packaging
At first glance, a digital passport may look like a familiar QR code linking to a product page. The difference, however, is fundamental.
An ordinary QR code can link to any webpage, catalogue, or PDF file. It does not guarantee that the information will be complete, up to date, properly organized, or readable by other systems.
DPP is intended to operate on the basis of defined identifiers, data structures, access rules, and interoperability standards. This means that preparing one should not be limited to creating a website with a product description.
The architecture of the entire solution is also important. Information may be stored by the responsible economic operator or an authorized service provider. The EU DPP registry is not simply a central repository for all product data. It primarily stores unique identifiers and required registration information, making it possible to link a product to the relevant passport.
This is an important distinction for companies planning an implementation. They need to design both how data will be stored and updated and how it will be shared.
Why is DPP becoming a challenge for IT systems?
The information needed to create a digital passport is rarely in one place.
Product data may be spread across an ERP system, product database, warehouse management system, technical documentation, production tools, B2B platform, and online store. Some information may come from component or material suppliers, while other data is only generated during the product’s use.
If a company wants to prepare a reliable passport, it must be able to collect this data, verify it, link it to the right product, and share it in the appropriate format.
This is where a well-designed IT environment comes into play.
1. Organizing product data
The first step is to determine what product information the company already has, where it is stored, and who is responsible for its accuracy.
Duplicates, gaps, naming differences, and inconsistencies between systems need to be identified. For example, the same component may appear in several databases under different codes, making it difficult to link it unambiguously to the finished product.
2. Unambiguous product identification
The system must distinguish between the appropriate levels of identification. Depending on the requirements, a passport may apply to a model, a production batch, or an individual item.
This is not a minor detail. Information shared across an entire product range is managed differently from data that changes over the course of a specific device’s use.
3. System integration
A DPP may require information to be collected from several sources. This makes integrations between ERP and PIM systems, production and warehouse systems, sales platforms, and solutions provided by external partners essential.
The goal is not to replace all systems with a single one. It is to ensure controlled data flows and reduce manual data entry.
4. Managing access to information
Not all data has to be public. Some information may be intended for consumers, while other information may be intended for service providers, recycling operators, supervisory authorities, or other authorized participants in the supply chain.
The system should therefore enable permissions to be managed and the relevant data to be shared with the appropriate recipients.
5. Data currency and history
A passport cannot be merely a static document generated on the date of sale. Depending on the type of product and legal requirements, information may need to be updated, for example when a product’s status changes, after a repair or reuse, or when the responsible operator changes.
This means that procedures for updates, version control, a change history, and clear rules on who can modify specific information are needed.
Who is responsible for the Digital Product Passport?
This question has significant organizational and technical implications.
As a rule, responsibility for meeting DPP requirements rests with the relevant economic operator designated in the regulations for the product group in question. Depending on the regulations, this may be the manufacturer, importer, or another entity placing the product on the market.
A company may outsource the preparation, storage, or technical management of a passport to an external provider. However, this does not automatically transfer to that provider legal responsibility for the product’s compliance and the required information.
For batteries, the European Commission clearly distinguishes the economic operator’s responsibility from the possibility of authorizing another entity to carry out passport-related activities. Ultimate responsibility remains with the entity designated in the regulations.
That is why it is worth establishing the following at the solution design stage:
-
who provides each data item;
-
who verifies it;
-
who approves its publication;
-
who is responsible for updates;
-
who manages access to information;
-
how responsibilities are transferred if the provider or operator changes.
Without this division of responsibilities, even a well-designed system can quickly become difficult to maintain.
How to prepare your company for the Digital Product Passport: a practical checklist
You do not have to wait for all the detailed regulations before starting preparations. There are several steps you can take now to reduce future costs and the risk of a chaotic implementation.
Step 1. Check whether your products will be subject to the requirements
Identify the product groups your company manufactures, imports, or places on the EU market. Then check the relevant regulations and timelines. Do not base your decisions solely on general information about the DPP.
Step 2. Map your product data
Determine what information is already available, which systems store it, and who is responsible for it. It is also worth including data provided by suppliers and subcontractors.
Step 3. Assess data quality and completeness
Check whether the data is consistent, up to date, and can be unambiguously linked to a product, batch, or individual item. This is a good time to standardize identifiers and naming conventions.
Step 4. Review your current systems and integrations
Determine whether your existing solutions can retrieve, update, and share the required data. Identify where information is transferred manually or stored in separate files.
Step 5. Plan the solution architecture
Decide whether it is enough to extend your existing systems, build an additional module, or create a dedicated platform. The solution should be ready for future requirements and should not make your company dependent on a single provider.
Step 6. Establish maintenance and update procedures
A passport must not only be created; its information must also be maintained in the appropriate form. Plan data ownership, change procedures, backups, and continuity of access.
Does your company need a new application for this?
Not necessarily. In some companies, it may be enough to extend existing systems appropriately and prepare integrations. Others may need an additional module for managing product data or a separate platform for digital passports.
The decision should be based on an analysis of your current infrastructure, the number of products, data sources, access requirements, and the scale of the planned solution.
It is also worth remembering that the cost of such a project does not end with building the application. You should also account for integrations, data migration, testing, maintenance, updates, and system development as regulations change.
We wrote more about what to consider when planning a budget for custom solutions in this article: How much does a custom application really cost? More than just the implementation price.
It is also worth considering the DPP in the broader context of the entire application landscape used by your company. If product information is scattered across many tools, preparing a passport may reveal problems that were not previously apparent. Read more about this in: How many systems does your company really need? SaaS sprawl: the chaos of tools you pay for.
The DPP is not just an obligation. It is also an opportunity to organize product information
The Digital Product Passport is part of a broader change in how information is managed across the supply chain. Data that may previously have been scattered across documents, spreadsheets, production systems, and product databases will need to be available in a more structured and interoperable form.
For companies, this means new tasks, but also an opportunity to improve product traceability, streamline service, improve information flows with partners, and manage product lifecycles more effectively.
The DPP should not be treated merely as another field to fill in in the documentation. It is an issue that affects system architecture, data quality, integrations, and business processes.
At Web24, we design custom applications, platforms, and integrations that help companies organize their data and develop their technology environments in line with their actual needs. Preparing for digital product passports may be one reason to take a closer look at how your company’s systems currently operate.
Because in a world of digital passports, the advantage will go not only to companies that have data. It will go to those that can manage it efficiently.



