- 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.
Use it when legal, product compliance, sustainability, engineering, supply chain, and data teams need one source-linked intake record before product release or market placement.
Structured answer sets in this page tree.
Cited legal and guidance references.
Under ESPR, product rules are set through delegated acts adopted under Article 4. This workflow starts when a team sees a new or changed ESPR delegated act, working-plan item, consultation, or Commission implementation update, and ends only when product scope, ecodesign requirements, DPP impacts, technical documentation, owners, and release evidence are recorded.
Create an intake record when an ESPR delegated act is adopted, amended, repealed, consulted on, or connected to a new working-plan product group. The source check must separate binding text from planning or consultation material: Article 4 delegated acts set ecodesign requirements, while the working plan identifies product groups 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 requirement mapping until the product-group boundary is explicit. Article 8 says delegated acts must define the covered product group or groups, including commodity codes and product descriptions. Article 18 also names priority groups for the first working plan, including iron and steel, aluminium, textiles, furniture including mattresses, tyres, detergents, paints, lubricants, chemicals, certain energy-related products, ICT products, and other electronics.
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 delegated act, 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, conformity assessment module, markings, labels, and declaration-of-conformity impacts. The DPP workstream captures whether a DPP is required 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 delegated act the control point for what must be included for the product group.
The release gate should block EU market placement, product-page publication, supplier onboarding, or DPP go-live when scope, requirement extraction, technical documentation, DPP data, or conformity evidence is incomplete. ESPR obligations for importers and distributors also depend on delegated-act coverage, so commercial and marketplace teams need a clear yes/no gate before launch.
Close the workflow with an evidence package that can answer a market-surveillance request without reconstructing the decision later. For products covered by a delegated act, 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.
Use this ESPR intake workflow to 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"