Four problems that show up in every DPP project we join, and how the platform solves each one.
You can't comply with what you can't validate
The EU Ecodesign for Sustainable Products Regulation (ESPR) doesn't hand brands a checklist. Each product category has its own mandatory attribute set, its own labelling rules, and its own supporting standards — and those standards keep evolving. Most brands find out they're non-compliant after the fact, at customs or in a customer complaint.
DPP Agent ships with the validator built in. Every draft passport gets checked against the schemas that apply to its category: ESPR Base, AGEC textile, CIRPASS-2 core, and the EU Batteries Regulation. Missing mandatory fields are flagged the moment they're missing, with the exact regulatory text that requires them. Nothing publishes until the completeness score is green, and every version is archived per EN 18221 §4.2 lifetime retention so an auditor can reconstruct the record on demand.
Fair warning: no software makes non-compliant data compliant. What we do is stop it from shipping.
Your PIM is a graveyard of half-filled attributes
By the time a compliance project starts, most catalogues have been through five system migrations, three PIM re-implementations, and at least one round of merger consolidation. Attributes are inconsistent, families overlap, care instructions live as free-text somewhere, and the country-of-origin field has 40 % coverage on a good day.
DPP Agent's AI Suggest doesn't hallucinate. It reads the fields you have, cross-references category-mandatory rules and any tenant-level defaults you've configured, and proposes fills with a visible source citation for every value. Operators approve or override in-line. When we can't confidently propose a value, we say so — we don't invent data to hide a gap. That gate is deliberate: an auditor should never open a passport and find something the brand didn't sign off on.
The passport has to reach the consumer, not the vendor
A DPP that only lives inside a compliance vendor's subdomain is a legal artefact, not a brand asset. When a consumer scans the QR on a hangtag and lands onvendor.com/passport/12345they get a generic template with someone else's branding. Trust erodes; scan rates collapse.
DPP Agent runs your passports on your own subdomain (dpp.yourbrand.comor the DPP Agent-managed alternative yourbrand.dpp.dppagent.com) with your fonts, your colours, your logo, and no vendor watermark on paid tiers. Consumer analytics land in your admin: scans by country, device, referer, timeline. What consumers actually engage with informs what you improve next season.
Vendor lock-in is a real cost, not a rhetorical one
Compliance vendors love to talk about “lifecycle” and forget to mention that a DPP has a lifetime as long as the product does. Ten years for a heavy appliance, fifteen for a battery installation, effectively forever for a heritage watch. That's a decade of data you don't want held hostage by one integration you can't untangle.
DPP Agent connectors are additive and interchangeable: Akeneo, Centra, Shopify, Delogue PLM, WooCommerce, inriver, commercetools, Magento, or a plain CSV drop — use whichever fits the product line, mix them freely, and switch tomorrow. The passport URL doesn't change when you re-plumb the source. Data lives in EU-region infrastructure. Exports are available as CIRPASS-2 JSON any day of the week.
