EU Deforestation Regulation · FAQ index

Questions and answers

Search the answers across this artifact’s FAQ modules. Open any answer in its guide or copy a direct link to share it.

62 questions across 12 modules

Back to FAQ overview
Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Browse 12 FAQ modules

Showing 1–15 of 62 questions

EUDR Annex I product lookup: how to check scope

How should a team check whether a product is in EUDR Annex I?

Start with the product being placed on the EU market, made available on the EU market, or exported. Then compare that product to , which is the regulation's product-scope list for relevant commodities and derived products. An item that matches is a . Representative matches include cocoa beans and chocolate under cocoa, coffee under heading 0901, specified cattle meat and leather, palm oil, natural rubber, soya beans, and listed wood, paper, and furniture products.

A useful lookup record should name the product or SKU, the supplier, the relevant commodity family, the product match or non-match, and the role affected by the transaction. If the item is in scope, Article 3 connects the product to the EUDR conditions: deforestation-free status, production in accordance with relevant legislation of the country of production, and a due diligence statement or simplified declaration where required.

  • Identify the traded product, not only a marketing category or internal material group.
  • Check whether the product falls under one of the covered commodity families named in the EUDR: cattle, cocoa, coffee, oil palm, rubber, soya, or wood, including derived products listed in .
  • Record whether the business is acting as an operator, downstream operator, or trader for that movement.
  • If the product is in scope, link the lookup to the due diligence statement, simplified declaration identifier, or downstream supplier information required for the role.
  • If the product is out of scope, preserve the reason for the non-match and the evidence used, because product composition, suppliers, and trade descriptions can change.
EUDR Annex I product lookup: how to check scope

How should commodity links, CN codes, HS codes, and customs descriptions be handled?

Use customs and trade fields as evidence, not as a substitute for the check. Product descriptions, a or HS classification, supplier master data, and invoices can help identify what the product is and which commodity family it links to, but this FAQ does not reproduce a standalone code list.

For an Annex entry marked "ex", match both the code and the narrower product description because the entry does not cover every good under that code. Goods produced entirely from material that completed its lifecycle and would otherwise have been discarded as waste are excluded under the Annex rule. The exclusion does not cover manufacturing by-products from a process that used material that was not waste. Do not treat offcuts from such a process as excluded merely because they are described as recycled.

Keep the official source next to the business evidence that explains why the product does or does not match. Do not copy an old spreadsheet of codes into the lookup and treat it as current unless it is reconciled to the official EUDR source used by the review.

Read with Commission Delegated Regulation (EU) 2026/2102, in force from 18 September 2026. It changes product descriptions, removals and exclusions. Specific added entries, including frozen cattle tongues and coffee extracts, apply from 30 December 2027. Check the exact amended entry and its date before deciding that a product is covered.

  • Use customs descriptions to confirm the actual product being traded.
  • Use CN, HS, or tariff fields as pointers to review, especially when product names are vague or supplier descriptions differ.
  • Do not publish or rely on an internal code table unless the source and review date are clear.
  • Where product composition is ambiguous, ask the supplier for the material or commodity basis before marking the item out of scope.
  • Keep the final conclusion tied to the official product-scope source, rather than only to an internal stock category or brokerage description.
EUDR Annex I product lookup: how to check scope

What supplier and trade evidence should support an Annex I lookup?

The lookup should be backed by records that let a reviewer connect the legal scope conclusion to the commercial movement. For an in-scope product, the record should show the supplier, the product identity, the commodity link, the transaction or shipment context, and the EUDR reference information available for the role.

Operators need due diligence evidence before placing relevant products on the market or exporting them. Downstream operators and traders need supply chain information, including supplier details and, when the supplier is an operator, due diligence statement reference numbers or declaration identifiers. Those records make the lookup usable after the original buyer or product owner leaves the team.

  • Product or SKU name, supplier part number, and trade description used for the lookup.
  • Supplier identity and upstream role, including whether the supplier provides a due diligence statement reference number or declaration identifier.
  • Commodity family and match used for the scope conclusion.
  • Invoices, purchase orders, import/export records, or shipment records that tie the conclusion to the actual movement.
  • Downstream recipient information where the business is required to keep supply chain information.
  • Review note for unresolved uncertainty, such as a supplier description that does not clearly identify the commodity basis.
EUDR Annex I product lookup: how to check scope

What are the most common mistakes in EUDR Annex I product lookup?

Repeat the check when product composition, supplier data, or trade classification changes. Checking only a product name, internal category, or customs field can produce the wrong scope result when the record is not tied to Annex I and supplier evidence.

For an in-scope item, identify which party must hold or pass on the due diligence statement, simplified declaration identifier, or Article 5 supply-chain information.

  • Do not assume every product connected to a covered commodity is automatically listed; check the product against .
  • Do not assume a product is out of scope because the supplier description avoids the commodity name.
  • Do not rely on unsupported copied code lists, stale tariff mappings, or internal material groups as the only evidence.
  • Do not separate the lookup from supplier due diligence references or downstream trade records.
  • Do not mark a product out of scope without keeping the reason and the source used for the conclusion.
EUDR country benchmarking FAQ: low, standard, and high risk

What is country benchmarking under the EU Deforestation Regulation?

is the Article 29 system that assigns countries, or parts of countries, to a low, standard, or high risk category for EUDR purposes. The category is about the country-of-production risk context; it does not decide by itself whether a shipment, product line, supplier, or plot complies with the Regulation.

Use the benchmark as one input in the EUDR due diligence file. The starting question remains whether the product is a relevant commodity or relevant product under Annex I and whether it can meet the Article 3 conditions: deforestation-free, produced in accordance with relevant legislation of the , and covered by the required due diligence statement or simplified declaration.

  • Low risk: may support for products produced in that country or part of a country, if the operator also checks supply-chain complexity and circumvention or mixing risk.
  • Standard risk: does not create the low-risk simplification; ordinary information collection, risk assessment, and risk mitigation logic remains relevant.
  • High risk: should be treated as a stronger risk signal in the operator's assessment and controls, not as a reason to skip product-level evidence.
EUDR country benchmarking FAQ: low, standard, and high risk

How does low-risk benchmarking affect simplified due diligence?

For relevant products produced in a country, or part of a country, classified as low risk under Article 29, Article 13 can relieve operators from the Article 10 risk assessment and Article 11 risk mitigation steps. That relief is conditional: the operator must still assess supply-chain complexity and the risk of circumvention or mixing with products from other origins, and must be able to show documentation demonstrating negligible risk.

Low-risk status therefore narrows the due diligence work only after the operator has confirmed the production origin and checked for mixing or circumvention. It should not be used as a blanket rule for every supplier invoice, warehouse lot, or product batch connected to the country.

If relevant information or a substantiated concern points to non-compliance or circumvention, Article 13(2) requires the operator to carry out the Article 10 assessment and Article 11 mitigation and immediately communicate the relevant information to the competent authority. Keep the concern, authority notification, assessment and outcome with the affected product records; the low-risk country label does not preserve simplification in that case.

  • Confirm the relevant product was produced in the low-risk country or part of a country, not merely shipped from it.
  • Check whether the supply chain mixes origins, commodities, plots, establishments, or batches in a way that could undermine the low-risk conclusion.
  • Keep documentation that explains why the operator treated the risk of circumvention or mixing as negligible.
EUDR country benchmarking FAQ: low, standard, and high risk

What must still be collected even when production is low risk?

Low-risk benchmarking does not remove Article 9 information collection. Operators still need information and evidence for the relevant product, including production origin, geolocation of plots or establishments where required, and documentation showing the product is deforestation-free and produced in accordance with relevant legislation of the .

The operator also still needs the required EUDR submission route. The Regulation describes due diligence statements through the Article 33 information system, and simplified declarations for micro or small primary operators where the amended Regulation allows them. Downstream operators and traders still need the required supply-chain information, including due diligence statement reference numbers or declaration identifiers when those apply.

  • Product and commodity identity, including whether the product is listed in Annex I.
  • Country or part of , backed by production-origin evidence rather than shipping-origin assumptions.
  • Geolocation or permitted substitute information where the Regulation allows it for a specific actor.
  • Documentation showing deforestation-free status and production in accordance with relevant legislation in the .
  • Due diligence statement reference numbers, declaration identifiers, supplier details, and downstream recipient details where the actor's role requires them.
EUDR country benchmarking FAQ: low, standard, and high risk

Which countries are low, standard, or high risk?

Use Commission Implementing Regulation (EU) 2025/1093 for the current low- and high-risk lists. Its Annex lists, for example, Germany, the United States, China, and Ghana as low risk; Belarus, the Democratic People's Republic of Korea, Myanmar, and the Russian Federation are the high-risk countries. Brazil is not on either list and therefore remains standard risk under Article 1(2). These are classifications under that act, not permanent labels.

Because the Commission may review and update the list when new evidence warrants it, record the act and date checked rather than copying an unversioned country tier into a supplier record.

Match the benchmark to the country or part of country where the commodity was produced, not the supplier's address, exporter location, or port of shipment. Then document the product origin and any mixing or circumvention risk before relying on low-risk .

  • Record the official implementing act, date checked and classification next to each production country in the product file.
  • Record whether the classification applies to the whole country or only to a part of it.
  • Separate production origin from supplier location, exporter location, and port of shipment.
  • Refresh benchmark evidence before relying on low-risk for a new product, supplier, or origin path.
EUDR customs and import release

What should teams do before customs or import release under the EUDR?

Do not wait for the customs broker or import filing to discover an EUDR gap. Before a relevant product is placed on the EU market or exported, confirm that the product is in the EUDR scope, that the operator has completed due diligence or the applicable simplified declaration route, and that the release file includes the reference number or declaration identifier needed for the shipment.

Article 26 requires the reference number, or the declaration identifier for an eligible micro or small primary operator, to be made available to before or export. Except where the statement is supplied through the Article 28 electronic interface, the person lodging the customs declaration provides that identifier. Article 26(4) excludes exports by downstream operators from this paragraph; the exclusion does not remove their separate Article 5 duties.

  • Confirm the relevant product and commodity are in the EUDR scope before the shipment is approved for release.
  • Record whether the party responsible is acting as operator, downstream operator, trader, importer, authorised representative, or customs broker support.
  • Require the reference number or applicable declaration identifier before or export, subject to the downstream-operator export exception in Article 26(4).
  • Keep the evidence file separate from the customs filing so teams do not mistake a reference number for proof that the underlying due diligence is complete.
EUDR customs and import release

How should teams handle due diligence statement references?

The EUDR reference number is a handoff control. Operators submit the through the Article 33 information system after due diligence shows no or negligible risk, then communicate the reference number to downstream operators and traders further down the supply chain. Where a micro or small primary operator uses a simplified declaration route, the handoff should capture the declaration identifier instead.

For import release, match the reference or declaration identifier to the supplier, product, and customs movement. Before the Article 28 electronic interface is in place, customs and competent authorities exchange information under Article 27. Once the interface is in place, use it to examine the status assigned to the statement. A status requiring checks can suspend release; a competent-authority finding of non-compliance prevents release.

  • Capture the EUDR reference or declaration identifier as a required shipment-readiness field.
  • Link the identifier to the supplier record, product line, EUDR role, and due diligence evidence file.
  • Escalate missing, mismatched, duplicated, or unexplained identifiers before release instructions are issued.
  • Do not rewrite the after customs clearance just to fit a shipment file; correct the underlying EUDR record first.
EUDR customs and import release

What should operators, importers, and brokers hand off to each other?

The handoff should be explicit about roles. The operator remains responsible for compliance when it makes a available, even if an authorised representative submits the statement on its behalf. Downstream operators and traders need supplier information and, where the supplier is an operator, the due diligence statement reference number or declaration identifier.

Customs brokers can help enforce release readiness, but they should not be made the owner of EUDR due diligence unless they hold that legal role. Give brokers the identifiers and release instructions they need; keep product scope, supplier evidence, geolocation evidence, risk assessment, mitigation, and authority-response ownership with the EUDR compliance owner.

  • Operator to importer or downstream recipient: EUDR role, covered product, reference number or declaration identifier, and evidence-file owner.
  • Importer or downstream recipient to broker: release instruction, matched identifier, hold/release status, and escalation contact for EUDR exceptions.
  • Broker to importer: confirmation that the provided identifier was used as instructed and any customs authority query was returned to the EUDR owner.
  • EUDR owner to procurement and logistics: stop-release rules for missing identifiers, substantiated concerns, or unresolved supplier evidence gaps.
EUDR customs and import release

What evidence should the release file retain?

Keep the collected information, submitted statement or simplified declaration, and identifier handed to downstream parties. Where Articles 10 and 11 apply, include the assessment and any mitigation; where Article 13 simplified due diligence applies, retain the production-origin, supply-chain complexity, circumvention and mixing checks that support it.

Retention should cover both the customs-release event and the EUDR evidence behind it. Operators keep records for five years, and downstream operators and traders keep their Article 5(3) supply-chain information for at least five years. The wider file includes Article 9 information and evidence such as geolocation and documentation demonstrating deforestation-free and legal production.

  • Product and supplier identity used for the release decision.
  • reference number or simplified declaration identifier.
  • Evidence that the product is deforestation-free and produced in accordance with relevant legislation of the country of production.
  • Geolocation or establishment information required for the applicable EUDR route.
  • Article 10 assessment and Article 11 mitigation where required, or the Article 13 simplification record; unresolved-risk escalation and the resulting hold decision.
  • Release hold, approval, or authority-query log tied back to the EUDR evidence owner.
EUDR customs and import release

Does customs release prove EUDR compliance?

No. Article 26(10) states that or export is not proof of compliance with Union law or the EUDR. Customs release confirms that the applicable customs conditions allowed the movement at that point; the operator still needs the due diligence evidence supporting Article 3 compliance.

Keep the identifier and customs outcome with the evidence file. If competent authorities identify the product for checks, suspend release under Article 26. If competent authorities conclude that it is non-compliant, customs authorities must not release it.

  • Before the broker files, agree which official customs instruction identifies the required EUDR reference field, who supplies the identifier, and who resolves a rejected or mismatched entry.
  • Do not accept a bare reference number without matching it to the supplier, product, shipment, and EUDR evidence file.
  • Do not let the broker become the evidence owner when the legal responsibility sits with the operator, downstream operator, or trader.
  • Do not release products when new information or substantiated concerns require verification before placing, making available, or exporting.
EUDR DDS Reference Numbers: What to Record and Pass Down

What does an EUDR DDS reference number support?

A DDS reference number supports traceability after an operator has completed the EUDR due diligence sequence and made the due diligence statement available through the Article 33 information system. The system assigns a reference number for each submitted due diligence statement. For micro or small primary operators using the simplified route, the parallel handoff is the assigned after the one-time declaration.

Use the number to link three things that are often held in different systems: the supplier or operator that made the EUDR filing, the relevant product or shipment record, and the downstream recipient that needs the reference to keep its own Article 5 information file.

  • Operator filing: keep the due diligence statement record and its reference number together.
  • Downstream handoff: pass the DDS reference number, or where applicable, to downstream operators and traders further down the supply chain.
  • Recipient record: keep supplier and downstream-recipient details. Article 5(3)(a) requires the DDS reference number or only when the immediate supplier is an operator.
  • Authority response: keep the record usable for competent-authority requests instead of burying the number in email threads or shipment notes.
EUDR DDS Reference Numbers: What to Record and Pass Down

How should downstream operators, traders, and customs handoffs record DDS references?

When the immediate supplier is an operator, downstream operators and traders must record its details and the DDS reference number or before placing, making available, or exporting the product. When the immediate supplier is a or trader, Article 5(3)(a) requires supplier details but does not require collection of that identifier.

For customs, export, logistics, and broker handoffs, carry the same EUDR reference field on the movement record and tie it back to the product line. Article 26 normally requires the reference number or before release for free circulation or export, but excludes exports by a from that paragraph. Keep the control focused on the official identifier unless an official filing output or broker instruction requires an additional field.

  • Store the supplier legal name and contact details with the EUDR reference field.
  • Record whether the field is a or a simplified .
  • Map the reference to the product, commodity, lot, purchase order, shipment, export file, or customs broker handoff it supports.
  • Keep downstream-recipient details for Article 5 traceability, even where collecting the upstream reference number is not required.
  • Escalate missing, mismatched, or unexplained references before relying on the shipment or sales record as EUDR evidence.