Why supplier declarations do not complete the evidence trail

A declaration is a starting point

A supplier may sign a statement that its products are “EUDR compliant”. That is an assertion by a particular organisation, on a particular date, with a scope that needs to be understood. It can be useful evidence of what the supplier represents. It is not, by itself, the complete due-diligence record.

Articles 9 and 10 of the EUDR require information and an assessment of risk. The importer needs to examine the substance, reliability and relationship of the evidence to the relevant product, rather than relying only on the presence of a signed document.

Read the scope before the signature

Ask which legal entity issued the declaration, which products it covers, which production periods and origins it refers to, and whether exclusions are hidden in the wording. A group-level sustainability statement may not cover the subsidiary or factory supplying your order.

Expressions such as “to the best of our knowledge” and references to a supplier code of conduct should be recorded accurately. Do not silently convert conditional language into an unconditional conclusion in your evidence register.

Separate three layers

Layer	Example	Purpose
Assertion	Signed statement about a defined supply period	Records what the supplier claims
Underlying evidence	Production locations, sourcing records, applicable legality evidence	Supports or challenges the claim
Relationship	Input-lot and manufacturing-batch reconciliation	Connects that evidence to the goods being assessed

Missing the third layer is a common operational weakness. A collection of credible documents can still lack a credible connection to the particular product.

Read four boundaries before extending a declaration

Boundary	Question	Typical overreach
Product	Which family, output or material is described?	“All products” treated as batch-specific
Time	Which factual production period is covered?	Receipt date mistaken for coverage
Source	Who asserts this, based on which records?	Distributor signature treated as direct factory-origin evidence
Relationship	How does it connect inputs and plots to these goods?	Plot attachment treated as shipment lineage

Keep assertion, source record and conclusion distinct

The assertion is what the supplier says. The underlying records explain its basis. The review conclusion belongs to the responsible reviewer and must identify the assessed flow, exact versions and limitations. A summary such as “supplier compliant” can lose the supplier’s conditions and invent a broader conclusion.

A factory invoice supports a commercial link. A material specification supports composition. An allocation record can support an input/output relationship. A plot file supports location information. Do not assign a document to a relationship it does not establish.

Fictional operating example / not a customer case study

Declaration D-01 says the factory participates in a traceability programme. INV-EX41 identifies tyres and PS-07 lists plots. Without output B-A17 → rubber inputs → PS-07, the correct status is “received; product-origin relationship unresolved”. No positive risk conclusion follows from file count.

Certificates contribute information, not a blanket outcome

Article 10(2)(n) permits complementary information from relevant certification or third-party verified schemes within risk assessment. Ask what was assessed, by whom, for which products, period and origin set. It does not create a general EUDR exemption or transfer the operator’s responsibility.

A scheme can provide useful records while leaving your output-to-input linkage unresolved. A broader supplier programme and a narrower shipment decision may require different supporting evidence. Preserve both the certificate’s scope and the reviewer’s explanation of its use.

Turn a broad reply into a precise next action

Request the allocation connecting B-A17 to relevant lots, then the map relating those lots to the asserted plot set for the covered period. Name an evidence owner and acceptance criteria. “Please ensure compliance” gives the supplier no specific record to supply.

For repeat orders, inspect sourcing changes rather than extending a yearly declaration indefinitely. A new batch, processor or plot version may alter coverage even when commercial names remain the same. Record those dependencies in the ledger.

Try a retrieval test

Give someone an import reference and the evidence pack. Can they identify goods, output, relevant inputs, origin set, versions and reasoning without the preparer’s memory? A declaration sitting in a folder is not an answer to all six questions. The diagnostic turns missing relationships into bounded owner/action requests.