Filed under EU Deforestation Regulation Explained: Scope, Requirements and Compliance
Plot record: legal status and review details
- Jurisdiction
- European Union
- Status
- In force; main obligations apply according to Article 38
- Application
- 30 December 2026 generally; 30 June 2027 only where Article 38(3) applies; specified Annex I additions from 30 December 2027
- Relevant provisions
- Articles 2 to 13, 26, 33, 38
Review this page when:
- EUDR amendments
- Commission guidance or FAQ revision
- Article 38 application dates
- Annex I amendments
Compliance is a sequence of connected decisions
An EUDR compliance lifecycle begins before purchasing or releasing covered goods and continues after their sale or export. The sequence is to establish product scope, identify the transaction and legal role, collect the required information, assess and address risk, obtain the required regulatory coverage, control release and retain evidence. Later concerns can require further action.
The steps should share a product identifier. Otherwise procurement may approve a supplier, the compliance team may assess a farm list and logistics may dispatch a different batch. A sound lifecycle explains why each decision and document concerns the goods actually entering the regulated commercial flow.
Establish scope and application timing
Begin with the product description, material composition and customs classification. Compare them with current Annex I. Record the legal basis for any conclusion that the product is outside scope, affected by a transition or subject to a deferred application date. Do not let an unexplained supplier answer become the company's permanent scope rule.
The current general application date for principal obligations is 30 December 2026. Article 38(3) provides a later date for qualifying operators under its conditions, while specified new product entries apply from December 2027. Timber has additional transitional issues. Timing should be assessed alongside the actual product and business facts rather than assigned solely from the company's headcount.
Assign the legal person and role
Identify who places, exports or supplies the relevant product. Apply the current operator, downstream operator and trader definitions. Record enterprise status where it affects the obligations. A transformed product made from covered relevant inputs may lead to a downstream operator assessment, while directly introducing other goods can create an operator flow.
The role determines the work required. Ordinary operators undertake the principal due diligence and statement process. Article 5 controls downstream operator and trader duties. Qualifying micro or small primary operators use the separate Article 4a regime. Giving a central team operational responsibility is helpful, but the legal entity responsible for each flow must remain visible.
Collect information before the decision point
Ordinary operator information under Article 9 includes product and quantity data, production country, locations and production period, supplier and customer details, and evidence for deforestation-free status and legality. Build collection into supplier onboarding and purchase planning rather than waiting until a shipment is ready to leave.
Use a real batch to test whether the information connects. Can the supplier explain all contributing production origins? Do processing records preserve that relationship? Are quantities plausible? A completed questionnaire can hide major gaps if its location field contains a warehouse address or its farm list is unrelated to the goods delivered.
Evaluate and resolve the actual risk
Article 10 requires the operator to analyse the information against relevant criteria, including source reliability, country risk, supply-chain complexity and mixing concerns. The assessment should identify what was checked and why the information supports the conclusion. Merely labelling the supplier “approved” leaves the reasoning unclear.
Where risk is more than negligible, use appropriate Article 11 mitigation. The measure should answer the unresolved issue, such as obtaining better historical evidence, investigating a land-rights concern or changing the sourcing arrangement. If the required conclusion cannot be supported, hold the product. The readiness checklist helps teams test whether they can operate that hold in practice.
Make the required submission and release decision
An ordinary operator submits the due diligence statement before placement or export after completing the assessment. A qualifying primary operator follows the simplified declaration route. Submission through the Information System creates the relevant regulatory record; it is not an authority's approval of the underlying goods.
Tie the reference or declaration identifier to the product and relevant quantity. Decide who may authorise release and which exceptions trigger a hold. Changes between assessment and dispatch, including a different production origin or substituted batch, should be checked before release. An earlier assessment should not automatically follow a purchase order after its underlying goods have changed.
Preserve downstream information
Operators communicate associated statement references or declaration identifiers to downstream operators and traders. Those businesses keep the Article 5 information, including supplier and business-customer details and, where their supplier is an operator, the relevant identifiers. Non-SME downstream operators and traders also have registration duties.
Commercial systems should preserve the relationships between receipts, stock movements and outgoing supply. Retaining a reference number without knowing which goods it covers is weak evidence. Similarly, an operator should preserve the assessment and source records supporting its submission rather than keeping only the final electronic statement.
Monitor, notify and correct
New information can emerge after the product has been supplied: an incorrect origin declaration, a supplier's undisclosed purchases or a substantiated land concern. Articles 4 and 5 require notification in specified circumstances. The response process should identify affected products, downstream recipients and the competent authorities concerned.
Build this into normal incident handling. A buyer receiving an origin correction should know how to escalate it immediately. The team needs access to the original evidence and decision, including any limitations. Fast identification of the affected batches is more useful than a general company policy promising to investigate concerns without explaining who will act.
Review the system as well as individual files
Article 12 requires maintenance and review of the operator's due diligence system, while the risk assessment provisions also require documented review. Changes in products, suppliers, law, country classifications and official guidance can affect the controls. Review should therefore test whether the process still produces reliable decisions in current circumstances.
The EUDR overview explains the framework behind this sequence. Use Articles 4 to 13 of the current regulation to define the applicable duties, and keep the workflow specific enough that a colleague can follow one real product from procurement through release and later review.
Primary sources on the record
Articles 2 to 13, 26, 33, 38. 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.