The Make-or-Buy Decision
Build vs Buy: Should a Factory Build Its Own DPP System?
The honest framing: a Digital Product Passport system is not one project but four ongoing operations — data structuring, identifier management, decade-scale hosting, and standards-tracking as delegated acts and EN standards evolve. A basic in-house build runs roughly €80,000–250,000 and six to twelve months before maintenance begins. Buying a specialist platform turns that into a subscription and a service-level agreement. The right answer depends on scale, software capacity and how core the passport is to your business.
Written by Nazrul Islam, Founder, DPPLive · Last updated: 16 July 2026
Build
What in-house really includes
Schema design against ESPR Annex III, identifier issuance and GS1 Digital Link resolution, tiered access (Article 11 audiences), version integrity, registry submission when textiles onboard, and hosting engineered for the lifetime-plus-ten-years horizon. Then: permanent staffing to track every delegated act and standard revision.
€80–250k + 6–12 months
Buy
What a platform amortises
The same machinery, spread across many customers: standards-tracking, registry interfaces, identifier stacks, hosting and verification tooling arrive as updates rather than projects. Your effort concentrates where it is irreplaceable — producing accurate factory data.
Subscription + SLA
Hybrid
The usual right answer
Keep your data pipeline (ERP, PLM, spreadsheets even) as the source of truth; rent the passport layer through APIs and structured imports. You stay portable — insist on full archive export — while the regulatory surface is somebody's full-time job.
Own data, rent machinery
Test 1
Volume & variety
Hundreds of styles across many buyers amortise a platform instantly; a build only pays back at group scale with engineering already on payroll.
Test 2
Standards exposure
The EN 18219-series system standards (ratified early 2026) are not yet harmonised; the 2027 textile act will set data fields and granularity. Whoever owns the build owns tracking every change — forever.
Test 3
Exit cost
Whichever path you choose, demand portability: open formats, exportable archives, documented schemas. A passport system you cannot leave is a liability wearing a compliance badge.
Build vs Buy FAQ
Quick Answers
How much does it cost to build a DPP system in-house?
+
Industry estimates for a basic custom build run roughly €80,000–250,000 over six to twelve months — before ongoing maintenance, standards updates and the decade-scale hosting commitment. Costs rise with serialisation, integrations and multi-buyer formats.
What is the biggest risk of building in-house?
+
A moving target. The EN 18219-series DPP system standards were ratified in early 2026 but are not yet harmonised, the textile delegated act lands in 2027, and registry interfaces will keep evolving — an internal build must track all of it indefinitely.
When does building make sense?
+
For very large groups with permanent software teams, existing PLM/ERP depth and volumes that amortise a compliance-engineering function — or where a passport is core product strategy (resale, authentication) rather than compliance.
Is there a middle path between build and buy?
+
Yes: run a specialist platform for the passport layer (identifiers, hosting, registry, standards-tracking) and integrate it with your own systems through APIs and structured imports — your data pipeline stays yours; the regulatory machinery is rented.
Keep Reading
Go Deeper
If buying: the evaluation checklist, vendor-neutral.
The operation an in-house build must run for a decade.
The integrity bar any system — built or bought — must clear.
Scope your styles, buyers and volumes against both paths.
Sources & official references
- Regulation (EU) 2024/1781 (ESPR) — full text on EUR-Lex — Articles 9–13 and Annex III (what any system must implement)
- CEN/CENELEC JTC 24 — EN 18219-series DPP system standards (ratified early 2026; harmonisation pending)
- Industry build-cost estimates: DPP vendor and consultancy analyses, 2025–2026 (figures indicative)
DPPLive’s Take
Build Your Data. Rent the Regulation.
Your product data is an asset — own it completely. The regulatory machinery around it is overhead — share it. That split is why the hybrid path wins for almost every factory: DPPLive runs the passport layer, your data stays exportable and yours.