Search every question across sub-FAQs

An operator should prepare the due diligence path before placing a relevant product on the EU market or exporting it. The operator path centers on Article 3 compliance, due diligence, and the due diligence statement unless the specific micro or small primary operator simplified declaration route applies.

A downstream operator or trader should first collect the supplier and supply-chain information required for its role. Non-SME downstream operators and non-SME traders also need registration in the Article 33 information system before placing, making available, or exporting relevant products.

Keep the timing file practical: it should show why the business used the main date or the later date, who the EUDR actor is, and which product activity creates the obligation. A size label alone is not enough for review because EUDR duties also depend on role and product movement.

For operators, retain the due diligence statement record and the underlying Article 9 evidence. For downstream operators and traders, retain the Article 5 supply-chain information. For a micro or small primary operator using the simplified route, retain the simplified declaration identifier and the source facts showing why that route applies.

The common mistake is to read "SME" as if every micro, small, and medium-sized enterprise receives the same delayed obligation date. The grounded distinction is narrower: the later 30 June 2027 date is tied to certain natural persons and micro or small undertakings, while the main core-obligation date remains 30 December 2026.

A second mistake is to answer timing before role. The same business group may have different EUDR records for operator activities, downstream operator activities, trader activities, and micro or small primary operator activities.

Build the supplier evidence file around the product movement that will be placed on the EU market, made available, or exported. The file should identify who supplied the relevant product or commodity, what product or quantity the evidence supports, where the commodity was produced, and which due diligence statement reference number or simplified declaration identifier applies when one has been provided.

A supplier declaration is useful only if it can be reconciled with the commercial record and the origin evidence. Treat missing supplier identity, missing production origin, unsupported geolocation, unexplained mixing, or a reference number that cannot be tied to the product as unresolved EUDR risk rather than as a completed evidence file.

Article 9 information collection should let the operator demonstrate that the relevant product complies with the EUDR market-access conditions: deforestation-free, produced in accordance with relevant legislation in the country of production, and covered by the required statement or declaration. In practice, that means the supplier file has to connect commercial product data to origin data and supporting documents.

The grounding reviewed for this FAQ supports collecting and keeping information and evidence, including geolocation of plots of land or establishments and documentation demonstrating deforestation-free and legal production. Teams should therefore make geolocation and legal-production evidence mandatory fields in the supplier pack, not optional sustainability attachments.

Supplier evidence feeds the Article 10 risk assessment; it does not supersede it. The practical test is whether the evidence shows enough about the supplier, product, production origin, geolocation or establishment, legal-production documents, supply-chain complexity, and possible mixing or circumvention to support no or only negligible risk.

If the evidence is incomplete or inconsistent, record the gap and mitigate before the product is placed on the market or exported. Mitigation may include supplier clarification, additional origin documents, segregation of mixed lots, rejection of unsupported inputs, or holding the shipment until the evidence supports the risk conclusion.

Operators use supplier and origin evidence before submitting or making available the due diligence statement through the Article 33 information system. The statement should not be assembled from a disconnected certificate archive; it should point back to the product, supplier, geolocation or establishment, legal-production, risk assessment, and mitigation records that support the conclusion.

Downstream operators and traders need supply-chain information too. Where the supplier is an operator, keep the supplier details and the due diligence statement reference number or simplified declaration identifier, then pass required references further down the supply chain.

Keep records in a way that a reviewer can reconstruct the supplier chain without relying on inbox searches. Operators keep due diligence statement records for five years, and downstream operators and traders keep Article 5 supply-chain information for at least five years and provide it to competent authorities on request.

A useful retention file contains both the upstream evidence and the downstream handoff: supplier details, product and quantity linkage, origin and geolocation evidence, legal-production documents, risk assessment result, mitigation record if used, due diligence statement reference number or declaration identifier, and downstream recipient information.

Avoid treating a supplier attestation, certificate, or reference number as complete EUDR evidence by itself. The supplier file has to remain connected to the actual product movement and to the Article 9, risk assessment, statement, and retention records behind the release decision.

The grounding reviewed for this FAQ supports one specific geolocation adjustment: for micro or small primary operators, Article 9(1)(d) geolocation may be replaced by the postal address of plots of land or the establishment. Do not turn that into a general shortcut for other suppliers, and do not publish unsupported coordinate-format, polygon-threshold, penalty, or deadline claims in the supplier evidence FAQ.

Member States designate competent authorities to check whether operators and traders comply with the EUDR. For an in-scope product, the practical enforcement file should show that the product is deforestation-free, was produced in accordance with relevant legislation in the country of production, and is covered by the required due diligence statement or simplified declaration.

For operators, enforcement readiness starts before placing on the EU market or exporting: exercise due diligence, submit the required statement through the information system when due diligence shows no or negligible risk, keep the due diligence statement record for five years, and pass the reference number or declaration identifier down the supply chain where required.

A competent authority request should be answered with the underlying due diligence file, not just the due diligence statement reference. The file should connect the product to the commodity, country and place of production, supplier, risk assessment outcome, mitigation steps where needed, and the final no-risk or negligible-risk conclusion.

Downstream operators and traders have a separate evidence burden. They must collect and keep the supply-chain information required by Article 5, including supplier details and relevant due diligence statement reference numbers or declaration identifiers, and provide that information to competent authorities upon request.

Treat the request as a product-specific evidence exercise. Freeze changes to the relevant evidence file, identify the affected due diligence statement or declaration identifier, and assemble the records that prove the product met Article 3 before it was placed, made available, or exported.

If new information suggests a product already placed or made available may be at risk of non-compliance, downstream operators and traders should not wait for a formal penalty process. The grounded obligation is to inform competent authorities and downstream recipients; for export cases, the downstream operator informs the competent authority of the Member State that is the country of production.

The safe public answer is that consequences are set through the EUDR and Member State enforcement rules, and they should not be reduced to a generic national fine number. The Regulation requires Member States to lay down penalties for infringements, while competent authority checks can also drive corrective handling of the affected products and evidence gaps.

For internal planning, separate the grounded consequences from unverified local figures: preserve the authority correspondence, identify whether the issue is missing evidence, unresolved risk, an incorrect due diligence statement, or product non-compliance, and keep any penalty assessment tied to the Member State rule that actually applies.