The supplier data clause that decides your DPP timeline

Run the exercise once and the shape is always the same: of the fields a passport requires, a minority are already in your PLM, a few can be derived, and the rest are supplier-dependent — material composition, recycled content, substance declarations, provenance, and test evidence. You cannot build, buy, or automate your way past a field somebody else has to give you.

That is why platform-first programmes stall. The publishing layer is the easy part. The hard part is a tier-two supplier who has never been asked for recycled-content data and has no obligation to produce it.

Keep it short enough that procurement will actually use it, and specific enough to be enforceable.

• The field list, referenced as an annex you can update without reopening the contract.
• Format and transport — a named schema and channel, not "on request".
• An attestation: a named signatory confirming accuracy, which is what your own sign-off ultimately rests on.
• An update obligation with a response window when a specification, formulation, or source changes.
• Flow-down: the supplier must obtain the same commitments from their own suppliers.
• Audit rights, scoped narrowly enough to survive negotiation.

Sequence by renewal date, not by strategic importance. Pull the renewal calendar, rank suppliers by the number of passport-relevant fields they own, and instruct procurement to attach the clause to every renewal from the next cycle onward. For long-dated contracts with critical fields, negotiate a side letter rather than a full amendment.

One quiet detail: the annex approach means each new delegated act adds fields to a list, not clauses to a contract.

Treat refusal as sourcing information. A supplier who will not attest to material data today is a supplier whose data you will be defending to a market surveillance authority later. Price the risk, dual-source the part, or accept it consciously and record the decision — the record is what protects the individual who signs.