EUDR Readiness: Connect Supplier Evidence to Due Diligence Statements

Follow one product lot from supplier documents to the decision and EU reference

Published

Cream, lavender, and orange paper-cut illustration connecting coffee origins, an evidence-review dossier, and an EU reference document, with the FormKiQ wordmark

A coffee importer has a supplier certificate, a shipment record, and a file of farm locations. Can the team show which farms supplied one lot, which evidence was reviewed, and which due diligence statement covers it? A connected dossier should answer those questions without rebuilding the history from email.

One lot, three connected records

  1. 1 · Collect

    Link the goods to origins

    Keep supplier records and the lot's source evidence.

  2. 2 · Review

    Resolve gaps and decide

    Keep the assessment, corrections, and approval.

  3. 3 · Connect

    Retain the EU reference

    Link the submitted or received record to that evidence.

Check the product and your role before choosing a deadline

Start with the product code and description in the current Annex I, your supply-chain role, and the relevant enterprise category. The Commission's current overview gives the main application dates:

30 December 2026

Large and medium-sized operators and traders. This date also applies to micro and small operators handling products already covered by the EU Timber Regulation.

30 June 2027

Eligible micro and small operators established as such by 31 December 2024, except for products already covered by the EU Timber Regulation. Confirm the applicable category and timber transition provisions.

Product changes have their own dates. Delegated Regulation 2026/2102 amends Annex I, removing some products and adding others. Newly added entries such as coffee extracts apply from 30 December 2027. That is not a general postponement for coffee or every covered product. Record the classification and the rule version used.

Role check: a new statement, a declaration, or an upstream reference?

The amended regulation distinguishes operators, qualifying micro or small primary operators, downstream operators, and traders. Qualifying primary operators can use a simplified declaration regime; downstream operators and traders have traceability and other obligations rather than a blanket requirement to submit a fresh statement for every transaction. Confirm the route before configuring the workflow. The importer example below follows a due diligence statement route.

Follow the coffee lot through its evidence file

  1. 1. Connect the supplier evidence to this lot

    The work

    Link the product, quantity, supplier, production period, country, and relevant plots to the shipment. Identify all contributing origins when material is combined. Check that documents and location data describe the same goods.

    Keep in the dossier

    Original submissions, lot and supplier references, plot identifiers, source dates, and the versions actually reviewed.

    A missing plot reference becomes an assigned request for correction. It should remain visible when procurement checks whether the lot is ready to advance.

  2. 2. Resolve gaps and record the decision

    The work

    Review the evidence under the applicable due diligence route. Record the country-risk classification, checks performed, findings, and any mitigation. Route inconsistent origins or missing legality evidence back for correction.

    Keep in the dossier

    The evidence considered, assessment version, open issues, mitigation results, reviewer, decision, and approval time.

    For the statement route, the regulation requires the operator to have found no or only negligible risk. A certificate or an internal approval label cannot replace the required due diligence.

  3. 3. Connect the EU record to the approved evidence

    The work

    For this importer, prepare the statement from the accepted data and check authorisation before submitting. Retain the EU result and reference. Check an uncertain submission outcome before retrying to avoid unintended duplicates.

    Keep in the dossier

    The submitted data, reference number, response and status, submission time, and links to the exact evidence and decision versions.

    A submission response does not establish that the evidence is correct. If the supplier later changes a plot or origin, reopen review and follow the permitted EU update or correction process while preserving the earlier record.

Keep these implementation details available

Information System access and integration

The Commission's Information System guide provides registration, training, and access to the relevant environments. Use current technical documentation for an automated connection. Define ownership of credentials, submission authority, validation errors, status checks, retries, and corrections. A document repository and an EU submission integration perform different parts of the workflow.

Retention and later changes

Under the recordkeeping provisions, statement records and supporting evidence have five-year requirements with different starting events: submission for statements and placing on the market or export for Article 9 information. Map retention by record type and role, including other applicable obligations. Preserve earlier evidence, later corrections, and the reasons decisions changed.

Test one lot before scaling the workflow

  • Scope: can staff explain the product classification, role, and applicable date?
  • Evidence: can they trace the lot to its suppliers, origins, and reviewed files?
  • Decision: are missing evidence and unresolved risk visible before release?
  • History: can they retrieve the EU reference and the exact records behind it?

Keep the lot and its decision history connected

A useful EUDR dossier connects the product lot and its origins to the evidence reviewed, the decision made, and the relevant EU record. Confirm the applicable product scope and role, resolve gaps before release, and preserve earlier versions when suppliers or submissions change.

    Start with FormKiQ Core

    The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

    Get Started Free

    Deploy FormKiQ Essentials or Advanced

    Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

    Explore Options

    Plan an Enterprise Rollout

    For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

    Book a Call