The Digital Product Passport becomes mandatory category by category, with the first deadlines in 2027. A DPP platform is not a QR code generator: it is the infrastructure that creates, validates, publishes and keeps your passports reachable for the product's whole lifetime. Here are the five building blocks it must cover, and the six questions to ask any provider.
passports deployed across industries · September 2026
brands
regulations covered by a single engine
SOC 2 Type II · GS1 partner · AFNOR member · legal archiving with Arkhineo (Docaposte, NF Z42-013). Ranked a Market Leader by ABI Research · August 2024.
Your deployment
Choose a product family, target markets and a data owner. Identify the applicable requirements and the gaps to close.
Map an ERP/PIM export or API data to the passport, define identifiers and access rights, then check a representative sample.
Verify publication, scanning, updates and data export. Agree acceptance criteria before expanding to more products.
A catalogue sample, product references and volumes, target markets, available ERP/PIM data and the intended customer journey. These inputs define the pilot scope.
Product volumes, data quality, integrations, access rights and the services to activate. The pilot schedule and estimate are agreed after scoping; there is no universal price or delivery time.
Your teams and suppliers provide and validate source data. Arianee supports passport creation, validation and access. The economic operator retains its regulatory responsibilities.
Include data export, identifier continuity, permissions and the migration process in the pilot acceptance criteria. Ask to see these operations with your own product sample.
An incomplete platform gets paid for twice: once on purchase, and again when it has to be replaced at the first delegated act its data model cannot absorb.
Every product carries a unique identifier at the granularity its category requires (model, batch or item), reachable from a data carrier — QR code, NFC or RFID. Standard EN 18219 requires a resolvable, globally unique URL: it is the entry point to everything else.
The consumer-facing portal →Mandatory data differs by product category and is set by delegated act. A DPP platform has to model those schemas, version them as the rules evolve, and absorb heterogeneous sources — ERP, PIM, PLM, supplier spreadsheets.
The management back office →Publishing an incomplete passport exposes you to market withdrawal. Completeness and consistency checks must run automatically and before publication, with evidence of what was published, when, and by whom.
The compliance engine →Consumers, repairers, recyclers, logistics partners and market surveillance authorities do not see the same data. The Commission's JRC145830 report describes a five-tier model, role-based and need-to-know: your industrial data stays yours.
The five-tier access model →The passport must stay reachable for the product's entire lifetime — often longer than any software contract. That requires integration APIs, registration with the EU registry, and a portability guarantee if you change provider.
The enterprise APIs →Compare providers on the same scope. For each criterion, ask for evidence and agree what the pilot must demonstrate.
A named customer, the deployment scope and the services used. Check the requirements applicable to your products separately.
Ecosystem × Fnac Darty for appliances; Breitling for watchmaking. Each case study describes the project.
A dated figure, its scope and a test at the volume planned for your catalogue.
4M+ passports deployed across industries, confirmed on 11 September 2026. This is not the volume of a single customer or battery project.
A test with your data: import, publication, updates and error handling. Ask which connectors are available and what work is needed.
The API documentation and integration workflow are public. The connection to your ERP or PIM is defined during scoping.
A test export, continuity of identifiers and passport access, exit costs and responsibilities written into the contract.
The Arianee protocol is open source. Data export and service continuity also need to be tested in your project.
A demonstration of role-based permissions, hosting locations and the scope of security audits.
The Trust Center describes security commitments. Review access rights, hosting and supporting documents for your deployment.
A quote separating integration, issuance, hosting, maintenance, support and exit. A schedule identifying the data needed and the owner of each step.
Pricing depends on volume, available data and integrations. Bring a catalogue sample to scope the pilot.
The same product data feeds different obligations. Handling it in a single repository avoids running the whole project again at every deadline.
The general DPP framework. The EU registry has been live since 20 July 2026 and its operating rules apply since 6 August 2026 (implementing regulation 2026/1778).
Regulation details →Traction, industrial and electric-vehicle batteries. The nearest and most detailed deadline to date.
Regulation details →Electrical and electronic equipment: collection, repairability, end-of-life treatment.
Regulation details →French environmental disclosure obligations and sustainability reporting, both drawing on the same product data.
Regulation details →Six of the eight European standards from CEN/CENELEC JTC 24 have been published as EN:2026 standards since 27 May 2026; two remain final drafts under formal vote. A published standard does not confer presumption of conformity until it is cited in the Official Journal of the European Union — see the EU registry and its timeline.
The gap between a demo and a production rollout shows up in the installed base, retroactivity and support. These deployments are public.
Producer responsibility organisation and retailer: repairability passport across an appliance fleet.
Watchmaking: item-level passport, digital warranty and authenticated resale.
Textiles: product identity and a direct customer relationship from the scan.
Watchmaking: service history and lifecycle traceability.
Fashion: access to the Mugler bag passport through its QR code.
Yachting: the Astor 36 boat passport and access to product information.
A DPP platform is the software that creates, validates, publishes and keeps Digital Product Passports reachable. It brings together five building blocks: a unique resolvable identifier carried by a QR code, NFC or RFID tag; a data repository structured against the regulatory schemas; a compliance validation engine that runs before publication; role-based access rights; and APIs that handle integration and keep the passport available for the product's whole lifetime.
Compare deployed volumes, integration with your systems and results from a representative pilot. Arianee reports 4M+ passports deployed across industries as of 11 September 2026. ABI Research ranked Arianee second overall and among two Market Leaders in its August 2024 assessment. Check the customer references and test the volume required for your project.
The first obligations land in 2027, starting with batteries on 18 February 2027. The lead time to plan for is not the software but the data: structuring a complete, consistent product repository out of an ERP, a PIM and supplier files typically takes six to ten months. Since the EU registry went live in July 2026, testing is possible today.
A QR code is only a data carrier: it points at an address. A DPP additionally requires a unique, globally resolvable identifier, a mandatory data set defined by delegated act, a compliance check before the product is placed on the market, differentiated access depending on who is looking, and registration with the EU central registry. A QR code linking to a product page satisfies none of these.
Compare six points: sector references, deployed volumes, integration with your systems, data portability, security and total cost. Ask for dated evidence, test a representative catalogue sample and record the pilot acceptance criteria in the proposal.
No. Six of the eight European standards from JTC 24 have been published as EN:2026 standards since 27 May 2026; two remain final drafts under formal vote. One caveat: a published standard does not confer presumption of conformity until it is cited in the Official Journal of the European Union. The technical foundations — identifier, data carrier, API, storage, security — are nonetheless stable enough to build on today.
More questions about the DPP? The full FAQ or the EU DPP guide.
Thirty minutes is enough to place your catalogue, your regulatory deadlines and the state of your product data — and to say whether our infrastructure is the right call for you.