Passvanta

Digital Product Passport implementation guides

Supplier Data Collection for DPPs: From Request to Accepted Evidence

Supplier collection succeeds when both sides understand the question and what counts as an acceptable answer. Sending every possible field to every supplier usually creates more interpretation work. Use a defined product and a small set of genuine gaps to establish a repeatable request, response and review process before scaling it across the supply base.

Sources checked:

Start with gaps your team can explain

Review existing specifications and declarations first. For each missing value, record the component, information owner, preferred unit and purpose of the request. This is an operational collection method; the applicable product requirements determine which information is legally needed.

Separate absent data from conflicting data. A blank composition field and two contradictory composition statements require different questions. Give the reviewer access to the originals and preserve the unresolved state until someone can substantiate a decision. Do not remove uncertainty merely to improve a completion percentage.

Source: Passvanta — Documented product evidence and review workflow

Write a request that can be answered

Name the supplied item using a reference the supplier recognises. Specify the requested period, production version or material specification where relevant. Ask whether a percentage refers to a component or the finished product, and allow the supplier to explain why the requested value is unavailable.

Use a short example of the expected unit or scope, while avoiding a suggested answer that could be mistaken for a confirmed value. State the response date as a project agreement, not an invented legal deadline. Ask the recipient to identify the person who can resolve technical questions.

Source: Passvanta — Supplier Portal

Choose access appropriate to the relationship

Passvanta offers limited guest requests for selected field values and accounts for ongoing supplier relationships. Guest links have expiry and revocation controls. A supplier account requires an accepted customer connection and does not receive access to the customer's entire workspace.

Documents follow a separate boundary: uploads require the signed-in, linked supplier portal and customer permission. Tell the supplier which route applies before requesting files. For a pilot, test the request with a colleague acting as a supplier and confirm that only the intended information is visible.

Source: Passvanta — Supplier Portal

Evaluate what a document actually covers

A document title is not enough. Check its issuer, date, product reference, tested sample and limitations. A facility certificate may not support a particular material claim. A test for one construction may not cover a replacement adhesive or a different production site.

Keep a short explanation of why the source supports the proposed value. In Passvanta, extraction creates reviewable proposals with source references; it does not independently approve them. If the evidence does not answer the question, return a precise clarification request rather than accepting a familiar-looking certificate.

Source: Passvanta — Documented product evidence and review workflow

Separate receipt, acceptance and publication

Treat receipt as the beginning of review. Check completeness of the response, then assess the source and product fit. Assign acceptance to someone with the relevant authority. A fast response is useful, but speed does not resolve inconsistencies between a declaration and an engineering specification.

Passvanta keeps customer acceptance separate from the supplier submission. Publication is another authorised action. Define which unresolved questions block your internal release and who can settle them; do not promise that every operational rule you write is automatically enforced by the software.

Source: Passvanta — Supplier PortalSource: Passvanta — Passport publication and lifecycle

Follow up on reasons, not only response counts

Measure requests returned, responses accepted after review and clarification cycles separately. These are suggested project measures, not claimed built-in dashboards. Record why a request stalled: wrong contact, unclear component, missing test or disagreement about disclosure. The remedy depends on that reason.

Agree on change triggers with recurring suppliers. When a specification, source or treatment changes, review the affected evidence instead of asking for the complete library again. Retain the previous context and assign an owner to overdue clarifications so a staff change does not erase the open decision.

Source: Passvanta — Documented product evidence and review workflowSource: Passvanta — Supplier Portal

Sources and supporting material

  1. Passvanta — Supplier Portal

    Checked:

  2. Passvanta — Documented product evidence and review workflow

    Checked:

  3. Passvanta — Passport publication and lifecycle

    Checked:

Explore and apply

FAQ

Frequently asked questions

Must every supplier create an account?

Field values can be submitted through a scoped guest request. An account supports an ongoing customer connection; supporting file uploads require that linked, signed-in route and customer permission.

Can we accept a supplier's estimate?

Keep the distinction between an estimate and measured or verified information. Assess whether that evidence is sufficient for the particular purpose and applicable requirements before approving it.

What if the supplier will not disclose a sensitive value?

Clarify the required scope and acceptable evidence with the responsible team. Do not invent a value or promise disclosure restrictions that have not been configured and checked.

Passvanta

Start with the information you actually have

Assess your operational preparation and identify data gaps and next steps.