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
You hire a team and learn the standards
You start right away with a ready process
Regulatory expertise
You track ESPR, CBAM and delegated acts yourself
We track and translate the requirements for you
Data and quality
You structure and validate everything
We help you collect and validate the data
EU registry and eIDAS
You integrate it yourself
Ready integration and passport registration
A change in the law
You rebuild yourself on every change
We update the platform on every change
Time to ready
Months of development
Days to weeks
Upfront investment
High — development and a team
Low and predictable, subscription
Non-compliance risk
You carry it entirely
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
With WIARA you are not locked in — the passports and data stay your property, on open standards.
DPP provider or software
Frequently asked questions
No. The data and passports stay yours, on open standards (GS1, the EU registry), so you can migrate or take it in-house.
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 sector templates for the twelve categories we publish solutions for — from batteries and textiles to furniture and steel. Templates are maintained centrally and updated when the regulation changes, and you are notified when a passport needs revision.
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. Technical detail, including EPCIS and OpenAPI, is documented on our API page.
All three, as the relevant delegated act requires. The Commission's registry currently operates at item level for batteries.
Every change is written to an audit log with seven-year retention — who entered the value, when, and the before and after states. That covers the regulatory retention period and makes every value traceable to its author.
A REST API for ERP and PIM integration, plus full data export. 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.
Yes, at any time and in open formats — this is also a regulatory obligation under ESPR Articles 10(4) and 27(1)(c), which the platform was designed against. 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.
