Design EUDR records so product lots, supplier evidence, production locations, risk assessment results, and due diligence statement references stay connected.
Use stable product and supplier identifiers to preserve origin evidence, track corrections, and reconstruct the records behind each filing.
An EUDR must preserve the link from each relevant product lot to every production plot, or to every establishment where covered cattle were kept. Plot coordinates use at least six decimal digits, and non-cattle plots larger than four hectares require polygons. The same record should hold the production date or time range, supplier, legality and deforestation-free evidence, risk conclusion, statement status, and downstream reference-number handoff.
Start with a record that can survive handoffs between procurement, sustainability, trade compliance, and the team that files or tracks the due diligence statement. The record should identify the relevant product and commodity, the supplier relationship, the product lot or consignment used by the business, and the origin evidence used for EUDR due diligence.
The system should keep evidence attached to the product record it supports. Do not store coordinates or map files as a detached sustainability archive if procurement, risk review, submission, and downstream communication depend on them.
Sources (1)
Supports linking relevant products to deforestation-free, legality, due diligence statement, and Article 9 information-and-evidence records, including geolocation of production plots or establishments.
the geolocation of all plots of land
Use Sorena to connect product lots, supplier evidence, geolocation records, risk assessment results, DDS references, and downstream handoffs before EUDR filings depend on them.
Supplier intake should decide whether the supplier is providing original production-location evidence, an existing reference number, a simplified declaration identifier, or documents that support legal and deforestation-free production. The receiving workflow should block acceptance when the supplier evidence cannot be tied to the product lot or origin record.
Apply the Regulation's minimum definition: latitude and longitude with at least six decimal digits, and polygons for non-cattle production plots larger than four hectares. The Regulation does not prescribe a map vendor, platform, API, or internal database schema.
Sources (1)
Supports supplier intake for geolocation and legal-production evidence, plus the limited postal-address substitution for qualifying micro or small primary operators.
adequately conclusive and verifiable information that the relevant products are deforestation-free
Traceability breaks when sourcing, warehouse, customs, and sustainability systems use different identifiers without a join key. For EUDR work, every product lot or consignment record used by the business should be linkable back to the supplier evidence and forward to the risk assessment and record.
Where a consignment contains inputs from several plots, establishments, suppliers, or production periods, the system should retain the many-to-one relationship. Replacing several origins with one averaged location or one country-level note can leave the risk reviewer unable to test whether the relevant product is supported by the required evidence.
Operational example: if a lot combines cocoa from three production plots, retain all three plot identifiers against that lot. If a supplier corrects one polygon, keep the prior version and ask the risk reviewer to record whether the correction changes the release decision.
Sources (1)
Supports maintaining product traceability through the due diligence sequence: information collection, risk assessment, and mitigation where the risk is not negligible.
The risk assessment should consume the same product, supplier, and origin records that the business will use for market placement, export, or downstream communication. A separate spreadsheet can be useful for review, but it should not become the only place where EUDR evidence is reconciled.
The reviewer should be able to see the product scope decision, supplier chain, country of production, origin evidence, legality documentation, deforestation-free evidence, and any supplier correction or new risk information. If the risk assessment does not conclude no or negligible risk, mitigation must happen before placing on the market or exporting.
Sources (1)
Supports the no-or-negligible-risk release rule, mitigation before placement or export, and the limited low-risk simplification after checking supply-chain complexity and circumvention or mixing risk.
no or only a negligible risk
The due diligence statement should be the controlled output of the evidence workflow. Operators submit the only after due diligence supports compliance and no or negligible risk; they also keep DDS records and communicate reference numbers downstream. Where a simplified declaration applies, the system should track the declaration identifier instead.
The Article 33 information-system handoff should not be treated as a one-way upload. Internal systems need to store what evidence version supported the submission, who approved it, the reference number or declaration identifier returned or used, and which downstream operators or traders received that identifier.
Sources (2)
Supports DDS submission, operator responsibility, five-year DDS retention, downstream reference-number communication, authorised-representative submissions, and Article 33 information-system handoffs.
the reference numbers of the due diligence statements
Official implementing-regulation source for the EUDR information-system context; this page does not infer field schemas or vendor requirements from it.
the Information System
Articles 2 and 9 specify minimum precision, all-location coverage and the polygon threshold. Record internal choices about software, storage, validation and exchange formats separately, and check the information system's current submission requirements before filing.
The system must preserve the information and evidence needed for EUDR due diligence, keep supplier and downstream records connected, support risk assessment and mitigation, and retain or declaration identifiers for authority and supply-chain handoffs.
Sources (1)
Supports keeping the page focused on EUDR evidence duties, downstream information duties, risk assessment, and mitigation rather than unsupported technical-tool mandates.
collect information, documents and data
"the Information System"
"no or only a negligible risk"
"the geolocation of all plots of land"
"the reference numbers of the due diligence statements"
"adequately conclusive and verifiable information that the relevant products are deforestation-free"
"collect information, documents and data"
"collect information, documents and data"
Concise EU Deforestation Regulation answers on scope, covered commodities, operator and trader roles, due diligence statements, geolocation, low-risk countries, customs release, SME timing, enforcement, and records.
Test whether the EU Deforestation Regulation applies by checking Annex I product scope, EU market placement or export, operator/trader status, downstream role, SME status, and simplified due diligence conditions.
A practical EU Deforestation Regulation checklist covering product scope, supplier evidence, geolocation, risk assessment, mitigation, due diligence statements, recordkeeping, and customs readiness.
EUDR compliance guide covering operator and trader duties, Article 9 information, Article 10 risk assessment, Article 11 mitigation, due diligence statements, records, and authority-readiness.
How EUDR country-risk benchmarking affects low-risk simplified due diligence, full due diligence, information collection, risk monitoring, and evidence records.
Use the official EUDR country list to route each production origin through low-risk simplified due diligence or full due diligence, with evidence and review triggers.
EUDR calendar covering application dates, the current country-risk act, the information system, timber transition rules, and preparation tasks by actor.
EUDR readiness guide covering the correct application cohort, role-specific first actions, geolocation evidence, due diligence statements, and country risk.
Build an EUDR evidence file for due diligence statements: Article 9 information, geolocation records, supplier proof, risk assessment, mitigation, reference numbers, and retention.
File an EUDR due diligence statement with the correct Annex II data, operator approval, Information System handoff, reference number, and retained evidence.
Prepare the mandatory EUDR Annex II due diligence statement fields and the internal evidence log that supports the operator's no-or-negligible-risk conclusion.
How to collect, check, and use EUDR geolocation evidence for relevant commodities and products, Article 9 information, risk assessment, supplier records, and due diligence statements.
Build an EUDR evidence file that links Annex I commodity scope, supplier and trader records, geolocation evidence, product lots, risk assessment, and due diligence statement support.
How to check EUDR scope for the seven commodities, Annex I relevant products, operator and trader roles, and the evidence needed to support a scope decision.
EUDR enforcement guide covering risk-based checks, no-warning inspections, interim measures, corrective action, penalties, and records by actor.
EUDR penalty guide explaining Article 25 fines, the 4% turnover rule, confiscation, temporary restrictions, corrective action, and national-law limits.
EUDR requirements based on official sources: scope, due diligence, geolocation, risk assessment, mitigation, DDS filing, records, and simplified regimes.
How to run an EUDR Article 10 risk assessment, decide when risk is not negligible, apply Article 11 mitigation, and keep release evidence before placing products on the EU market or exporting.
A practical EUDR supplier onboarding template for Annex I product scope, supplier roles, geolocation evidence, risk inputs, mitigation records, DDS references, and five-year records.
Compare EUDR product-level market controls with the current CSDDD company-scope thresholds, human-rights and environmental due diligence, application dates, evidence, and enforcement.
How to check whether a product is in EUDR Annex I, connect it to a covered commodity, and keep supplier and trade evidence without relying on unsupported code lists.
What EUDR country benchmarking means, how low-risk production affects simplified due diligence, and what operators still need to collect.
How to prepare EUDR due diligence statement references, information-system handoffs, importer checks, and release evidence before customs or export clearance.
FAQ on EU Deforestation Regulation DDS reference numbers, including operator submissions, downstream handoffs, Article 33 information-system context, and evidence records.
How EUDR teams should collect, link, and use plot-level geolocation evidence for due diligence statements, suppliers, consignments, and risk assessment.
FAQ guidance on EUDR information system filing, due diligence statement submission, declaration identifiers, downstream handoffs, representatives, and evidence retention.
FAQ on how EUDR Articles 10 and 11 handle non-negligible risk, when operators should stop placement or export, and what evidence belongs in the file.
Classify EUDR operators, downstream operators, and traders by product and transaction, then identify the due diligence, information, registration, and recordkeeping duties for each role.
When EUDR Article 13 simplified due diligence applies, what operators must still collect and submit, how mixing or circumvention defeats it, and which low-risk list controls.
EUDR timing by role and size: the 30 December 2026 main date, the narrow 30 June 2027 operator exception, its timber exclusion, and the evidence needed to use it.
What supplier evidence to collect for EUDR Article 9 information, geolocation, risk assessment, due diligence statements, and downstream recordkeeping.
EUDR FAQ on competent authority checks, evidence requests, due diligence records, corrective action and penalties for non-compliance.