Static vs Dynamic DPP Data: What Changes, What Doesn't, and Why It Matters

A DPP Is Not a Document You File Once

One of the most common assumptions brands make when approaching Digital Product Passport compliance is that the DPP is a one-time deliverable — something to prepare, attach to a product, and move on from. This assumption is incorrect, and acting on it will create significant compliance and operational problems down the line.

Under the EU's Ecodesign for Sustainable Products Regulation (ESPR), DPP data explicitly comes in two forms: static and dynamic. Static datapoints are fixed at the point of production. Dynamic datapoints must be updated throughout a product's lifecycle as its status, composition, or associated information changes.

Understanding the difference — and building systems capable of managing both — is foundational to a compliant and functional DPP.

Static Data: Fixed at Production

Static DPP datapoints are defined as fixed, unalterable information that remains consistent over time. These are the facts about a product that do not change once it leaves the factory floor.

For textile products, static datapoints typically include:

• Country of manufacture — where the garment was assembled (cut, make, trim)
• Country of origin of raw materials — where the primary fibres were sourced or grown
• Original fibre composition — the material breakdown at the point of production (e.g., 80% cotton, 20% polyester)
• Supplier and facility identifiers — the names and unique identifiers of the production facilities involved
• Intended season of sale — the commercial season for which the product was designed
• GTIN and unique product identifier — the serialized code assigned to this specific unit
• Certification documentation — certifications valid at the time of production (GOTS, OEKO-TEX, GRS, etc.)
• Chemical compliance records — REACH substance of concern declarations based on the original manufacturing inputs
• Care instructions — washing, drying, ironing, and storage guidance for the original product
• End-of-life guidance — disassembly and recycling instructions based on original composition

Static data is your DPP's foundation. It is the information you can — and should — begin collecting and structuring today, because the facts it captures are already knowable. Country of origin is not waiting for a Delegated Act to be defined. Fibre composition is not a methodology question. These are objective, direct datapoints that are within reach for any brand that has mapped its supply chain.

The static datapoints are defined and within reach already. Start collecting them now — waiting for final regulatory guidance on dynamic and footprint data is not a reason to delay building your static data foundation.

Dynamic Data: Updated Throughout the Lifecycle

Dynamic DPP datapoints are those that can and must be updated as a product's status or associated information changes after it leaves production. This is where the DPP becomes fundamentally different from any product document or label you have managed before.

Dynamic datapoints reflect the reality that a physical product does not stop having a story once it is sold. Under a circular economy model — which the DPP is specifically designed to enable — products are repaired, resold, remanufactured, and eventually recycled. Each of these events may change facts about the product that the DPP must accurately reflect.

What Makes a Datapoint Dynamic?

A datapoint is dynamic when any of the following can occur after production:

• Material composition changes — A repair that involves replacing a component with a different material (for example, adding a polyester patch to a cotton garment) changes the product's fibre composition. The DPP must be updated to reflect the new composition accurately.
• Ownership and location changes — As a product moves through resale channels, its custodian changes. Some DPP frameworks anticipate that resale events may be recorded to support circular economy tracking.
• Condition and serviceability updates — A product that has been professionally serviced or inspected may have its durability or condition status updated in its DPP.
• Certification renewals or changes — If certifications associated with a product are updated, suspended, or expanded in scope, this may need to be reflected.
• End-of-life status — When a product enters a recycling stream, this circular economy event is a dynamic update to the DPP that provides valuable data to the wider system.

A Concrete Example

Consider a wool jacket that carries a DPP at the point of sale. Its static data records 100% wool composition, a specific manufacturing facility, and a set of care instructions. Five years later, the consumer takes the jacket to a repair service, which replaces the worn lining with a polyester-blend fabric. The jacket is no longer 100% wool.

If the DPP is not updated, it now contains inaccurate information. A recycler who later processes this jacket and relies on the DPP data for fibre sorting will receive incorrect composition data — undermining the very circular economy efficiency that the DPP is designed to support.

This is not an edge case. It is the core use case for dynamic DPP data.

The DPP Is a Two-Way Data System

This is one of the least-discussed but most consequential aspects of DPP for brands to understand: the data flow is not one-directional.

Most brands instinctively think of DPP as a communication channel from them to consumers — a way of sharing product information at the point of purchase. This captures only part of the picture. A fully functioning DPP is a system in which multiple actors throughout the value chain can both read and contribute data.

Under ESPR, the stakeholders who interact with DPP data fall into distinct categories:

• Responsible Economic Operators (REOs) — the brand or retailer that places the product on market. Responsible for creating the DPP and maintaining its core data.
• Consumers — access publicly available product information. Read-only, limited to public data layer.
• Circular Economy Operators (CEOPs) — repairers, remanufacturers, recyclers, and sorters. Need both read access (to understand what a product is made of) and write access (to record what they have done to a product).
• Public authorities — regulators, customs, and market surveillance bodies. Need access to compliance documentation and declarations beyond what consumers see.

The implications for your system architecture are significant. Your DPP platform must not only allow your team to enter and update data — it must support controlled write access for third parties who interact with your products throughout their lifecycle.

Data Governance: Who Controls Updates?

If multiple parties can write data to a DPP, the question of data governance becomes critical. Who is authorized to update a DPP? How is the accuracy of updates verified? What happens if an unauthorized party enters incorrect data?

These questions are not yet fully resolved by ESPR guidance — the specific rules for data access authorization are expected to be detailed in the Delegated Acts due at the end of 2025. However, the broad framework is clear:

• Data access and update rights must be defined and controlled — not open to anyone
• The responsible economic operator (your brand) retains ultimate accountability for the accuracy of the DPP
• Secondary use of DPP data — using the data for purposes other than its intended function — requires explicit consent
• A backup copy of all DPP data must be maintained by a certified independent third-party provider

Practical questions that brands will need to address as Delegated Acts are finalized include: Should only approved, certified repair facilities be permitted to update DPP data, or can any repairer enter information? How is the accuracy of third-party updates verified? What audit trail is maintained for DPP changes over time?

These are not reasons to delay — they are design requirements to factor into your DPP system specification as you build it.

Public vs Restricted Data: A Third Dimension

Alongside the static/dynamic distinction, ESPR introduces a second axis of data classification: public versus restricted access.

Not all DPP data is visible to all stakeholders. The regulation specifies that:

• Public data — accessible to consumers and the general public via the data carrier scan. This includes care instructions, basic material composition, and sustainability claims.
• Restricted data — accessible only to authorized parties with defined access rights. This includes detailed chemical compliance records (relevant to regulators), supply chain facility identifiers (relevant to authorities and auditors), and potentially commercially sensitive supplier information.

The combination of static/dynamic and public/restricted creates a matrix of data types that your DPP system must manage:

	Public	Restricted
Static	Fibre composition, country of origin, care instructions	Facility identifiers, full chemical compliance documentation
Dynamic	Repair history (summary), circularity status	Detailed repair records, regulatory compliance updates

What This Means for Your Data Strategy

The static/dynamic distinction has concrete implications for how you approach DPP preparation:

Start with Static Data Now

Static data is your immediate priority. It is knowable today, it does not depend on regulatory methodology decisions, and it represents the bulk of the initial DPP data requirement. Use the DPP Data Checklist to map your current holdings against the required static categories and identify gaps.

Build Dynamic Data Capabilities into Your System from the Start

Do not build a DPP system that treats the passport as a static record. The architecture must support updates — which means version control, audit trails, access management, and API connectivity with third-party systems (repair platforms, recycler networks, resale platforms).

Plan for Circular Economy Operator Connectivity

As circular economy business models grow — and ESPR is explicitly designed to accelerate this — the volume of dynamic DPP updates will increase. Repair services, take-back schemes, and certified remanufacturers will all need structured access to the DPPs of products they handle. Building this connectivity infrastructure now, rather than retrofitting it later, is significantly more efficient.

Separate Data Collection from Data Publication

Your internal data collection process and your public DPP interface are two different things. Collect all data — static and dynamic, public and restricted — in a structured internal system. Publish only what is appropriate for each stakeholder type. This separation protects commercially sensitive information while ensuring compliance with ESPR's transparency requirements.

Frequently Asked Questions

How often does dynamic DPP data need to be updated?

There is no prescribed update frequency. Dynamic data must be updated when a relevant event occurs — a repair, a remanufacturing process, a material change, or a change in certification status. The key principle is that the DPP must remain accurate. An outdated DPP that no longer reflects a product's actual state is not compliant.

Can a consumer update DPP data?

Under current ESPR guidance, consumers have read access to public DPP data but are not envisioned as data contributors. The entities authorized to update DPP data are the responsible economic operator (brand/retailer) and circular economy operators (repairers, recyclers, remanufacturers) with defined access rights.

What happens to a DPP when a product is recycled?

The DPP data should remain accessible even after a product has been recycled — it provides valuable data to the circular economy system about material flows. The end-of-life event itself is a dynamic datapoint that should be recorded in the DPP. The archiving requirement under ESPR (Art. 9 (3a)) ensures a backup copy of all DPP data is maintained by a certified third-party provider.