What did EUDR simplification actually change?

Do traders still need to submit a DDS?

Under the amended rules, traders and downstream operators do not submit their own DDS for that downstream activity. Non-SME businesses in these roles still register in the Information System. All retain the required supplier and business-customer records; the first downstream recipient also keeps the upstream DDS reference or declaration identifier. The Commission’s role guidance explains these distinctions and the duties to act on possible non-compliance.

A business that calls itself a trader may also import products and first place them on the EU market. Treat those transactions separately. Use the operator, downstream operator and trader definitions to establish its role before removing a submission step.

One supply chain, different records

Consider a fictional importer selling covered coffee to a distributor, which resells it unchanged to a retailer. Assume the importer is the upstream operator and the other two businesses act as traders.

Importer

Carries out the operator’s due diligence and supplies the statement reference with the relevant goods.

Distributor

Keeps the reference received directly from the operator, alongside the required supplier and business-customer information.

Retailer

Keeps the required trading records. The first-recipient reference-collection duty is not repeated at every later resale.

In operational terms, the distributor needs a reliable link between incoming goods, the supplier and the reference. The retailer needs retrievable trading records. Building three identical DDS submission pipelines would solve the wrong problem. This example illustrates the Commission’s downstream traceability explanation; processing, mixed activities or different sourcing can change the role analysis.

A simplified declaration is not a lighter DDS for every SME

The simplified declaration route is for qualifying micro or small primary operators: broadly, eligible producers established in a low-risk country who themselves produce the relevant commodities there. Buying and reselling someone else’s products does not establish that eligibility.

Article 4a introduces a one-time declaration and a declaration identifier, with provision for updates after major changes and a specific equivalent-database exception. It also permits qualifying operators to use production-location postal addresses instead of geolocation. These are targeted changes, not general concessions for all small businesses. See Regulation (EU) 2025/2650, Articles 2(15a) and 4a as inserted.

Keep simplified declaration separate from simplified due diligence. The latter concerns the low-risk sourcing conditions in Article 13; it is not a form that replaces every DDS. The due diligence requirements explain the evidence and risk work behind a filing.

What still needs to work

Covered products must still meet the deforestation-free and legality conditions. Simplification changes who files and what some businesses retain; it does not turn a system reference into proof that the underlying goods comply. Article 3 remains the product-level test in the consolidated EUDR.

• Classify the goods. Check the actual product against Annex I, including the wording of any limited entry. The HS/CN lookup helps locate the relevant entry.
• Preserve the connection to the transaction. A reference in an email is difficult to use later if nobody can tell which goods it covers. Store it with the relevant supplier, product and internal record.
• Give exceptions an owner. Missing information, inconsistent goods descriptions and new concerns need a review route. Removing a form should not remove that route.

Separate the legal change from the software change

Adoption, application and technical availability are different milestones. The 2025 amendment changed the legal framework; the application dates and qualifying-business exceptions determine when obligations apply. An updated screen or API specification does not move those dates.

When changing an integration, check the Commission’s V2-to-V3 migration documentation against the interface you actually use. Keep legal-role decisions separate from API role names, form availability and historical test labels. The TRACES API integration guide covers that technical boundary.

Which parts of your workflow should change?

Map each transaction to its role, identify the information it must produce or retain, and compare that with today’s process. Keep the useful controls; remove only the work that no longer serves an obligation or a genuine operational need. We can help turn that comparison into a bounded EUDR implementation scope.

Reviewed 7 September 2026. This guide explains the role and filing changes, not every technical amendment. Check the linked legislation for the full conditions; this is not legal advice.