Businesses should already be focusing on implementation today, as a lack of preparedness may in practice result in imports being stopped, products being unable to be placed on the market, or the need to change suppliers at the last minute.
The greatest challenge is not reading the regulation itself or technically submitting a due diligence statement (DDS), but obtaining data, linking it to a specific product and batch, and documenting why the risk of non-compliance has been assessed as non-existent or negligible.
Below, I discuss challenges that regularly arise in implementation projects, often only after the general legal analysis has been completed and the organisation begins dealing with the actual flow of data, documents and decisions.
The first mistake is creating a product list based solely on commercial descriptions or product composition. The scope of EUDR results from the combined assessment of the CN/HS code, the description of the relevant entry in Annex I of Regulation 2023/1115, and the commodity from which the product is made. The mere fact that a product contains wood, natural rubber or palm oil does not automatically mean it falls within the scope of EUDR. The European Commission provides examples of margarine containing palm oil and a vehicle fitted with tyres made from natural rubber. As a whole, these products are not subject to EUDR if their codes are not listed in Annex I. Likewise, the designation “ex” before a code means that the regulation applies only to part of the goods classified under that heading.
Multi-component products create an additional challenge. A chocolate bar containing cocoa and palm oil should not automatically be analysed by applying identical rules to every commodity. It is necessary to determine which commodity category Annex I associates with the relevant product code. In the case of furniture, it may also be necessary to identify several species and sources of wood used in a single product.
Implementation should therefore begin with a review of material master data and customs codes. For disputed classifications, it is advisable to document the rationale behind the classification, verify it with the customs team and, where commercially significant, consider obtaining a binding tariff information decision. An error in one direction may result in unnecessary costs and operational barriers; an error in the other may lead to importing or selling products without meeting the applicable requirements, incorrect customs declarations, penalties and customer claims.
In many companies, the term “country of origin” is used in practice to refer to the supplier’s country, the country of shipment or the place of last processing. For EUDR purposes, however, the key factor is the country where the commodity was produced, meaning the location where it was cultivated, harvested, raised, collected or extracted. Cocoa processed into powder in country A may originate from beans produced in country B. An invoice from a European intermediary therefore does not answer the question that EUDR requires companies to address.
This issue becomes especially apparent when purchasing from trading entities. A direct supplier often knows the mill, paper factory or processor, but may not know the plantation, forest or farm. Data remains scattered among brokers, cooperatives, aggregators, manufacturing facilities and logistics operators. At the same time, batches are merged, split and repackaged, while the company ERP system tracks SKU numbers and deliveries rather than production plots.
A practical data model should include at least: the product, the EUDR-regulated commodity, CN code, batch, quantity, country of production, supplier, production plots and evidence of legality. It must also demonstrate that products of known and compliant origin have not been mixed with commodities of unknown or non-compliant origin. The Commission confirms that a “mass balance” model is not permitted, and the inability to separate a non-compliant component may render the entire mixed batch non-compliant.
The requirement to provide geographical coordinates sounds relatively simple until it becomes apparent that a supplier may work with thousands of small farms, plot boundaries may not be digitised, and commodities from several harvests may be combined in a single silo. As a general rule, all plots on which a given commodity was produced must be identified. For plots larger than four hectares, a polygon is required, while a point may be used for smaller areas. Simplifications available to micro and small primary operators should not be automatically extended to importers sourcing products from them.
Receiving a GeoJSON file does not solve the issue. In practice, both technical and substantive errors frequently occur: reversed coordinates, points located in the sea, overlapping polygons, duplicates, or areas disproportionately large compared to the declared production volume. It may also happen that a supplier provides the current plantation boundary but lacks documents or reliable historical data enabling an assessment of land status after 31 December 2020.
Verification should include, at a minimum, technical validation of plot geometry, consistency checks against the relevant country and administrative area, comparison of plot size with production volume, duplicate detection and analysis of available historical sources. Satellite imagery may serve as important supporting evidence but should not replace a proper assessment. Cloud cover, seasonal cultivation patterns, wildfires, lawful logging, land cover changes or inaccurately mapped boundaries may all produce false positives. Ultimately, responsibility for the accuracy of geolocation data remains with the operator, even where the data originates from the producer, certifier or intermediary.
Suppliers’ reluctance is rarely caused solely by a lack of goodwill. Geolocation and producer data may reveal sourcing structures, intermediary margins or sources that constitute a competitive advantage. Suppliers may also be concerned about data protection risks, liability for errors or direct contact between the customer and their upstream suppliers. Outside the EU, the issue is even more visible because local producers are generally not directly subject to EUDR. An EU buyer therefore expects them to provide costly data needed to fulfil the buyer’s own obligations.
The solution should not be a single extensive questionnaire sent to all suppliers. It is better to divide requirements according to the product, the supplier’s role and the level of risk, define acceptable evidence in advance and provide a secure channel for sharing data. In practice, confidentiality agreements, access restrictions, the possibility of sharing information through a trusted third party, and a clear explanation of who will receive the information, for what purpose and to what extent it may be used are all helpful.
At the same time, the escalation point should be defined in advance. If an operator cannot obtain the information required to perform due diligence, it cannot replace that information with a “best efforts” declaration and still place the product on the market. In such a situation, the operator should suspend the supply, limit sourcing options or change suppliers. Postponing the decision until customs clearance transforms a compliance issue into a business continuity crisis.
More from this expert: Tax changes from 2027 - new PIT scale, higher CIT and limitations on lump-sum taxation
DDS is the outcome of a process, not the process itself. The risk assessment should demonstrate whether specific products comply with the requirements relating to deforestation-free production and legality in the country of production. It is not enough to verify that documents have been collected. Their reliability, consistency and accuracy must also be assessed, while taking into account factors such as corruption risks, supply chain complexity, the potential circumvention of requirements, batch mixing, information concerning land disputes and the rights of third parties.
A country’s classification as low risk may justify the application of simplified due diligence, but it does not remove the obligation to collect information or assess the risk of mixing or circumvention. Current country classifications are published by the European Commission. Similarly, certifications may support the assessment but do not replace it. The scope of the certification scheme, the inspection methodology, the identity of the certificate holder and the connection between the certificate and a specific batch should all be verified.
The most common weakness is a risk assessment based solely on a supplier declaration. Such a document may be accurate but still too general if it does not identify plots, production periods or evidence of legality. If a company then communicates to customers that its supply chain is “deforestation-free”, an additional risk of greenwashing arises. Therefore, every decision should leave a clear audit trail: what information was verified, what discrepancies were identified, who accepted the explanations, what mitigation measures were applied and why the risk was considered non-existent or negligible.
A standard clause stating that “the supplier complies with applicable law” will not ensure that data is provided or that responses are received within the required timeframe. The contract should clearly define the information required for EUDR purposes, its format, quality standards, submission deadlines and the method for linking data to a specific batch. It should also require these obligations to be passed on to earlier stages of the supply chain, the prior notification of source changes, cooperation in resolving discrepancies and the retention of supporting evidence.
Audit rights should also be regulated, including remote audits and audits conducted by independent experts, together with rules governing corrective action plans. Equally important as indemnification are operational mechanisms such as the right to suspend orders, reject batches, segregate goods, charge suppliers for testing and inspections, and, in serious or repeated cases, terminate the agreement. The clause should also clearly allocate responsibility for inaccurate, delayed or incomplete information, downtime costs, storage costs, returns, product withdrawals and customer claims. Indemnification provisions should be coordinated with liability caps, insurance arrangements and confidentiality obligations.
However, a contract does not transfer the operator’s administrative liability to the supplier. Even full compensation will not release goods detained at the border. For that reason, the delivery of a complete data package should be a condition of shipment or release of the goods, rather than an obligation to be fulfilled after an invoice is issued. In import scenarios, companies should additionally review Incoterms, the importer identified in the customs declaration and the customs representation model, since the party described as the “buyer” in a contract does not always qualify as the operator for EUDR purposes.
Procurement teams maintain supplier relationships, but they should not independently approve CN codes, assess evidence of legality, design warehouse controls or submit DDS. Effective implementation requires cooperation between procurement, compliance, logistics, legal, customs, IT and senior management. In corporate groups, finance and tax teams also play an important role because transaction structures, the importing entity, invoice flows and the timing of title transfer help determine the roles of participants in the supply chain. This does not mean, however, that VAT or customs classifications can automatically be equated with an EUDR role without separate analysis.
The internal procedure should describe how the process actually operates rather than merely repeating statutory obligations. A clear responsibility matrix is essential: who approves product scope, who collects supplier data, who validates geolocation information, who performs the risk assessment, who can approve mitigation measures, who submits the statement and who has authority to block imports or sales. For each critical decision, a deputy, a deadline and the system retaining the evidence should be identified.
A key mechanism should be a “release gate”, meaning a control point before shipment, customs clearance or sale. Goods covered by EUDR should not proceed if the required controls have not been completed. Management must accept that, where data is missing, such a gate will genuinely stop the transaction. Otherwise, pressure to meet sales targets will quickly turn a formal procedure into a collection of exceptions applied to every urgent delivery.
Following the 2025 amendment, the DDS is generally submitted by the operator that first places the relevant product on the EU market or exports it. Downstream operators and traders perform separate traceability obligations, the scope of which depends, among other things, on their position in the supply chain and their SME status. However, one fundamental principle remains unchanged: a reference number is not a “certificate of compliance”. The operator remains responsible for properly performing due diligence.
Documentation must be retained for at least five years. It should make it possible to reconstruct the connection between the DDS, quantities, batches, plots, evidence of legality, risk assessments and the mitigation measures applied. The Commission also points to the need for an annual review of the due diligence system. Where a single DDS covers multiple shipments, the risk of incorrectly allocating quantities and sources increases, and a non-compliance issue affecting part of the goods may influence the assessment of the entire statement.
The process should therefore capture changes in plantations, intermediaries, recipes, CN codes, countries of production, mixing models and country risk status. Periodic supplier reviews, monitoring of external signals, reconciliation of declared quantities against products actually placed on the market, and procedures for responding to information received after the transaction are all necessary. In the event of an inspection, the ability to quickly reconstruct the decision-making process will be far more important than maintaining a folder containing thousands of unrelated PDF files.
Even the most comprehensive policy will fail if the product master record does not indicate whether a given product is subject to EUDR, the buyer does not know which data is mandatory, and the warehouse mixes traceable and non-traceable batches. A typical scenario looks like this: the supplier sends a GeoJSON file, the document lands in the procurement inbox, no one verifies its quality, and the customs department only discovers the missing reference number just before filing the declaration. Formally, a “geolocation process” exists, but operationally it has no owner, no control point and no decision-making mechanism capable of stopping a transaction.
Before launching the process, it is worth conducting end-to-end testing on actual deliveries, from placing the order and obtaining data, through risk assessment and batch allocation, to DDS submission, customs clearance, warehousing and sale. The test should also cover exceptional situations, including quantity adjustments, vessel changes, deliveries from multiple plots, data inconsistencies, integration failures or urgent supplier replacement.
Quality controls and performance indicators are equally important, such as the percentage of classified SKUs, the proportion of suppliers with complete data sets, the number of geolocation errors, the time needed to resolve discrepancies and the number of transactions placed on hold. Training should be tailored to specific roles. A buyer must be able to identify a source change, a logistics specialist must understand the risk of mixing, a customs specialist must understand reference number requirements, and an approver must understand escalation criteria. A single webinar delivered to the entire organisation does not create a functioning compliance system.
A supplier questionnaire or the purchase of an IT tool at the beginning of the project can create a quick sense of progress, but often reinforces unverified assumptions. The first step should be to establish the actual scope of products and transactions: CN codes, composition, commodities, volumes, countries, suppliers, and import, production, distribution and export channels. Only then is it possible to assign roles to a specific product and a specific flow.
The same company may act as an operator when importing coffee, as a downstream operator when placing on the market a product manufactured from a commodity covered by a previous DDS, and as a trader when reselling another product. A change of code resulting from processing does not automatically determine a change of role; the determining factor is the code level specified in Annex I. Therefore, an analysis conducted solely at the legal entity level will be too general and may lead to incorrect conclusions.
The next step should be to map data flows: who creates the information, who transfers it, where it is validated, to which batch and document it is linked, and what happens when a supplier, source or recipe changes. Only on this basis can the three stages of the operator’s due diligence process be designed: information gathering, risk assessment and, where necessary, risk mitigation, together with acceptance thresholds and escalation criteria. Questionnaires, contractual clauses, procedures, integration with the EU information system and the selection of technological tools should be the outcome of this analysis, not its starting point.
A good approach is to pilot several supply chain scenarios of varying complexity: direct import of a single commodity, a multi-component product and sourcing through an EU intermediary. Such testing quickly reveals where problems actually arise, whether in source data, contractual arrangements, batch identification, risk decisions or system integration. It also allows companies to realistically estimate the resources required to cover the entire product portfolio.
Most challenges related to EUDR implementation are operational rather than purely legal in nature. The regulation defines the obligation, but its actual fulfilment depends on data quality, the ability to link information to a specific batch and a clear allocation of responsibilities. The greatest risks arise where information passes between participants in the process: between producers and intermediaries, suppliers and importers, procurement and compliance teams, as well as warehouse and customs systems.
For this reason, businesses should assess their supply chains well in advance, test data collection processes, identify suppliers requiring corrective actions, adapt their contractual frameworks and implement procedures capable of stopping non-compliant transactions. In practice, mapping thousands of plots, resolving inconsistencies or changing a sourcing strategy often takes much longer than preparing the legal documentation itself.
Effective implementation requires combining legal, tax, customs and compliance perspectives. Law defines obligations and liabilities; tax and finance help reconstruct corporate structures and transaction flows; customs ensures correct classification and the handling of import and export processes; and compliance provides the framework for risk assessment and the evidence trail supporting decisions. Only by integrating these elements into a single process can companies remain compliant with EUDR even when suppliers change, data is incomplete or goods are awaiting customs clearance.
No. The determining factors are the CN/HS code, the description in Annex I and the relevant commodity. Product composition alone is not sufficient. The analysis must also take account of “ex” designations and the classification of multi-component products.
As a general rule, yes. Low-risk status may simplify due diligence obligations, but it does not remove the requirement to collect the necessary information or assess the risk of mixing with commodities from other sources.
No. Such documents may serve as supporting evidence, but the operator should verify their scope, reliability and connection to a specific batch. Responsibility for due diligence remains with the operator.
In principle, the operator that first places the relevant product on the EU market or exports it. Downstream operators and traders have separate traceability obligations, the scope of which depends, among other factors, on their position within the supply chain and their SME status.
The operator cannot replace missing information with a general assurance from the supplier. A corrective deadline should be set, escalation procedures should be initiated and, if the required data is still not provided, the supply should be suspended or an alternative source of supply should be identified.
For at least five years. The records should allow the DDS and risk decisions to be linked to specific quantities, batches, plots and evidence of legality.