Filed under EUDR Timeline: Application Dates, Amendments and What Happens Next
Plot record: legal status and review details
- Jurisdiction
- European Union
- Status
- In force; substantive obligations apply on the dates and conditions specified in current law.
- Application
- 30 December 2026 generally; 30 June 2027 for qualifying operators under Article 38(3); 30 December 2027 for expressly deferred Annex I entries.
- Relevant provisions
- Articles 1(2), 37, 38 and Annex I
Review this page when:
- Amendment to Articles 37 or 38
- Annex I amendment
- Updated Commission guidance or FAQs
Track deadlines by product, entity and legal route
An EUDR deadline tracker should show why a particular activity follows a particular date. The current baseline is 30 December 2026 generally, 30 June 2027 for operators satisfying Article 38(3), and 30 December 2027 for expressly deferred Annex I entries. A list of dates without eligibility evidence is not enough to control release decisions.
Use the EUDR implementation timeline for the legal background. The tracker described here is a practical register, not an official Commission tool or an automated eligibility determination. Its value comes from connecting the enacted rule to actual products, legal entities, planned transactions and the person responsible for keeping the conclusion current.
Create one record for each meaningful assessment
Start with the legal entity performing the activity and the relevant product category. Add the commercial role, commodity, CN code and full Annex description. The product category should be precise enough to preserve meaningful differences. A single row called coffee could conceal already-covered beans and expressly deferred extracts with different timing conclusions.
Record the relevant market activity and expected date separately from the supplier's invoice and production dates. These events answer different legal questions. A record should make clear whether the business is considering first placement, downstream availability or export. Where the role changes between supply routes, create separate assessments rather than forcing both routes into an ambiguous company-wide label.
Record the basis for any later date
For Article 38(3), include the referenced size category, evidence that the operator was established as such by 31 December 2024 and the EUTR Annex comparison. Do not enter June 2027 simply because a salesperson describes the business as small. The later route has several conditions, and each should be visible in the record.
For an expressly deferred Annex I entry, record the exact code and wording containing the December 2027 application statement. Keep any origin limitation or exclusion with the assessment. A commercial product name or shared commodity is insufficient. The December 2027 product explanation illustrates why a later date for one derivative cannot automatically extend to all products from the commodity.
Keep timber transitions in a separate field
Where legacy timber is relevant, record the Article 37 assessment independently of the general application date. Include the EUTR product definition, evidence of production before 29 June 2023 and placement history. This prevents a general small-operator entry from hiding a product-specific older-stock rule or incorrectly postponing EUTR Annex products to June 2027.
Preserve the exact legal boundary: EUTR continues for the described goods until 31 December 2029, and Article 37(3) requires Article 3 compliance for the described older timber placed from 31 December 2029. A tracker showing only EUDR from 2030 would not faithfully record that wording. Boundary-date consignments should trigger a focused review rather than a guessed system default.
Add operational milestones before application
The legal date is only one field. Add target dates for supplier onboarding, production-location collection, legality evidence, land-history review, risk assessment, mitigation and any required submission. Work backwards from the intended transaction so incomplete evidence can be corrected without pressure to release unsupported goods. Internal milestones should reflect the complexity of the supply chain.
Assign an owner to each unfinished task and identify the evidence of completion. A status such as supplier contacted is not the same as validated production locations. Likewise, account created does not mean statement submission has been tested. Use status descriptions that show what has actually been achieved and what remains necessary before the product can follow the approved release process.
Make unresolved assumptions visible
Include a field for open questions and a decision owner. A disputed classification, unclear establishment history or missing production record can change the route. Do not allow an unresolved question to disappear behind a green deadline cell. Record the temporary planning assumption and the condition that must be satisfied before the conclusion is treated as final.
Where evidence conflicts, retain the conflict and the review outcome. Replacing an older document with a newer supplier assertion without explanation weakens the record. The tracker should link to the underlying file, not attempt to hold every document itself. Its purpose is to show the decision and where the supporting material can be retrieved.
Review at defined triggers and intervals
Set a responsible owner and a next review date for each assessment. Trigger earlier review when an amendment is published, guidance materially changes, a supplier changes origin, a product is reformulated or a new entity takes over the activity. Changes in country benchmarking or Information System requirements may also affect the practical compliance route.
After an application date passes, update the status from preparation to ongoing control. Keep collecting and reviewing evidence for subsequent products and transactions. A deadline tracker should not mark the business permanently compliant merely because a date was reached or a project was closed. Continuing duties and responses to new information remain part of the operating process.
Use a controlled approval and change log
Every approved timing conclusion should identify its legal source, verification date and reviewer. Keep earlier versions so users can understand past decisions. When a conclusion changes, record whether the reason was new law, corrected facts, new guidance or a changed product. That distinction helps management understand whether other records need the same review.
Use current Articles 37 and 38 and Annex I as the legal reference. The resulting register should let purchasing, logistics and compliance staff answer one practical question consistently: which requirements must be ready before this entity performs this activity with these goods? A clear evidence-backed answer is more useful than a countdown that treats the whole portfolio as identical.
Primary sources on the record
Articles 1(2), 37, 38 and Annex I. 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.