NexusDPP logo NexusDPPDigital Product Passport
🇮🇹IT 🇬🇧EN
Home / DPP compliance
Compliance by design

Turn DPP requirements into operational controls.

NexusDPP connects rules, datasets, roles and evidence to a versioned workflow. The platform is configurable by product category and separates public information from data available to partners, verifiers and authorities.

Assess your scope Read the DPP guides
Applicable framework

One common system, different requirements by category.

Compliance combines DPP infrastructure with product law. A generic model is not enough: the project needs to identify the act defining data, granularity, access, retention and application date.

LayerWhat it definesProject impact
ESPR — Regulation (EU) 2024/1781Framework, DPP system, identifiers, access and product-specific actsOpen, interoperable architecture governed over time
Registry — Implementing Regulation (EU) 2026/1778Registration, access management, required data and Registry architectureConnector, API, status, errors and proof of registration
Standards — Decision (EU) 2026/1736Harmonised references for protocols, identifiers, carriers, storage, APIs and interoperabilityVerifiable technical choices and portability
Product legislationDataset, methods, granularity, authorised actors and application dateCategory templates, validations, evidence and workflows
Batteries RegulationPassport from 18 February 2027 for LMT, industrial batteries above 2 kWh and EV batteriesSector dataset, lifecycle and the first fixed DPP deadline
Controls applied to data

The rule becomes a workflow condition.

NexusDPP does not treat compliance as a final document. Requirements are connected to fields, sources, evidence, roles and states that prevent an unapproved version from being published.

Scope and templates

Category determines fields, units, conditional rules, evidence and dates. Template versions remain traceable.

Data ownership

Each item has a contributor, reviewer and person accountable for its use in the passport.

Validations

Format, range, unit, consistency, attachments and expiry are checked before approval.

Access control

Data is exposed to the public, partners, recyclers, verifiers or authorities according to role.

Versioning

Changes, author, date, reason, evidence and the link to the previous version remain available.

EU Registry

Only approved identifiers and metadata enter registration; status and electronic proof return to the product file.

Review of DPP data, documents and compliance controls
Role-based governance

Accountability is visible before publication.

The system distinguishes contribution, checking, approval, registration and maintenance. A supplier can contribute without seeing the full dossier; a verifier can record an outcome without changing source data.

  • Configurable RACI by product, facility and category.
  • Segregation of duties and multiple approvals where required.
  • Access and activity logs for reconstructing decisions.
  • Exceptions, deadlines and clarification requests.
Implementation

From requirement to registered passport.

A controlled route connects compliance, supply chain and technology.

01Classify

Product, role, legislation, thresholds and date.

02Model

Dataset, identifiers, evidence, access and owners.

03Configure

Portals, validations, approvals, APIs and carrier.

04Demonstrate

Approved version, logs, publication, registration and proof.

NexusDPP supports process organisation and execution. It does not replace legal classification, laboratories, notified bodies or the economic operator’s responsibilities.

Further reading

Read the rule, then build the process.

NexusDPP guides separate common infrastructure from product-dependent requirements.

EU DPP Registry

Identifiers, metadata, APIs and proof of registration.

Open the guide