Ensure your DPPs comply before, during and after publication
Compliance Engine covers the three moments of compliance: validating your data against ESPR, WEEE, Battery Pass and AGEC-CSRD before publication, monitoring and fixing it in real time throughout the product's life, then registering the passport in the EU DPP Registry and archiving the proof with legal value.
Every field checked, before publication.
The Compliance Engine checks each DPP against the ESPR, GS1, AGEC and PEF schemas. Errors are raised in real time, auto-corrected where possible and escalated to the operator otherwise. Nothing is published while a field is still red.
Compliance does not stop at publication.
A passport that complies on the day it is created may not comply six months later: the regulation evolves, the battery ages, the product is repaired and resold. Compliance Engine holds all three moments.
Validation
Nothing goes out until the passport passes the schema of the regulation that applies.
- ESPR, WEEE, Battery Pass and AGEC-CSRD templates aligned with the latest version of the text
- Every mandatory field checked against the schema, on every save
- Publication refused while a mandatory field is missing or invalid
- Product identifier issued as a GS1 Digital Link, resolvable from the first scan
Monitoring
A DPP's compliance is not settled on publication day: data ages and regulations move.
- Compliance dashboard: the status of every passport, by product, by batch, by regulation
- Real-time alerts on fields that are missing, outdated or no longer compliant
- Fixes made from the platform, with no re-keying and no custom development
- Dynamic updates of in-use data: state of health (SoH), repairs, ownership changes
- Regulatory monitoring: templates follow changes in the text
Proof
What is left when a market surveillance authority, an auditor or a buyer asks to see.
- Registration in the EU DPP Registry through the standardised CEN 18222 API
- Time-stamped proof of registration, archived with legal value (Arkhineo, eIDAS, NF Z42-013)
- Kept for 10 years, the retention period the regulation requires
- Full, exportable audit trail — for an inspection as much as for an RFP grid
A structured data model, aligned with JRC145830
The compliance engine rests on a normalised data model: each DPP is composed of a static layer (Core DPP) and a dynamic journal (Life-cycle Log). Data is typed, versioned and linked to an explicit granularity (model, batch or item). This is what makes validation deterministic, auditable and extensible to all regulations.
Static product layer
Identification, material composition, technical characteristics, mandatory documentation, compliance declarations. Fixed at market placement and cryptographically anchored for audit.
- — Unique identifier (GS1, DID, URI)
- — Composition & substances of concern
- — Carbon footprint & recycled content
- — Durability, repairability, manuals
Lifecycle journal
All post-market events are recorded append-only: sale, repair, maintenance, resale, collection, recycling. Each entry is attributed to an actor according to the 5-level RBAC model.
- — Ownership & after-sales events
- — Maintenance & replaced parts
- — WEEE collection & reuse
- — End of life & recycling
3 granularity levels
Data shared by all units (specs, composition, type compliance).
Data common to a production run (date, factory, materials, carbon footprint).
Unique data per unit (serialisation, owner, after-sales history, end of life).
Reference: JRC145830 — Methodology for defining data requirements for the DPP under the ESPR framework.
Four regulations, one engine.
Each regulation has its own template and validation rules. They run in the background at every save — you only see the alerts that matter.
Ecodesign for Sustainable Products (ESPR)
All energy-related and relevant products (electronics, textiles, etc.)
Validated mandatory fields
Technical specifications · Environmental data · Durability and repairability · Substances of concern · Mandatory documents (manual, warranty)
Validated mandatory fields
Material composition · Dismantling instructions · Hazardous substances · Manufacturer identification · Recycling traceability
Validated mandatory fields
Chemical composition data · Energy performance · Carbon emissions · Lifecycle status · Unique battery QR code
Circular economy and sustainability reporting
Large companies and sustainability reports
Validated mandatory fields
Sustainable supply chain · Circularity action plan · Environmental impact data · Governance and traceability · CSRD reporting
The engine that refuses to publish an invalid DPP.
Before each publication, the DPP is compared against the applicable regulation's schema — then again on every update, for as long as the product lives. You know exactly what's missing, what's outdated, what won't pass.
- Pre-configured templates
- Ready-to-use ESPR, WEEE, Battery Pass, AGEC-CSRD templates. Aligned with the latest regulation versions.
- Automatic validation
- Validation engine that checks data completeness and validity before publication.
- Real-time alerts
- Instant flagging of missing fields, outdated data, or non-compliant entries.
- Compliance dashboard
- Overview of the compliance status of all your DPPs. Detailed statuses per product.
- Certified legal archiving
- Arkhineo partnership (Docaposte Group). Secure archiving with legal probative value for audit.
- Regulatory monitoring
- Automatic template updates when regulations evolve. You are always up to date.
An archived DPP is one that holds up in court.
Compliance Engine integrates natively with Arkhineo (Docaposte Group), the French leader in electronically archived documents with probative value. Data centres in France with geographic redundancy, trusted timestamping, electronic signature, audit trail of every consultation and modification.
Archiving certificates are accepted by French authorities and courts. GDPR-compliant, NF Z42-013 standard, international standards. Dedicated interface for regulatory audits and inspections.
Regulatory cadence, not marketing cadence.
Compliance is ongoing work. Regulations evolve, obligations change, deadlines arrive. Compliance Engine maintains the pace — reports and alerts calibrated to the real needs of a legal or quality team.
- Daily
- Compliance alerts · Publication status scan
- Weekly
- Completeness report · Non-compliance summary
- Monthly
- Full audit trail · Compliance report · Engagement analytics
- Annual
- Legal archiving · Compliance certification · External audit
AFNOR, GS1, Arkhineo, SOC 2.
Regulatory compliance does not happen by improvisation. AFNOR member for French standardisation, GS1 partner for product identification standards, Arkhineo (Docaposte) for electronic archiving with probative value, SOC 2 Type II certified for enterprise data security.
Connected to the EU DPP Registry.
The EU central registry for Digital Product Passports, established by Article 13 of the ESPR, has been live since 20 July 2026 and its operating rules apply since 6 August 2026. Compliance Engine registers every passport there through the standardised CEN 18222 API. Arianee is a member of the CIRCUIT4EU consortium and an active partner in the regulatory initiatives defining the standard.
Standardised APIs, support for GS1 · EPCIS 2.0 · JSON-LD, governance model aligned with the Commission's. The registry only keeps a proof of registration: your passport data stays with you, portable and auditable.
Other platform modules
See Compliance Engine in action?
Fifteen minutes with one of our experts, on one of your products and the regulation that applies.
Request a demo