See how a DPP can be presented.
The public example shows identity, data, evidence, access and lifecycle without claiming real product data or certified compliance.
Open the public DPP demo
NexusDPP Control Center
The platform that governs DPP data, decisions and identity.
NexusDPP separates collection, checks, approvals, identity, publication, registration and lifecycle. Each module can integrate with existing business processes.
Supplier portalConfigurable workflowsQR / NFCRegistry adapter
Architecture and controls with a declared status.
The Trust Center separates defined components, MVP implementation work and the enterprise roadmap.
Open the Trust CenterData-ingestion configuration
Three ways to bring data and documents into NexusDPP.
Each company can select one primary approach or combine all three within the same project. Configuration may vary by product category, data family, supplier or process stage.
Mode 01
Guided manual entry
Users enter information directly into the DPP model configured for the product. The platform displays only the fields relevant to the role, sector and current workflow status.
- Mandatory fields, units of measure and controlled values.
- Draft saving and progressive completion.
- Evidence linked to the data: certificates, datasheets, declarations and images.
- Immediate checks for omissions, formats and consistency.
- Role-based review, correction requests and approval.
Best suited to: pilot projects, limited portfolios, strategic data and information requiring close operator control.
Mode 02
AI-assisted acquisition
The company uploads documents it already holds. AI analyses the content and prepares completion proposals, reducing the work required to read and transcribe large volumes of information manually.
- Upload of PDFs, technical sheets, certificates, declarations and structured files.
- Identification of candidate data and linkage to the source document.
- Mapping of information to the relevant DPP fields.
- Flags for missing data, inconsistencies and documents requiring renewal.
- Human confirmation before data enters the official DPP.
Best suited to: existing document archives, rapid onboarding of many items and reduction of repetitive data-entry activities.
Mode 03
Supplier and item document database
NexusDPP can include a lightweight repository linking suppliers, items, components and documents. Recurring information is organised once and reused across authorised DPPs.
- Master data for suppliers, items, components, models and product families.
- Relationships among supplier, purchased item and finished product.
- Repository for certificates, datasheets, declarations and revisions.
- Expiry dates, document owner and validity status.
- Controlled data reuse and coordinated updates across linked DPPs.
Best suited to: companies with recurring suppliers, large item catalogues and documentation shared by multiple products or projects.
A hybrid configuration
The three modes operate together in one process.
The ingestion method can be defined for each field or data group. A single DPP can therefore combine manually entered data, information extracted from documents and content already held in the company database.
1. Initial mapping
During onboarding, products, suppliers, available documents, internal owners and information sources are identified. NexusDPP defines which data will be entered manually, which can be extracted with AI and which will come from the document database.
2. Rules by data family
Master data may come from the database, technical data from AI-analysed documents, and commercial or confidential information from manual entry. The rule may vary by sector, model, batch, component or individual unit.
3. Roles and permissions
Each user sees only the assigned fields, documents and actions. Suppliers can complete their part, importers or manufacturers can review it, and verifiers access only the authorised evidence.
4. Data control
Acquired data remains a draft or proposal until validated. The platform records the source, author, date, version, corrections and approval, preserving a readable path to publication.
5. Product linkage
Every item of information is associated with the correct object: company, supplier, item, component, model, batch or unit. This prevents a generic document from being used for a different product.
6. Reuse and updating
Approved data can feed multiple DPPs according to defined rules. When a document is replaced or expires, NexusDPP identifies the affected products, opens the update workflow and preserves the history of previous versions.
The outcome
A configurable process that reduces duplication, preserves human control and provides structured data, linked documents and verifiable responsibilities throughout the DPP lifecycle.
ManualMaximum control over sensitive or product-specific data.
AI assistedFaster analysis of existing documentation.
Lightweight databaseOrganised reuse of recurring data and documents.
Core modules
From onboarding to the public view.
One environment for organisations, products, documents, roles, statuses and integrations, with a clear separation between public data, restricted data and verifiable evidence.
Portal & IAM
Organisations, users, roles, delegations and access for importers, manufacturers, non-EU suppliers and verifiers.
Workflow Engine
Data requests, deadlines, revisions, approvals, signatures, statuses and blocking rules managed in the backend.
DPP Core
Product identity, versions, datasets, attachments and relationships among components, batches and individual units.
Compliance Engine
Dynamic category templates, mandatory fields, validations, evidence and consistency checks.
Trust Layer
Audit trail, digital fingerprints, timestamps, notarisation and third-party verification opinions.
Trade Compliance & Sanctions
Counterparty screening, final destination, end users, logistics documents and an evidence dossier.
Explore the modulePublic Access Layer
QR, NFC, GS1 Digital Link and differentiated views for consumers, partners, authorities and service teams.
End-to-end workflow
Every step leaves a clear and readable responsibility.
Configure the DPP model
Product, sector, economic operator, dataset and access levels.
Collect data and evidence
Internal completion or secure invitation to suppliers and partners.
Validate and approve
Automated checks, human review and optional independent verification.
Generate identity and data carrier
Unique code, QR/NFC and linkage to the physical carrier.
Activate and update
Triggers from ERP, orders, logistics or market events, followed by maintenance and end-of-life updates.
ERP / PLMSuppliersDocumentsMES / WMS
NexusDPPDPP orchestration
IngestionValidationWorkflowIdentityTrustLifecycle
Integrations
NexusDPP connects business systems in one DPP flow.
Data can be imported or synchronised through structured files, connectors and dedicated integrations. Events can activate or update the passport automatically and in a coordinated way.
ERP / management system
Item master data, orders, suppliers, invoices, batches and commercial status.
MES / WMS / logistics
Production, serialisation, packing, shipping, warehouse receipt and delivery-event data.
BMS and IoT
For batteries: state of health, technical events and dynamic data, according to availability and access rules.
Printing and encoding
Data-carrier generation and integration with labelling, QR and NFC systems.
Registry adapter
Connector for the live EU DPP Registry, including identifiers, metadata, status, errors and electronic proof of registration.