Filed under EUDR Due Diligence Explained: Information, Risk and Compliance
Plot record: legal status and review details
- Jurisdiction
- European Union
- Status
- Current consolidated Regulation (EU) 2023/1115, including the 2025 amendment and September 2026 consolidation. Main obligations are not yet generally applicable on the verification date.
- Application
- Generally 30 December 2026; 30 June 2027 for eligible micro and small operators, subject to the timber exception; some newly added products apply from 30 December 2027. Check the product and actor-specific rules.
- Relevant provisions
- Articles 3, 4 and 8 to 13
Review this page when:
- Amendments to Articles 3 to 13
- New Commission due diligence guidance or FAQs
- Changes to country benchmarking
- Application dates and product-scope changes
Before the regulated transaction
An ordinary operator must complete EUDR due diligence before placing a relevant product on the EU market or exporting it. Articles 4 and 8 put the process ahead of that regulated event. Article 4(2) also requires prior submission of the due diligence statement. A plan to collect missing evidence after the goods have entered the market does not satisfy this sequence.
Completion means having enough verified information and a supported conclusion that the product complies, with no or only negligible risk. It does not mean that a supplier questionnaire has merely been sent, that a file has been opened, or that a mitigation audit has been booked. If a material concern remains unresolved, the ordinary operator has not reached a lawful release decision.
Use the wider due diligence process to define which activities must precede the release gate. Identify the legal placing-on-the-market or export event for the actual transaction. Contract signature, payment, production, shipping and delivery are useful operational milestones, but none should be assumed to define that legal event in every supply arrangement.
Separate legal deadlines from purchasing milestones
A business can begin collecting stable information well before an order is placed. Supplier identities, farm registries, product composition and relevant production laws may be investigated during onboarding. Transaction-specific information, such as the final lot quantity and production sources, must then be reconciled before the product is released. Early collection saves time only if the eventual goods genuinely match the approved file.
For example, a buyer may approve coffee from specified plots in March and place a shipment order in August. If the supplier fills part of the order from a different cooperative, the March review cannot automatically cover the replacement beans. The release decision must use the actual origins, applicable harvest period and supporting evidence. Approval of the commercial supplier is not approval of any product it may supply.
Build procurement dates around the time needed to resolve discrepancies. Set an internal evidence deadline before the statutory transaction, allowing for document verification, location corrections and additional risk work. This earlier deadline is a business control, not a separate date prescribed by the Regulation. Label it clearly so employees understand which rule is legal and which is an internal operating standard.
Follow the right order for an ordinary operator
First establish that the product falls within the relevant scope and that the business acts as an operator for this transaction. Then collect Article 9 information, verify and assess it under Article 10 unless a qualifying Article 13 route applies, and carry out necessary Article 11 mitigation. Record why the resulting risk is no or negligible before submitting the ordinary statement.
After submission, connect the statement to the covered goods and make the required reference available to the relevant transaction teams. The reference is useful for traceability and subsequent formalities, but receipt of a reference does not prove the authority has checked and approved the consignment. Releasing goods on that assumption confuses a declaration made by the operator with an official compliance determination.
Article 4(4) prevents placement or export where the ordinary operator cannot fulfil its required due diligence or statement obligations. An Information System problem therefore needs a documented resolution through applicable official procedures. Do not invent a fallback consisting of an internal reference number or a promise to submit later. Where a formal contingency arrangement exists, check its exact scope and conditions.
Check role-specific exceptions
Downstream operators and traders are governed by the revised Article 5 framework. Their obligations should not be rewritten as an ordinary operator statement requirement for every resale or processing step. Nevertheless, their applicable duties and the Article 3 prohibition matter before goods proceed. A downstream business cannot solve a known compliance problem simply by obtaining an upstream reference.
A qualifying micro or small primary operator follows Article 4a. Its one-time simplified declaration must precede placement or export, or the applicable public-database arrangement must result in assignment of the declaration identifier before the goods proceed. This is a narrow eligibility-based regime, rather than an automatic exception for all small businesses.
Article 13 simplified due diligence concerns qualifying low-risk production and modifies the assessment and mitigation duties. It does not move the general compliance decision after release. The ordinary operator still needs the required information and, where applicable, the prior statement. Relevant information indicating non-compliance or circumvention restores the full Article 10 and 11 process.
Reopen decisions when the facts change
Repeated shipments can use reliable existing evidence where it remains applicable, but each intended placement or export must be covered by a valid compliance conclusion. Changes in quantities, sources, locations, production periods or risk information can break the relationship with the earlier assessment. The repeated-shipment workflow explains how to preserve useful evidence without turning a supplier approval into indefinite permission.
After placement, Article 4(5) requires immediate notification when an operator obtains relevant new information indicating a risk that the product does not comply. That post-market responsibility is separate from the pre-market gate. Reporting a later concern does not excuse a deficient original assessment, and an originally reasonable assessment does not justify ignoring new evidence.
As verified on 16 October 2026, the principal general application date is 30 December 2026. Most eligible micro and small operators have a later date of 30 June 2027, with the specified timber exception, and some newly added products have a later December 2027 date. Check Article 38 and the applicable scope provisions in the current Regulation before setting a transaction's mandatory release controls.
Primary sources on the record
Articles 3, 4 and 8 to 13. This entry was checked against the consolidated text dated 18 September 2026. Consolidated texts are documentation tools; the authentic acts are those published in the Official Journal.
Check the current sources and the guidance of the relevant competent authority for your situation. This page is not legal advice or a compliance determination.