What DPP means for SMEs in practice
For SMEs, the Digital Product Passport is rarely a standalone IT project. The key questions are which products may be affected, which data already exists in ERP, spreadsheets, supplier files or certificates, and which obligations will only become concrete through delegated acts.
The consulting work translates regulatory requirements into a lean working structure, so teams do not start with an enterprise roadmap that ignores budget and data reality.
What the SME start clarifies
Nulara prioritises a few reliable decisions: product groups, data sources, evidence gaps, supplier roles and a first process for maintenance and approval.
- Applicability: Which product groups are first relevant through battery passports, ESPR priorities or customer requirements?
- Data estate: Which data already exists in ERP, PIM, spreadsheets, certificates or supplier files?
- Roles: Who maintains product data, reviews evidence and approves product-pass information?
- Start plan: Which small work packages create measurable progress in the next few weeks?
Consulting outcome
- SME-ready DPP applicability and priority list
- Overview of existing data sources and missing evidence
- Lean role and approval model
- First implementation plan without unnecessary system migration
Sources and next steps
The SME start connects ESPR foundations with operational Nulara pages for readiness and product data.
Nulara deep dives
- DPP Readiness Check - Fast first classification of product groups and data gaps.
- Centralize product data - Operational use case for data sources, required fields and product families.
- ESPR - Regulatory overview of framework, exemptions and delegated acts.
Primary sources
- European Commission: ESPR - Official overview of the ESPR framework and implementation through working plans.
- EUR-Lex: Regulation (EU) 2024/1781 - Legal basis for product passports, data requirements and SME-related support.
SME DPP consulting FAQ
- Is this only for large manufacturers?
- No. SMEs benefit from sorting DPP requirements early and reusing existing data instead of launching unnecessarily large programmes.
- Do we need to introduce a new system immediately?
- No. The start first reviews data estate, gaps and responsibilities. System decisions come once requirements are reliable enough.
- Which teams should join?
- At minimum product, procurement, quality or compliance. In small teams, a few people may cover several of those roles.
