What has changed and its scope
Regulation (EU) 2026/405 provides for a DPP for detergents and, in the case of surfactants, those intended for end users. General application starts on 23 September 2029, subject to exceptions and transitional rules. Products compliant with the previous framework and placed on the market before that date may remain available; an additional transitional regime runs to 23 September 2030. [1] [2]
Guide contents
A separate information model from digital labelling
The DPP is model-based, with a persistent identifier, controlled access and ten-year availability. Annex VI covers product and operator identity, compliance information and ingredients; certain industrial or institutional uses have specific provisions linked to safety data sheets. Digital labelling and the DPP are distinct requirements. [1]
Start by classifying the catalogue
Our proposed approach begins with a family-and-model matrix: product type, intended use, markets, operator role and placing-on-market date. A classification agreed by technical, commercial and regulatory teams avoids applying the same profile indiscriminately to every surfactant or package.
The matrix should also show which information comes from business systems, laboratories or suppliers. A missing value becomes an assigned information request, not a field populated with an assumption.
Separate public information from supporting records
In a NexusDpp project, we propose distinguishing publishable information, supporting technical records and restricted working notes. Permissions must be checked against the legislation: confidentiality cannot justify withholding information that must be accessible.
An internal formulation archive should not automatically become a public web page. The publication profile needs field-by-field design and approval before it is linked to the code on the product.
The NexusDpp approach
A cross-sector structure. A dedicated profile.
NexusDpp is designed to connect product identity, data, records, responsibilities and access. Preparation starts from this foundation: the proposed process translates the regulatory topic into a project configuration to validate against the customer's product and organisation. Platform architecture.
Identify the model
Connect master data, packaging presentations and variants to the appropriate product identity.
Collect the records
Associate label versions, ingredients, technical records and test evidence with their sources.
Approve the information
Configure roles, completeness checks and approval before publication.
Validate publication and continuity
Test identifiers, access rights, updates and backup against the sector profile.
Configuration example / illustrative
From requirements to daily work
For a reformulated detergent, the project can associate new records with the appropriate revision while preserving the previous reference. Whether to update the model or create a new one must be validated by the product owner; it cannot be inferred automatically from the trade name alone.
What needs configuration and validation
The detergent profile requires dedicated mapping and testing. This page does not certify that a customs connector, sector schema or backup service is already active for every customer. A DPP does not replace safety and conformity assessments.
Available features, integrations and acceptance tests must be specified in the agreed service scope. An information page is not a conformity certificate. Project status and transparency.
Primary sources and editorial method
Editorial review: 26 September 2026. Regulatory references are distinguished from NexusDpp organisational proposals. Always consult the applicable text and any subsequent updates.
- EUR-Lex / Regulation (EU) 2026/405
Articles 18, 21-25, 36-37 and Annex VI. Legislative text.
- EUR-Lex / Official detergents summary
Application timeline and transitional provisions; reviewed 11 June 2026.
General information, not legal advice on an individual product. Requirements, exemptions, transitions and responsibilities depend on the specific case.