Quick summary: Understand EUDR compliance requirements, 2026–2027 application dates, supplier data, plot geolocation, risk assessment and declarations—and how digital traceability can support your workflow.
EUDR compliance means meeting the obligations that apply to relevant products under the European Union Deforestation Regulation (Regulation (EU) 2023/1115), as amended. In-scope products must meet the deforestation-free and legal-production conditions, and the responsible supply-chain actor must follow the due diligence or declaration route that applies to its role.
For businesses sourcing or trading cattle, cocoa, coffee, oil palm, rubber, soya and wood, compliance is not simply collecting certificates or submitting a form. Teams need reliable information about products and production locations, evidence that can be checked, and a process for addressing risks. The exact obligations depend on the product’s Annex I classification, the company’s role and size, and the applicable dates and transitional rules.
The European Commission’s current overview identifies different application dates by business category. Do not treat the date as universal: certain micro and small operators already covered by the EU Timber Regulation have the earlier date, and products newly added to scope by the 2026 delegated regulation have a separate later timeline.
| Category / product situation | Application date |
|---|---|
| Large and medium operators | 30 December 2026 |
| Most micro and small operators | 30 June 2027 |
| Micro and small operators already covered by the EU Timber Regulation (EUTR) | 30 December 2026 |
| Products newly added to EUDR scope by Commission Delegated Regulation (EU) 2026/2102 | 30 December 2027, according to the European Commission |
These dates should be checked against the current official EUDR page and the precise product and company category. A transitional period or a later application date does not automatically remove the need to maintain evidence, map product flows or prepare for obligations that will apply later.
Discover how to use the available preparation time to strengthen supplier data collection, validate geolocation, and close compliance gaps before the applicable deadlines.
Start with Annex I of the Regulation and the applicable amendments. Product codes, the commodity actually used and product composition can determine whether an item is in scope. Where a code is prefixed by “ex”, only the described portion of that code may be covered. Record the rationale for each scope decision and review it when product specifications or legislation change.
Next, identify the legal entity and its role in the supply chain. Operator, downstream operator, trader and eligible micro or small primary operator routes may carry different requirements following the amendments. Avoid assuming that every company must submit a new DDS for every transaction.
Learn which commodities and product categories are in scope, understand the role of HS/CN codes, and identify whether your products may be subject to EUDR requirements.
Read our EUDR Scope Guide to clarify your obligations and take the right steps toward compliance.
Article 9 sets out information requirements for due diligence. Depending on the product and applicable rules, records can include product description and quantity, country of production, supplier and buyer details, production-period information, geolocation of relevant plots and evidence of legal production. Build a standard data-collection process with clear owners, mandatory fields and a method for resolving missing or inconsistent information.
Geolocation links the commodity to its production location and supports checks against the deforestation-free requirement. Validate coordinates and polygon files, retain stable plot identifiers and connect the plots to suppliers, procurement lots, processing batches, products and shipments. If material from several origins is combined, preserve the source-level records needed to assess each relevant input and explain the resulting product’s traceability.
Risk assessment should consider the collected information alongside relevant contextual evidence, including the sourcing country and region, supply-chain complexity, possible mixing with unknown-origin material and credible indications of non-compliance. Certification and third-party reports may support an assessment but should not be treated as an automatic substitute for the checks required from the responsible business.
Learn how to evaluate supplier data, verify plot-level geolocation, identify potential risks, and implement appropriate mitigation measures.
Where the applicable due diligence process identifies more than negligible risk, the responsible operator must take appropriate mitigation measures and reassess the risk before proceeding. Keep a record of evidence reviewed, gaps identified, actions taken, decisions made and the rationale behind those decisions. A defensible record explains not only the conclusion but how the business reached it.
Where a DDS or simplified declaration is required, prepare it through the EU Information System in accordance with the route that applies to the responsible actor. Capture the relevant reference or identifier and link it to the product and transaction records. A reference number alone does not prove that the underlying information is accurate or that all applicable obligations have been fulfilled. Confirm the current record-retention and handover duties for each role.
Learn which records to maintain, how to organise supplier data and due diligence evidence, and how to ensure documents are accessible when required.
EUDR implementation has changed through amendments and supporting measures. Compliance teams should track both the overall application timeline and the more detailed changes to roles, declarations and Annex I product scope. The three TraceX articles below cover different parts of this picture and can be used together as a focused regulatory-update reading path.
For a practical reading order, start with the delay article for the timeline, read the simplification article for changes to responsibilities, check the delegated-act article for product scope, and then use the transitional-period article to evaluate inventory and evidence scenarios. Revisit the official European Commission guidance whenever a legal interpretation or product-scope decision affects a shipment.
Suppliers may provide inconsistent identifiers, incomplete documents or data in different formats. Define required fields and resolve gaps before declaration preparation.
Coordinates may be missing, incorrectly formatted or linked to the wrong plot. Validate geospatial files early and preserve their connection to the relevant supplier and product.
Purchase orders, processing batches, invoices and shipment references may live in separate systems. Use consistent identifiers to connect them and retrieve evidence quickly.
Spreadsheets and email can make version control, exception handling and audit trails difficult. Standardised workflows can reduce re-entry and reveal missing data earlier.
Supplier onboarding, document review, risk assessment and declaration preparation may involve different teams. Assign responsibility for collection, validation, approval and maintenance.
Discover practical strategies to overcome these challenges, strengthen supply-chain transparency, and prepare your business for compliance.
Read our EUDR Compliance Challenges Guide to identify potential gaps and build a more reliable compliance process.
An EUDR gap analysis helps businesses identify what is missing from their current compliance processes. Assess supplier data, plot-level geolocation, legality documents, risk assessments and due diligence records to prioritise gaps and develop a clear action plan before placing relevant products on the EU market.
Preparing for EUDR enforcement means ensuring your business can demonstrate compliance through accurate, accessible and verifiable evidence. Establish clear responsibilities, maintain complete documentation, address identified risks and ensure your team can respond effectively to requests from competent authorities.
Failure to comply with EUDR requirements can result in penalties and other enforcement measures under the regulation and applicable national rules. Understanding potential consequences, including fines and restrictions on relevant products, can help businesses prioritise compliance controls, address gaps early and strengthen their due diligence processes.
Learn about potential penalties, enforcement measures, and practical steps to strengthen your EUDR compliance.
Read our guide to understand the risks and prepare your supply chain for regulatory scrutiny.

Digital compliance software can connect supplier onboarding, geolocation, traceability, evidence management, risk workflows and declaration preparation. When appropriately integrated with procurement or ERP systems, it can reduce duplicate data entry and help teams identify missing information earlier. Evaluate solutions against your actual workflow: bulk supplier onboarding, polygon validation, source-to-shipment traceability, exception management, audit trails, role-specific workflows and supported EU Information System functions.
TraceX helps businesses organise supplier and plot information, connect traceability records and support EUDR due diligence workflows. In a product evaluation, ask to walk through a representative product and shipment from supplier-data collection and geolocation validation to risk review, declaration preparation and evidence retrieval. Confirm the integrations and submission functions available for your configuration. Software can support the process, but it does not guarantee compliance or replace the responsible organisation’s obligations.
Ask for a live demonstration that connects the shipment to its product, batch, supplier and relevant plots, including how mixed-origin inputs and missing links are handled.
Check supported formats, polygon validation rules, duplicate detection, exception handling and the process for reviewing alerts. Ask how the platform records the evidence and outcome of each review.
Review available integrations, data ownership, import/export formats, permissions and how the platform avoids duplicate records. Confirm what is supported today rather than assuming every integration or submission step is included.
Test whether the team can retrieve supplier documents, geolocation, risk decisions, mitigation records and declaration references for a selected batch without manually reconstructing the file from multiple systems.
No. Software can support data quality, traceability and workflow control. The organisation remains responsible for confirming which legal requirements apply and for ensuring that the information and decisions are accurate.
Reliable EUDR compliance depends on connected data, documented decisions and clear ownership from supplier onboarding to shipment-level evidence. The revised timeline creates preparation time, but the practical work remains: confirm product scope, understand role-specific responsibilities, validate geolocation and legality records, and make evidence retrievable. A digital platform can help coordinate these tasks and improve consistency while the organisation remains accountable for the obligations that apply to it.
No. Use the available time to confirm product scope, collect supplier and plot data, resolve gaps and test workflows. Supplier onboarding and geospatial validation can take time, and later changes may require updates to product and evidence records.
No. DDS reference number is not enough, a reference is one part of the record. The underlying information, applicable due diligence, risk decisions and supporting evidence must also be accurate and retrievable.
No. EUDR scope depends on the relevant products listed in Annex I and the precise commodity and product code. Review the current legal text, including amendments and “ex” code descriptions, rather than relying only on a commercial product name.
No, the obligations depend on the actor’s role, size and circumstances under the amended rules. Confirm whether the applicable route requires a DDS, a simplified declaration, registration, record retention or passing on reference information.
Spreadsheets may support simple tracking, but complex supplier networks, polygon files, changing product scope and shipment-level traceability can make validation, version control and audit retrieval harder. Evaluate software based on scale, complexity and integration needs.
Do not assume that the warehouse or purchase date alone settles the question. Review the applicable transitional rules and maintain evidence of when the relevant product was placed on the EU market, its production and source records, and any downstream processing or mixing. Apply the rule to the actual facts and product category.