DPP provider or your own software?
Outsourced provider or your own build
The question is not whether, but how
The Digital Product Passport is coming for your product group — that much is settled. The real decision is how to do it: outsource the burden to a DPP provider, or buy software and build and maintain the passports yourself. The choice depends on your volume, your in-house resources and how close your deadline is.
See the platform and the technical standards we build on →
What are you after?
Your own software (in-house)
WIARA as your DPP provider
Getting started
Your own software (in-house)
You hire a team and learn the standards
WIARA as your DPP provider
You start right away with a ready process
Regulatory expertise
Your own software (in-house)
You track ESPR, CBAM and delegated acts yourself
WIARA as your DPP provider
We track and translate the requirements for you
Data and quality
Your own software (in-house)
You structure and validate everything
WIARA as your DPP provider
We help you collect and validate the data
EU registry
Your own software (in-house)
You integrate it yourself
WIARA as your DPP provider
Registry connection in preparation; registration uses your own qualified electronic seal
A change in the law
Your own software (in-house)
You rebuild yourself on every change
WIARA as your DPP provider
We update the platform on every change
Time to ready
Your own software (in-house)
Months of development
WIARA as your DPP provider
Days to weeks
Upfront investment
Your own software (in-house)
High — development and a team
WIARA as your DPP provider
Low and predictable, subscription
Non-compliance risk
Your own software (in-house)
You carry it entirely
WIARA as your DPP provider
We share the regulatory burden with you
When each fits
Your own software makes sense
If you have a large in-house IT and regulatory team, very specific needs and enough time before the deadline.
A provider makes sense
If you want speed, predictable costs and someone to carry the regulatory burden for you.
A hybrid approach
Often you start with a provider for speed and gradually take parts in-house — with no disruption.
The data is yours either way
Data and passports stay yours: everything you enter is reachable through the REST API, and every published passport carries its data as JSON-LD. You can also export all of it at any time, in open formats — no vendor lock-in.
The platform behind this guide: DigitalProductPassport by WIARA
The page above describes both routes. We are the first one: a provider you buy from, rather than a codebase you maintain.
If you choose the provider route, our comparison of eight DPP platforms sets out what each vendor publishes about itself, including us.
DigitalProductPassport by WIARA is the cloud platform behind the worked examples on this site, built by WIARA, a software company. You enter the product data once and it publishes the passport page, the QR code and the machine-readable file, in all 24 official EU languages, with model, batch and item level passports and a full change history.
The free plan covers 3 passports in total. What the platform does is set out on the product page, and the plans and their limits are on pricing.
DPP provider or software
Frequently asked questions
The data and passports stay yours. Everything you enter is reachable through the REST API, and every published passport carries its data as JSON-LD behind a GS1 Digital Link address. You can export all your data at any time — every passport, all files and metadata — in open formats. No vendor lock-in: if you leave, your data comes with you.
Rarely, once you count the full cost — team, development, maintenance and risk. A provider spreads that into a predictable subscription.
Yes, that's a common path. You start fast and later bring parts in-house, without losing the data.
A short consultation — we review your volume, resources and deadline and tell you honestly which approach fits.
The platform carries templates for textiles, furniture, masonry, reinforcing steel, structural steel, aluminium, tyres, lighting and batteries. Templates are maintained centrally and updated when the rules change, and you are notified when a passport needs a new version. If your product group is not on the list, we build the template with you.
GS1 Digital Link and JSON-LD, yes: passports resolve through GS1 Digital Link, data is published in structured form (JSON-LD), and every product gets a permanent web address on EU infrastructure. EPCIS 2.0 is on our roadmap. The OpenAPI specification is on our API page.
All three, as the relevant delegated act requires. The Battery Regulation requires a passport per individual battery.
Every change is written to an audit log: who entered the value, when, and the before and after states, so every value is traceable to its author. Published passports stay online for the product's lifecycle plus 10 years as our own commitment.
A REST API for ERP and PIM integration, through which everything in your account is reachable, plus a full export of all data in open formats. The specification is public on our API page.
Under the regulation, the economic operator placing the product on the market is responsible for data accuracy. The platform validates structure and completeness against the category requirements, but cannot substitute for the truth of the inputs — which is why the audit log records the source of every value.
Everything you enter is reachable through the REST API, and every published passport carries its data as JSON-LD on a public page. You can export all your data at any time — every passport, all files and metadata — in open formats. No vendor lock-in: if you leave, your data comes with you. The data is yours.
On infrastructure in the European Union. Passport pages are published as static files on a European content delivery network, with a permanent address per product.
