What has changed and its scope
Regulation (EU) 2025/2509 introduces the DPP into toy safety legislation. Main application is scheduled for 1 August 2030; some provisions apply from 1 January 2026. Toys compliant with the previous directive and placed on the market before the deadline may remain available under the transitional regime. [1] [2]
Guide contents
What the passport represents
The DPP is associated with the model and includes persistent identification, access rules and retention. Annex VI includes an identifying image, operators, conformity information, CE marking and relevant technical references. Warnings and instructions should not be confused with the DPP's mandatory core; applicable communication duties still need to be met. [1]
Avoid attaching the right record to the wrong product
We propose starting with the relationship between the model, variants, materials and components. A supplier or component change should prompt the technical owner to assess its impact on records and published information.
The useful check is not simply whether a file exists. It is whether that document covers the revision being sold and who approved its use.
A governed technical file, not a folder of attachments
A project can organise documentation by model and assign ownership, revision, validity and purpose to each item. Complete evidence and information displayed in the passport should remain distinct.
A public record should be the result of an approved process, rather than an automatic copy of the whole technical file. The specific profile needs validation by the people responsible for toy safety and conformity.
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.
Build the identity
Connect the model, identifying image, variants and supply-chain operators.
Organise the technical file
Link documents and tests to the correct revisions, separating publishable information from evidence.
Manage changes
Define who reviews material, component and supplier changes.
Prepare publication
Test the data profile, permissions, access code and retention in the pilot project.
Configuration example / illustrative
From requirements to daily work
For a colour variant containing a different component, we propose an impact assessment before reusing the original model's documents and information. The platform does not automatically decide that the variant has the same conformity status.
What needs configuration and validation
NexusDpp provides a basis for managing information and evidence; it is not a conformity assessment body. The toy profile and integrations require specific configuration and testing. A passport does not replace testing, safety assessment or manufacturer responsibility.
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) 2025/2509
Articles 19-24, 57 and 59; Annex VI.
- EUR-Lex / Official toy safety summary
Scope, application and transition from the previous framework.
General information, not legal advice on an individual product. Requirements, exemptions, transitions and responsibilities depend on the specific case.