One platform, from supplier data to a compliant passport
The AI does the manual data labour that forces everyone else into a services contract — reading documents, translating them, mapping them to the legal schema, and telling you what is still missing.
The core loop
One continuous run from the data you already have to a passport at its own URL. The AI carries the middle of it — which is the part that otherwise needs people.
- 01OnboardPick a category template
- 02Pre-fillAI reads your product dataAI
- 03MapAI matches it to the legal schemaAI
- 04InviteSuppliers get a magic linkAI
- 05ExtractAI structures what they sendAI
- 06ValidateGaps and implausible values flaggedAI
- 07ConfirmYou sign off what is legally material
- 08PublishGS1 Digital Link, QR, JSON-LD, resolver
Registration with the EU registry joins the end of this run once its API is final — the enrolment is done, the interface is not.
Where the AI actually sits
Marked honestly: what ships in v1, and what does not yet.
- Compliance advisorUnderstand what your category obligesIn v1
- Data ingestionImport and read your existing product dataIn v1
- Schema mappingMatch your fields to the legal onesIn v1
- Supplier extractionRead, translate and structure supplier documentsIn v1
- ValidationFlag gaps and implausible values before publishIn v1
- Consumer copyDraft the public-facing text in EU languagesIn v1
- Agentic chasingFollow up with unresponsive suppliersLater
- Regulatory monitorWatch for changes that affect your passportsLater
The hard part is the supplier data
How the supplier flow worksSixty to eighty per cent of what a passport needs sits with your suppliers rather than in your ERP, and visibility collapses past the first tier. That is why the incumbents need services teams and why the cheap tools skip it.
Everdge asks a supplier for what it actually needs, in their language, and accepts whatever they already have. Fill a component once — a fabric, a cell — and it is reused across every product that contains it, so each passport costs less than the last.
Guardrails
About EverdgeA passport is a legal document. The product is built on the assumption that someone will one day be asked to defend every value in it.
AI drafts. A human confirms.
Anything legally material waits for your sign-off. The AI never publishes a value on your behalf.
Provenance on every value
Source document, confidence, and who confirmed it — kept with the value, not in a log you cannot reach.
The advisor is grounded
It answers from the regulation and your own data, and says when it does not know. Signal, not legal advice.
Green claims get checked
A plausibility check runs before publish, and a human confirms. An unsupported environmental claim is the expensive kind.
Questions
Does the AI make the legal decisions?
No. It drafts, extracts and flags; you confirm anything legally material. The obligation stays with whoever places the product on the EU market, and the product is built so that the record shows who signed off what.
How does the supplier flow work?
Your supplier gets a link — no account, in their language — and sends whatever they already have: a PDF, a certificate, a spec sheet, a photo. The AI extracts, translates and structures it into the passport schema, and tells you what is still missing.
Which categories are supported?
Battery and textile templates ship first, because those are the two the EU switches on first. The rest of the ESPR queue follows its delegated acts.
Can I import my existing data?
Yes — CSV, ERP or PLM export. The AI maps your columns to the legal fields rather than making you do it, and shows you the mapping before anything is used.