Choose a representative product revision and one missing information item. Ask the supplier for the value, unit, supporting source and the product scope that source covers. Use the example, editable cover message and workbook below to record the response and a separate review decision.
What happens if my supplier won’t provide DPP data?
Answer checked:
Supplier refusal does not remove a mandatory requirement or make an unsupported value acceptable. Establish which information is legally required for the product, which is a buyer request and which is recommended preparation. If required information is missing, the responsible operator must resolve the gap before the applicable market-placement conditions can be met.
ESPR Article 38 supply-chain duties apply when specified by the relevant delegated act; it is not an unconditional right to every supplier’s data today. Battery Article 39 separately requires cell and module suppliers supplying battery manufacturers to provide the information and documentation necessary for compliance, free of charge.
Send a bounded request identifying the product and revision, item, purpose, evidence needed and appropriate access arrangements. Check whether the information already exists internally or can be obtained from another legitimate source. Record refusal, uncertainty or conflicting evidence rather than inventing a value.
Escalate through procurement and the responsible compliance owner. Consider confidential access, a narrower request, evidence testing or a different supplier where appropriate. For an importer, missing required passport information or unresolved nonconformity can prevent placement under Article 29; obtain product-specific advice before proceeding. A questionnaire or AI-generated answer is not a legal substitute.
Source: ESPR — Regulation (EU) 2024/1781 — Articles 2, 4, 9–13 and 27–38; current displayed consolidation. As checked 22 September 2026.
Source: Battery Regulation — current consolidated text — Consolidation 13 August 2026; Articles 1, 3, 13, 39, 77–78 and Annex XIII. As checked 22 September 2026.
Why supplier information becomes a DPP blocker
For organisations placing products on the EU market, this work is becoming more pressing. Regulation (EU) 2024/1781, the Ecodesign for Sustainable Products Regulation (ESPR), establishes the Digital Product Passport as a product-information mechanism. Product-specific measures will determine much of the detailed information required by category. Regulation (EU) 2023/1542 provides the clearest current source-grounded basis for specified battery-passport preparation. For textiles, apparel and electronics, teams should prepare structured data and evidence collection while recognising that product-specific requirements continue to develop. That direction is not a claim that a final, universal passport schema already applies.
Most supply chains were not designed around product-level evidence retrieval. Information sits with tier-one factories, material mills, component makers, laboratories, agents and internal buying teams. The same product attribute may appear differently in a technical data sheet, bill of materials, test report and supplier questionnaire. Changes to colourways, material substitutions or production sites can make an otherwise accurate record obsolete.
The problem is not always supplier reluctance. Suppliers are frequently asked for broadly phrased sustainability data without a clear product scope, evidence standard or deadline. They may respond with a corporate policy when the buyer needs a batch-specific certificate, or with an unsupported percentage when the relevant calculation method has not been agreed.
A supplier declaration, an AI-generated data suggestion or a QR code attached to a product does not, by itself, demonstrate regulatory compliance. The practical objective is more disciplined: create an accountable record of what is known, what is evidenced, what is missing and who owns the next action. This is general guidance, not legal advice or a finding that a SKU is in scope.
This guide is for preparing and reviewing requests through your existing controlled channels. It is not a supplier portal, network, document-verification service or method of deciding whether a passport is required.
Supplier request example: ask for one reviewable answer
Fictional operational example. Adapt the request to the actual product, contract and applicable rules; this wording does not create a supplier disclosure duty. The page does not send a message.
Subject: TR-100 revision B — material composition evidence request
We are reviewing the material-composition record for TR-100 revision B. Please confirm the declared composition and units for that revision, and identify the source record, issuer, issue date and revision that support your answer. Our current declaration DEC-14 identifies revision A, so we cannot yet apply it to revision B.
Please state any calculation method, product boundary, estimate or limitation. If the evidence is unavailable, identify what is missing and the next contact or action. Please reply by the agreed date through our approved channel; agree a restricted route before sharing confidential information.
Internal handoff: procurement owns the response; the assigned technical reviewer decides whether it supports revision B. Record Requested, Received and Reviewed as different events. An unsupported answer stays unresolved.
Separate legal duties from operational requests
Under ESPR Article 9(2), the applicable product-specific measure determines passport information and arrangements. Article 38 supply-chain information, access and verification duties apply only when specified in the delegated act. Check its trigger, recipients and scope; this template is not universally required. For covered products, manufacturer duties under Article 27 and importer checks under Article 29 remain distinct from collecting supplier responses.
A separate battery provision exists: Article 39 of Regulation (EU) 2023/1542 requires suppliers of battery cells and modules, when supplying manufacturers, to provide free of charge the information and documentation necessary for compliance with the Regulation. That does not prescribe one questionnaire. Article 77(4) places passport accuracy, completeness and updating responsibility on the economic operator placing the battery on the market; another operator may act on its behalf under written authorisation.
Use the classifications below to explain each request. A row can reference more than one relevant category, but the legal basis and your operational method must remain distinguishable.
| Classification | What it establishes | Request boundary |
|---|---|---|
| Legal requirement | An identified provision imposes a duty within its conditions. | Cite the article, relevant actors and applicable scope; do not invent a field. |
| Economic-operator responsibility | A particular actor has a duty for the product or information. | A request for upstream support does not automatically transfer that responsibility. |
| Product-specific requirement | The applicable measure or regime specifies relevant information. | Record the product, version and conditions; do not generalise to every product. |
| Contractual / procurement practice | The parties agree how information will be exchanged. | Identify the agreed specification or process; a contract term is not EU law. |
| Recommended preparation | A suggested action helps locate and organise information. | Explain why it helps; internal job titles and this workflow are recommendations. |
| Evidence / governance practice | A control supports provenance, review and accountability. | Document the review method; receiving a certificate alone does not validate a claim. |
Build a supplier data request
Start with one information item. Identify its purpose and holder, then record the response and the evidence separately. Add only the fields useful for that item. This is an operational worksheet; it does not decide legal duties or verify supplier claims.
Private page memory: entries disappear on reload or close. No supplier or company name, email, contact detail or real product identifier is required. Use non-sensitive references and role names. Row values and notes are not sent to acquisition measurement. There is no submission to a supplier.
Source review required. Check current product rules before relying on legal classifications. The worksheet remains an operational planning tool.
One blank row. Add only the information you need.
For a classified brief, give each used row an item, a purpose, a dependency and a request state. Unknown dependency and Needs review are valid planning choices. Other details are optional; missing review evidence remains visible in the summary.
| Request and purpose | Values and scope | Evidence and verification | Ownership and state |
|---|---|---|---|
Request and purposeRequest item 1 Purpose and source details | Values and scopeProduct / component scope | Evidence and verificationSource and verification details | Ownership and stateDates, changes and notes |
Your request and evidence follow-up
Items to request or chase 0
Received but not verified 0
Missing evidence 0
Conflicts to resolve 0
Internal follow-up 0
Review dates and changes 0
Counts describe the rows and choices you entered, not compliance or readiness. One item may appear in several categories. A document received is not a verified value. “Verified” records your stated review; this tool cannot inspect the source or establish that a legal evidence requirement is satisfied.
Reusable request / review outline
Copy this local outline into your controlled request process. Check scope, recipients, access rights and confidentiality before sharing it.
Next steps
Keep supplier follow-up with the product record
In a DPPLogic workspace, record product facts with their sources, link evidence references and keep human review decisions together. The Free plan covers up to 5 products. Your choices and results on this page are not transferred; start the product record in the workspace.
Download a reusable supplier request workbook
Keep a local request and evidence log after you close the browser. The workbook provides 12 blank request references, matching evidence rows, the same status choices as the online tool, and a fictional completed review. Edit only the items relevant to your product and purpose.
Keep the request reference in both logs. Record Unknown or Uncertain / disputed where appropriate. “Verified” records your review against stated scope; neither the file nor the online tool inspects evidence or establishes legal compliance. CSV files contain values and headings only; they do not retain Excel dropdowns or formatting.
These are separate local files, with no import, supplier-submission or automatic verification function. Before sharing them, confirm the recipient, confidentiality and approved transfer route. Do not put restricted records in a public link. The fictional example is for learning and must not be used as product evidence.
Field names and choices checked 23 September 2026. The downloads add an operational record, not a universal legal questionnaire or a new legal review. Return to the online request tool or review the data and evidence checklist.
When supplier input is actually needed
Check controlled internal sources first. Reuse the generic checklist’s dependency labels: they describe input needed for preparation, not supplier identities or legal liability.
Internal
The information is mainly held within your organisation. Assign an internal owner instead of sending an unnecessary external request.
Supplier
Relevant upstream input is needed. State what is missing and why that source can support the request.
Mixed
Internal records and upstream input must be reconciled. Define which party supplies each part; supplier involvement alone does not prove a gap.
Unknown
The holder or dependency is unresolved. Investigate scope and sources before claiming that a supplier has failed to respond.
Choose request categories for the identified gap
These are possible categories, not a mandatory list. Select an item for an identified legal purpose or explicit preparation need. Ask for the relevant scope and access route; internal review does not grant publication rights.
| Possible category | Define the request before sending |
|---|---|
| Product identification | Which model, batch, component or version does the response describe? |
| Materials / composition | Which attribute, material boundary, value and source declaration are relevant? |
| Components / substances | Which component and substance information is needed under the applicable rule? |
| Manufacturing information | Which process or facility fact is necessary, and who can substantiate it? |
| Environmental attributes | Which metric, method, boundary and period support the stated value? |
| Performance / testing | Which test condition, sample, product revision and result are relevant? |
| Certificates / declarations | What does the document cover, and what does it leave unverified? |
| Repair / service | Which applicable product instructions and revision are required for the task? |
| Recycled content | What material, calculation boundary, method and evidence support the claim? |
| End of life / recyclability | Which treatment or recovery information applies to this product? |
| Source / provenance | Where did the value originate and how can its source be reviewed? |
| Change / version information | What changed, when did it become effective, and which records are affected? |
A value, a document and evidence are different
Data value
The information to be used: for example a material description or measured quantity, with its unit and product boundary.
Document
The file, report or declaration containing information. One document may contain several values and may cover a different product version.
Evidence
Support for the particular value or assertion. Check method, scope, relevance and limitations rather than treating the file’s existence as verification.
Source
The origin of the information: a controlled system, test, calculation or upstream statement. Preserve the original reference and revision.
Internal owner
The person or function accountable internally for reviewing and maintaining the record. This suggested assignment does not replace the legally responsible operator.
A ten-step supplier-data workflow
This recommended sequence is not a statutory process. Use only the template columns relevant to the request; agreed scope should make a complete response recognisable.
| Step | Practical action | Record to keep |
|---|---|---|
| 1. Identify data / evidence | Start from an applicable requirement or a clearly labelled preparation gap. | The item, purpose, source locator and unresolved scope. |
| 2. Identify the holder | Check internal systems and upstream records before assuming the supplier holds it. | Likely source and the owner of the investigation. |
| 3. Decide the dependency | Classify Internal, Supplier, Mixed or Unknown; divide mixed work into clear responsibilities. | Which input is requested and which work stays internal. |
| 4. Prepare and send | Specify the item, product boundary, format, unit and evidence expectation through an approved channel. | The request revision and an agreed response date where useful. |
| 5. Receive the response | Preserve the response and its attachments in your controlled process. | What arrived, when, and which request it answers. |
| 6. Validate the information | Check format, completeness, identifiers, units and coverage against the request. | Missing fields, interpretation questions and validation findings. |
| 7. Review the evidence | Check that the support actually relates to the value, method, version and claim. | The reviewer’s assessment and any limits or assumptions. |
| 8. Resolve exceptions | Raise missing or conflicting items; keep both original records while investigating. | The issue, follow-up action and unresolved decision. |
| 9. Approve and assign | Record the internal review decision and who maintains the accepted record. | Approval scope, accountable function and remaining restrictions. |
| 10. Set the next review | Choose a review date and change triggers appropriate to the item. | Next review, effective version and conditions requiring earlier attention. |
Track operational progress without a compliance score
A received response can still be incomplete, conflicting or unsupported. These states describe the work item. They do not establish legal compliance, and the template does not independently inspect your evidence.
| State | Meaning and next action |
|---|---|
| Not requested | The request has not been sent; confirm scope and the information holder. |
| Requested | The request is outstanding; follow the agreed response process. |
| Received | A response arrived; content and evidence still need review. |
| Incomplete | The response does not cover the defined request; identify the missing part. |
| Conflicting | Records disagree; investigate the cause before approving a value. |
| Evidence missing | The value lacks the support needed for the identified review. |
| Verified | You have marked the item reviewed against your criteria; this is not DPPLogic verification or certification. |
| Not applicable | The request item does not apply to the stated context; retain the reason. Unknown scope belongs in Needs review. |
| Needs review | Scope, evidence, ownership or another question remains unresolved. |
Validate the response, then assess its evidence
Check that the response answers your request. Confirm product/component, method, dates and units. A plausible number concerning another model, revision or reporting period is not enough.
Evidence type is not a quality ranking. Declarations, test reports and certificates have limits; calculated or estimated values need their inputs, method and uncertainty reviewed.
A reply can arrive without supporting the product you asked about. Follow the fictional wrong-revision review before recording your decision.
| Evidence description | Review question |
|---|---|
| Primary / direct | What was directly recorded, by whom, and within what scope? |
| Supplier declaration | Which statement is made, for which product/version, with what support? |
| Test report | Do sample, method, conditions and laboratory scope match the claim? |
| Certificate | What activity/product and dates are covered, and what is excluded? |
| Calculated | Are method, assumptions, input sources and calculation version recorded? |
| Estimated | Why was estimation used, what uncertainty remains, and is it acceptable for the purpose? |
| Unverified | Which review has not yet been completed? |
| Unknown | What information is needed to identify or assess the evidence? |
Worked example: received does not mean accepted
Fictional case. The supplier replies with the original revision-A declaration and a message saying the product is unchanged. Record the reply, retain the source reference and ask what substantiates its applicability to revision B. Do not mark the gap closed simply because a file arrived.
If an authorised revision-B statement and its supporting record resolve the scope question, the named reviewer can record acceptance for that stated purpose. If they do not, keep the gap open with an owner and next action. A later material change triggers another review.
Handle missing and conflicting information explicitly
Do not automatically treat either the supplier or the internal system as legally authoritative. Escalate unresolved issues through your normal quality, procurement or compliance process; this template does not adjudicate them.
| Example issue | Recommended action |
|---|---|
| Supplier value differs from an internal record | Compare product/version, measurement boundary and effective date. Preserve both records; ask their owners to reconcile the difference. |
| Two responses use incompatible units | Establish units and basis before conversion. Preserve original values and the conversion method; do not silently replace them. |
| Certificate dates do not match the product revision | Confirm coverage with the document owner. Keep the item under review until the current revision is covered. |
| A claim has no supporting evidence | Ask what substantiates the exact claim. Record evidence missing; a confident declaration is not independent verification. |
| One component has different identifiers | Check identity/version mapping before merging. Keep aliases and the basis for deciding they describe one component. |
Normalise records without losing their meaning
Agree definitions before formats. Consistent formatting cannot resolve different product boundaries or measurement methods. Retain original values alongside transformations so a reviewer can reconstruct the change.
- Units: specify the dimension, basis and conversion rule; do not confuse mass fraction with a total mass.
- Dates and formats: distinguish effective, issue, receipt, expiry and review dates; use an unambiguous date representation.
- Identifiers and versions: preserve the source identifier and revision, then record any controlled cross-reference.
- Language and naming: agree terms for components, materials and organisations; confirm translations that could change technical meaning.
- Duplicate records: investigate overlapping scope and provenance before merging; matching names alone do not prove identity.
- Standards: check the relevant edition and applicable requirement. A convenient internal format is not automatically a mandated standard.
Set review dates and meaningful change triggers
Data can become stale after a product, source, method or legal change. Record effective date, source version, last review and next review where useful. Document expiry and internal review dates differ; not every record expires.
Reopen affected items when a component or supplier specification changes, evidence is withdrawn, a conflict emerges or the applicable information requirement changes. Assign the follow-up and preserve the previous version. The suggested review interval is operational; this guide does not prescribe a universal legal refresh period.
Battery example: request evidence for a chemistry description
For an in-scope battery model, chemistry is mapped through Annex XIII 1(a), Annex VI Part A(7), and public composition information in Annex XIII 1(b). Confirm battery scope and profile conditions before using this example.
An operational request could ask the upstream holder to confirm the chemistry against a released specification, identify its revision and name the model covered. Compare the response with the controlled internal description and review its supporting specification or declaration. These request details are suggested preparation, not additional statutory questionnaire fields.
Detailed cathode, anode or electrolyte composition falls within the separate Annex XIII 2(a) access category. Do not publish it by default. Check recipients and access rights; the full matrix and operator-responsibility explanation remain on the existing battery page.
Make the workflow useful across internal teams
These are suggested contributions, not mandated job titles. Functions may overlap; keep request ownership and approval clear.
| Function | Useful contribution |
|---|---|
| Procurement | Agree scope, request channel and follow-up. |
| Product | Define the model/component boundary and revision. |
| Compliance | Check applicable instrument, actor, conditions and access. |
| Quality | Review completeness, conflicts and corrective actions. |
| Sustainability | Review environmental methods, boundaries and evidence. |
| Supplier management | Track request ownership, responses and unresolved dependencies. |
| Engineering | Check definitions, units, test conditions and product correspondence. |
Use the response to close the right preparation gap
Return to the generic checklist for the relevant data/evidence item. Supplier needed starts a request; it does not prove an upstream legal duty. Received and Verified remain distinct operational states, without changing applicable product rules.
Use the battery checklist for product-specific detail and the readiness assessment for wider ownership, supplier, evidence, traceability or systems gaps. Define the work before comparing software.
A practical preparation walkthrough
Follow the request and response examples on this page, then record the unresolved evidence and next action.
Follow a supplier evidence gap to a review decision
Follow the request and response examples on this page, then record the unresolved evidence and next action.
Primary and authoritative sources
Source links are provided for verification. Scope, consolidated versions and later measures should be checked again before implementation or reliance.
Regulatory disclaimer. This content provides general diagnostic and preparation information. It is not legal advice, certification or regulatory approval. Requirements may differ by product category, jurisdiction, market and supply-chain role and may change over time.