kolum
Log in
The Imports upload template changed on September 4, 2026. Older versions of the template are no longer accepted, please download the new one:Download the new Imports template
EUDR · Introduction to EUDR

The compliance flow, end-to-end

Overview

This page shows how the pieces fit together. Each step below is a section in this documentation, so you can use this page as a map. The order shown is the order you work in.

The journey

1. Set up master data. Before anything else, your foundational records exist in kolum.

  • Companies: the legal entities that import or trade.
  • Articles: your products, each with a CN code that determines whether it is EUDR-relevant.
  • Suppliers: your suppliers and buyers.

2. Raise a purchase order. Before an import, you create a purchase order and add the EUDR-relevant articles to it, together with the volume you intend to bring in. This is what triggers the need for an assessment.

3. Assess the risk. For each relevant supplier and article pair, you run a three-step assessment.

  • Collect due diligence data. Request the required information from the supplier, including the geolocation of the plots of land.
  • Conduct the assessment. Analyse the data against the risk criteria. The initial risk is driven by the country of production and the data sources kolum draws on.
  • Submit to TRACES. Once every criterion is at a negligible or low level, submit the statement to the EU system.

4. Mitigate where needed. If any criterion is above the acceptable level, the product cannot yet be cleared. You lower the risk either by applying risk mitigation measures or by collecting further documents from the supplier, until all criteria are negligible or low.

5. Generate the Due Diligence Statement. When the assessment passes, submitting it to TRACES produces a Due Diligence Statement (DDS) reference number. In kolum this reference is tracked against the article, its suppliers, and the connected purchase orders.

Key rules to remember

  • A Due Diligence Statement can only be generated when every risk criterion is negligible or low. Until then, the product is blocked.
  • A DDS reference is valid for 365 days and can cover several purchase orders up to the declared volume. Once you reach that volume ceiling, you request fresh data and assess again.
  • Traders do not run this assessment. They collect Due Diligence Statement references from upstream and pass them on. This is documented separately.

A worked example

To see how the steps connect, follow a single article through the flow.

  • Master data. You add the article Raw Cocoa Butter with its CN code. Because the code is in Annex I, the article is EUDR-relevant. You also add its producer as a supplier.
  • Purchase order. You raise a purchase order for 20 tonnes of the cocoa butter from that producer. This creates a supplier and article pair that needs an assessment.
  • Collect data. You request due diligence data from the supplier, who returns the geolocation of the plots and supporting evidence.
  • Assess. The country of production sets an initial risk. One criterion comes back as medium, so the product is blocked.
  • Mitigate. You apply a mitigation measure and request one further document. The criterion drops to low.
  • Submit. With every criterion now negligible or low, you submit to TRACES and receive a Due Diligence Statement reference, valid for 365 days, that covers this purchase order and any further orders of the same article up to the declared volume.

The flow at a glance

ℹ️ This overview describes how kolum operationalises the due diligence obligation set out in the consolidated EUDR. Each step is expanded, with screenshots and every workflow, in the EU Companies section.