- The Commission DPP consultation explains that DPPs store and share product sustainability, durability, environmental, instruction, and conformity information, and that service-provider rules were under consultation.
"store and share relevant data"
A concrete workflow for turning a new ESPR delegated act or working-plan signal into scoped product impacts, extracted requirements, DPP changes, release gates, and evidence records.
It is relevant when legal, product compliance, sustainability, engineering, supply chain, and data teams need one cited intake record before product release or market placement.
Structured answer sets in this page tree.
Cited legal and guidance references.
Use this workflow to separate an ESPR planning signal from a binding product rule. Open a watch item for a working-plan entry, consultation, or draft. Open an implementation record when an adopted or amended Article 4 covers the product, then record scope, application timing, ecodesign requirements, DPP impacts, technical documentation, owners, and release evidence.
Create an intake record when an ESPR is adopted, amended, or repealed, or when the Commission publishes a working-plan item, consultation, draft, or implementation update. The source check must separate binding text from planning material: Article 4 delegated acts set ecodesign requirements, while the working plan identifies priorities and estimated timelines for future rulemaking.
The first owner should be product compliance. Legal validates the source status, sustainability maps the environmental product aspects, engineering identifies design and manufacturing impacts, supply chain checks supplier evidence needs, and data or IT owns DPP implementation impacts.
Do not start binding requirement mapping until the product-group boundary is explicit. Article 8 requires delegated acts to define the covered group or groups through product descriptions and commodity codes. Article 18 required the first working plan to prioritise listed groups, and the Commission adopted the 2025-2030 ESPR and Energy Labelling Working Plan in April 2025. Neither the statutory priority list nor a working-plan entry proves that a product is already covered by final requirements.
The scoping output should say whether each SKU, model, batch, component, intermediate product, private-label product, imported product, online listing, and repaired or remanufactured variant is in scope, out of scope, or awaiting source confirmation. Where the source is only a working-plan or consultation item, label the entry as a watch item rather than a release requirement.
For a binding , extract the operative text into three linked workstreams. The product workstream captures performance and information requirements. The documentation workstream captures tests, measurements, calculations, standards, technical documentation, module, markings, labels, and declaration-of-conformity impacts. The DPP workstream captures whether a DPP applies and, if so, the data, data carrier, access rights, creator or updater roles, availability period, and model, batch, or item level specified by the act.
Do not add DPP fields from generic templates. Annex III lists possible DPP data elements, but Article 9 and Annex III make the applicable the control point for what must be included for the product group.
As an internal control, block EU market placement, product-page publication, or DPP go-live when a binding duty applies and scope, requirement extraction, technical documentation, DPP data, or conformity evidence is incomplete. Treat supplier onboarding as a risk gate only where missing supplier evidence would prevent compliance. An internal approval cannot override a prohibition on placing or making a non-compliant product available.
Close the workflow with an evidence package that can answer a market-surveillance request without reconstructing the decision later. For products covered by a , Annex IV requires technical documentation that can assess conformity to that act, and manufacturers must keep the declaration of conformity with technical documentation available to competent national authorities for ten years unless the delegated act specifies a different period.
This ESPR intake workflow helps connect delegated-act source checks, product-group scope, requirement extraction, DPP impacts, technical documentation, and product-release gates.
"store and share relevant data"
"Product rules will then be developed"
"shall not place the product on the market"