EUDR in 71 days: How your data becomes audit-ready, and the 4 habits that fail inspection
A joint Agridence and Meridia guide to preparing EUDR evidence: what to fix first, four linked stages, and four habits that leave shipments hard to defend.
A joint guide from Agridence and Meridia.
Audit-ready EUDR evidence comes from four linked stages: collecting plot and shipment data in a structured way, assessing risk independently, acting on the findings in sourcing, and filing a statement you can defend.
Most companies have the documents. Where they fall short is explaining what those documents mean. With 71 days to 30 December 2026, this guide sets out what to approach first and how to check where you stand.
Where the rules stand
Regulation (EU) 2025/2650 moved the application date to 30 December 2026 for three groups:
large and medium operators and traders
all downstream operators and traders, whatever their size
micro and small operators and natural persons placing products already covered by the EU Timber Regulation.
All other micro and small operators and natural persons follow on 30 June 2027.
What to fix first
With limited time and a small team, order matters more than completeness. These moves are ranked by the cost of getting them wrong.
Link every shipment to its plots
Effort: High. Suggested target: 31 October 2026.Clean the geometry (projections, duplicates, points on buildings)
Effort: Medium. Suggested target: 31 October 2026.Document your legality reasoning per sourcing country
Effort: High. Suggested target: 30 November 2026.Screen against more than one forest and land-use dataset
Effort: Medium. Suggested target: 15 November 2026.Show that excluded plots were removed from sourcing
Effort: Medium. Suggested target: 30 November 2026.Record input and output at every processing site
Effort: Medium. Suggested target: 30 November 2026.Rehearse an inspection with your own team
Effort: Low. Suggested target: 15 December 2026.
Most of these moves are analysis and documentation, not new data collection. The dates are suggested targets. The only regulatory deadline is 30 December 2026.
Stage 1. Collect data you can query, not just file
Test yourself: for any shipment, can you list its plots, legality answers and data version in one query? Folders and per-supplier spreadsheets can’t do this. You need plots, suppliers, transactions and shipments stored as linked records.
Fix these gaps now:
Validate geometry. Reject duplicates, misplaced points and conflicting boundaries.
Use polygons for plots above four hectares.
Give every legality answer an owner and a date.
Re-screen automatically when a supplier changes a boundary.
Done when:every shipment links to a fixed set of validated plots.
Stage 2. Assess risk independently, and show your working
Independent means the party screening isn’t the party being screened, and the method is set before the results are in.
Deforestation. Screen against more than one forest and land-use dataset. A single map can’t explain why it disagrees with another.
Legality. Assess land tenure, environmental law, labour rights and free, prior and informed consent against national and subnational law in each production area.
Landscape. A compliant plot in a fast-clearing area still carries mixing risk.
Done when:every risk rating has a named cause, such as tree-cover loss, a protected-area overlap or a failed legality check.
Stage 3. Act on findings in sourcing, and record it
Self-assessments and codes of conduct are not mitigation. Authorities expect evidence that non-compliant plots were excluded from sourcing.
Mitigation needs four things:
A named cause for each flag, so the supplier knows what to fix.
A dated decision: excluded, remediated, or accepted with a written justification.
A link to purchasing, so the next lot from a flagged plot is blocked when you buy, not when you file.
Supplier visibility, so suppliers see a finding before a shipment is rejected.
Done when:for any excluded plot, you can show when it was flagged, the cause, the decision, who made it, and the first purchase it blocked.
Stage 4. File, then be ready to defend each shipment
Submit the statement to the EU Information System before the goods are placed on the market, and pass the reference number downstream.
Then prepare for inspection.
The four habits that fail inspection
Filing data you cannot query
Keeping plots, suppliers, transactions and shipments in disconnected folders and spreadsheets.Assessing risk without showing your working
Relying on a single map or a risk rating without a named cause.Leaving findings outside purchasing
Recording a finding without linking the decision to sourcing and the next purchase.Filing without preparing to defend the shipment
Submitting a statement without being ready to explain the evidence behind it.
FAQ
We are downstream. Do we still need all of this?
No, you need less. Downstream operators and traders don't file their own statement. They pass on the first operator's reference number and keep supplier and customer records, with those reference numbers, for five years. Non-SME downstream operators still need to register in the EU Information System. You still need confidence that the statement you pass on can be defended, because your market access depends on it.
What if a plot is genuinely hard to map?
The regulation makes no exception for difficult terrain. Document the difficulty, the method you used and the evidence you relied on. A documented method is better than a missing polygon.
What happens after 30 December 2026 if we are not ready?
Products without a valid statement can't be placed on the EU market. You'll feel the impact before any penalty arrives: goods held at the border, orders unfilled and contracts at risk.
How long does it take to set this up from a standing start?
For a complex chain with several origins, longer than the time left. If you're starting now, focus on your highest-volume origins. Partial coverage you can document is better than full coverage you can't show.
Where Agridence and Meridia come in
A data platform alone won't get you through an inspection. Neither will a risk assessment that never reaches purchasing. That's why we work together.
Agridence covers the chain from farm to filing: structured data collection, links between plots and shipments, and the outputs you file.
Meridia Verify® checks that data against EUDR requirements at plot level. Every flagged plot comes with a named cause the supplier can act on.
Want a second opinion on your self-check? Either team can review where your setup stands and what you can realistically cover before 30 December.