Skip to content

Digital product passport

Digital product passport (DPP): structuring the supplier data that feeds it, with its proof

A digital product passport (DPP) is filled with supplier data: composition, origin, certifications, repair and recycling terms. Zylio extracts that data from your quotes, orders, invoices, delivery notes and certificates, structures it into normalised attributes, cross-checks the documents against each other and links every value to the document, page and line it came from.

The starting point

The passport data sits with your suppliers, and already with you

The digital product passport (DPP) is the digital identity record a product will have to carry: what it is made of, where it comes from, how it is repaired and recycled, with the proof. Most of that information comes from your suppliers. And most of it has already been sent to you, in one form or another.

A detailed quote describes the materials. A technical sheet attached to the offer gives the proportions. An invoice carries the country of origin. A delivery note confirms the batch and the shipping site. A certificate of conformity, emailed once, attests a label with its validity date. Each document knows one thing; none of them knows everything.

The problem is therefore not to go and find data but to link the data that exists: attach each attribute to the right product reference, the right supplier, the right document, and spot when two documents contradict each other. That structuring work is what Zylio takes on.

What the ESPR regulation requires, and which data to collect

The European framework, the timeline by category, the six data families.

The mechanism

Collect, structure, cross-check: the three steps

Zylio asks for no re-keying and no forms. The Capture agent reads documents as they arrive (dedicated mailbox, file drop, SFTP, ERP export, supplier portal) and in every format: native PDF, scan, photo, spreadsheet, structured feed, in several languages. It extracts every line and every attribute without detaching it from its source.

  1. 01

    Collect

    Every document that speaks about a product: quotes, technical sheets, orders, invoices, delivery notes, certificates, declarations. Where they are, in the form they are in.

  2. 02

    Structure

    Each attribute is brought back to a common vocabulary: material, proportion, origin, certification, unit. Different supplier labels for the same thing are aligned.

  3. 03

    Cross-check

    For the same reference, quote, order, invoice and delivery are confronted. What agrees is consolidated; what diverges comes up with its reason.

The model

What a product dataset structured by Zylio contains

Six properties, present for every attribute, whatever the product category.

  • A unified product reference

    The same item under three supplier codes becomes one reference, linked to its variants. Zylio’s knowledge graph holds that link.

  • A unified supplier

    The same supplier under several legal names or entities is recognised as one actor, with its sites and its tiers in the chain.

  • An attribute linked to its source

    Each value points to the document, the page and the line where it was read. One click opens the document, highlighted at the exact spot.

  • A time stamp and a version

    When the value was read, from which document, and what it replaces. History is consulted, not overwritten.

  • An explicit status

    Verified when several documents agree, inconsistent when they diverge, missing when none provides it. Never estimated.

  • An export to your register

    The dataset goes to your DPP register, your PIM or your quality tool, in their format. Zylio feeds them; it does not replace them.

The discrepancies

What cross-checking the documents brings up

The value of a passport lies in the consistency of its data. Zylio does not assume your documents agree with each other: it compares them and flags what does not match. The quote announces organic cotton, the invoice standard cotton. The certificate attached to the offer expired before the delivery date. Two suppliers declare different origins for the same reference. A recycled content proportion varies from one batch to the next without explanation.

Each inconsistency comes up with the two documents side by side and the reason for the gap. You decide: ask the supplier for clarification, retain one value, set a document aside. Zylio does not decide for you and contacts nobody. It makes the question visible, with the documents needed to answer it.

No discrepancy is set aside in silence. What matches no rule comes up, with its reason.

What changes

What changes for the teams preparing the passport

Collection stops being a data entry campaign. Procurement, quality and sustainability teams no longer fill spreadsheets from PDFs; they review attributes that are already proposed, with the source one click away, and handle the inconsistencies. Depending on scope and data maturity, that is from 15% to 45% of time given back to teams, per FTE.

Volume stops being an obstacle. The platform reads documents of more than a hundred lines, multi-page specifications and dense price tables included, and absorbs more than 10,000 supplier documents a week, across all formats. A catalogue of several thousand references is handled like a catalogue of a hundred.

The passport stops being frozen. When a delegated act adds an attribute, or a supplier sends a renewed certificate, the dataset is completed from the new document, without redoing the others. The audit trail keeps track of every update.

Our limits

Three limits, set before starting

Zylio contacts no supplier: missing data is flagged as missing, and the request remains yours. Zylio commits nothing without your validation: no attribute is published to a register without a person having accepted it. Zylio does not touch your information system: it reads exports and documents, it does not write to them.

Your documents are hosted in France, under ISO 27001 and SOC 2 Type II certifications. They are never used to train a model and never shared between customers.

Security and compliance of the platform

Hosting in France, certifications, data usage, audit trail.

Capture

Gather and consolidate all your procurement data.

Collection by dedicated mailbox, upload, SFTP, scan, API or ERP export. Reads every format (native PDF, scan, photo, spreadsheet, structured feed), then extracts line by line: supplier, references, quantities, unit prices, discounts, taxes, terms.

The end of re-entry. A procurement history you can finally query.

What Capture detects

  • Long documents and multi-page tables
  • Unknown layouts
  • Several languages and currencies
  • Poor scans and handwriting

Nothing is lost. Everything can be checked, everything can be proven.

  • The contract clause and the invoice line, highlighted side by side.
  • Every extracted value stays linked to the exact place in the document where it was read.
  • The same case produces the same decision, today as in six months: the rules are applied deterministically.
  • No discrepancy is set aside in silence. Anything that matches no rule is raised, with its reason.
  • The agent records what it did, in the order it did it: who, what, how much, when.

Frequently asked questions

Which documents does Zylio read to feed a digital product passport?

Everything that describes a product or its supplier: quotes and technical sheets, purchase orders, invoices, delivery notes, certificates of conformity, material declarations, label attestations. As native PDF, scan, photo, spreadsheet or structured feed, in several languages. No prior formatting is required.

What happens when a data point is missing?

It is declared missing for the reference concerned, with the list of documents read that could have contained it. Zylio never estimates an absent value and does not contact the supplier: you know precisely what to ask, whom to ask, and for which reference.

Does Zylio replace a PIM or a DPP register?

No. Zylio produces a structured, sourced and time-stamped dataset, then exports it to the tool you choose: PIM, DPP register, quality tool or a simple spreadsheet. It sits upstream, where the data is still inside documents, and leaves publication to your tool and your validation.

How does the data stay up to date?

Each new document, whether a renewed certificate, an invoice for a new batch or a revised technical sheet, is read and attached to its reference. The previous value is not overwritten: it is versioned, with the date and the source. You see what changed, when, and on the strength of which document.

Measurable impact in every environment

More than 5 million procurement documents analysed

Between 1 and 7% of margin recovered

on the scope analysed

From 15 to 45% of time given back to teams, per FTE

depending on the scope and on data maturity

Zylio fits into your existing ecosystem.

The ERP runs the process. Zylio handles the exception and recovers the value that escapes it: invoices without a purchase order, line-by-line price discrepancies, duplicates and overbilling, off-contract spend.

  • SAP
  • Sage
  • Oracle
  • NetSuite
  • Microsoft Dynamics 365
  • Pennylane
All integrations

Your data under high security.

Zylio meets the most demanding standards, and nothing is committed without your approval.

Certifications
SOC 2 Type II · ISO 27001
Hosting
Hosted in France
Encryption
End-to-end AES-256 encryption
Access
Enterprise SSO · multi-factor authentication · Zero Trust approach
Security and compliance

See what this looks like on your own data

Twenty minutes, on a spend category of your choosing. We show you what the agents detect, with the evidence behind it.

  • No commitment, on your own data
  • Result in 3 weeks
  • 20 minutes, no sales pitch
  • Your data stays hosted in France
  • No change of tool or process