Skip to content

DPP & Data Hub

The source of truth for the Digital Product Passport. Agnostic intake, regulatory validation and omnichannel distribution.

ESPRNative schema
Data model

One source. Three layers of truth.

Data from any source converges into a canonical ESPR model. From there it's ready for DPP, CSRD and any integration.

LAYER 1: DATA INGESTION
SchemaCANONICAL MODEL
ESPR CORE
DPP READY

Eco-Jacket v2

Verified by TraceWeave

Data completeness0/100
  • INTAKE

    Many sources, one format

    ERP/PLMExcel/CSVAPIsSuppliers
  • CORE

    Canonical ESPR schema

    35+ fieldsValidationImpactTraceability
  • DISTRIBUTION

    Certified outputs

    DPP QRCSRD ExportAlertsAPIs
Capabilities

Everything needed to manage DPP data

35+ native fields

Canonical ESPR schema

A data model designed from scratch for ESPR. GS1 Digital Link compatible.

dpp_schema.ts
interface DPP_Product {
1id: UUID;// GS1 Digital Link Key
2composition: Material[];// Art 9.1: Fibres
3pef_score?: ImpactMetric;// PEFCR Compliant
4circularity: Block<CyclicEvent>;
}
Native integration

ERP/PLM connectors

Shopify, Microsoft Dynamics, SAP Business One, Holded, Sage, Business Central. Also via email and Google Drive with AI. Without stopping operations.

ShopifynativeMS DynamicsnativeSAP Business OnenativeHolded · SagenativeExcel · CSVwizardEmail · DriveAI
Powered by TracePulse

Import wizard

Upload Excel/CSV. AI maps columns and detects errors automatically.

import_ss25.csvmapping
  • ref_idproduct_gtin98%
  • material_1composition[0]IA
  • origenpais_origen95%
Quality guaranteed

Automatic validation

Every data point goes through ESPR rules. Errors caught instantly.

trace_check --mode=strictPASSED
Schema validation45ms
Digital Link resolution120ms
PEF impact data gapsWarn
2 passed1 warning0 failed
Integrated collaboration

Supplier portal

Suppliers complete their data directly with automatic validation.

Requests3 suppliers
  • Spinning mill · Tier 22 h agoValidated
  • Weaving · Tier 1due in 3 dPending
  • Dyeing · Tier 1nowUploading
Differentiated access

One DPP, three audiences

Each stakeholder accesses the information they need. Consumers, authorities and internal teams, each with their own view.

Impact Engine

Impact built into the same flow

LCA-lite metrics calculated automatically. CO₂, water and energy with equivalences everyone understands.

2.4kg CO₂Carbon footprint≈ 14 km by car
1.850LWater consumption≈ 24 showers
18.5kWhEnergy consumed≈ 2 days of a household
Methodology aligned withPEF · PEFCR · CSRD ESRS
Pilot 2026

Product data structured for ESPR

Product data is structured for ESPR from day one. Access via the 2026 Pilot.

The DPP & Data Hub is the TraceWeave canonical record: an ESPR-native model of 35+ fields where product, materials, chain and impact are entered once. From that record derive the Digital Product Passport, the CSRD report, risk and impact, without duplicating data across tools.

One record, every output
Record dataOutputs that consume itReference rule
Composition and materialsDPP · labelling · riskESPR Art. 9 · Regulation (EU) 1007/2011
Stages and facilitiesTraceability · DPP · mapESPR (EU) 2024/1781 Art. 8
CO₂ / water / energy impactCSRD (ESRS E1) · DPP · boardDelegated Regulation (EU) 2023/2772
Substances of concernDPP · risk alertsREACH Art. 33 · SCIP

Frequently asked questions about the canonical record

What is a canonical product record?

It is a single structured source of truth per product: composition, materials, suppliers, chain stages, certifications and impact live in one data model with identity and versioning. Every output (DPP, CSRD, risk) is derived from the record, so correcting a data point corrects it everywhere.

How many fields does the ESPR-native model have?

More than 35 fields aligned with ESPR Articles 8 and 9 and with the JRC schemas: identification, composition and labelling (Regulation (EU) 1007/2011), multi-tier chain, substances of concern (REACH Art. 33), impact and circularity. The model is versioned as the textile delegated act advances.

How is data ingested?

Through three channels: API-first for existing systems (PIM, ERP, e-commerce), a TracePulse-assisted import wizard for CSV and Excel files, and the Supplier Portal, where suppliers answer structured data requests with automatic validation at the point of entry.

Last reviewed: