Quick summary: Understand EUDR Simplified Declaration eligibility, required information, declaration identifiers and practical examples for coffee, cocoa, rubber and timber producers.
The EUDR Simplified Declaration (SD) is a one-time submission route in the EU Deforestation Regulation (EUDR) Information System for eligible micro or small primary operators. Rather than submitting a separate Due Diligence Statement (DDS) for every relevant shipment, an eligible operator can submit a declaration covering the relevant products it produced itself, subject to the applicable conditions. The Information System assigns a declaration identifier that follows the relevant products through the supply chain.
The simplified route is designed to reduce repetitive reporting for a specific group of producers not to remove the underlying EUDR requirements. Eligibility, accurate production information and the ability to connect the declaration identifier to relevant products remain essential.
Eligibility depends on the operator’s status, location and production activity. Current EUDR Information System documentation describes the route for a natural person or micro/small undertaking established in a low-risk country that places relevant products on the market or exports products it produced itself in that country. An authorised representative may submit on behalf of an eligible operator when the relevant conditions, including a written mandate, are met.
This distinction matters in practice. A small coffee farmer producing coffee on their own farm may qualify if all conditions are satisfied. A small trader buying coffee from dozens of independent farms and reselling it does not qualify simply because the business is small. Confirm the operator role and the current country-risk classification before relying on the simplified route.
The SD must contain the information specified in Annex III and the applicable Information System rules. Depending on the activity and product, this can include operator and activity details, relevant commodity and product information, country of production, product or HS classification, quantities, and production-location details. The exact fields depend on the applicable requirements and the circumstances of the operator.
A notable difference is the production-location format. Current Information System documentation allows an SD to use GeoJSON geometry, postal address(es) or cadastral identifier(s). This flexibility can help eligible producers who do not already maintain geospatial files. It does not remove the need to identify the relevant production location accurately.
Read our guide to EUDR due diligence to understand the key requirements, avoid common compliance gaps, and discover how TraceX helps streamline supplier data management, risk assessment, traceability, and DDS preparation.
A micro or small coffee producer established in a low-risk country grows and exports its own coffee. If the producer meets the eligibility conditions, it may submit one SD covering its relevant products rather than preparing a separate DDS for every shipment. The declaration identifier can then be linked to the producer’s relevant coffee products and trade records. This reduces repetitive submissions, but accurate producer and product data are still needed.
An eligible cocoa producer supplies an EU chocolate manufacturer several times a year. The buyer should capture the SD identifier and connect it to the relevant cocoa purchases and product records. If important information in the declaration changes, the producer should assess whether an update is required. The buyer should not assume that a declaration identifier alone replaces every other applicable traceability or due diligence responsibility.
A small rubber producer harvesting rubber from its own production areas may qualify if the conditions are met. A similarly sized trader buying rubber from other producers is not automatically eligible. The difference is the operator’s production relationship and role—not company size alone. This is why eligibility checks should happen before a business designs its reporting process around an SD.
A small forestry business or sawmill may be able to use the simplified route if it meets the legal eligibility conditions. However, the declaration does not waive the substantive EUDR conditions for wood, including the relevant deforestation-free and legality requirements. A simplified reporting process is not an exemption from the underlying regulation.
An eligible producer with limited capacity to use the Information System may work with an authorised representative where permitted and under a written mandate. A practical workflow is: producer data collection → eligibility check → SD submission → declaration identifier → buyer and shipment records. Responsibilities and access to the supporting information should be agreed clearly.

The declaration identifier generated for an SD and a DDS reference number relate to different declaration routes. Downstream businesses should not assume every relevant product will arrive with a DDS reference. Their systems and procedures should be able to capture the appropriate identifier, link it to the relevant product and transaction, and make it available to the parties who need it.
Learn how to manage DDS reference numbers, link declarations to relevant shipments and transactions, and maintain accurate compliance records across your supply chain.
A digital traceability workflow can help organise producer and product data, validate required fields, maintain production-location records and connect declaration identifiers to purchases and shipments. For organisations working with many suppliers, this can reduce repeated manual entry and make it easier to retrieve the relevant information. The value depends on the platform’s actual functionality and how well it fits the organisation’s existing processes.
TraceX supports digital traceability and EUDR data workflows that help businesses organise supplier, product, production-location and shipment information. To evaluate fit, ask for a demonstration using a representative producer-to-shipment scenario, including how eligibility, data gaps, identifier capture and updates are handled. Software can support the process; it does not guarantee compliance or replace the operator’s responsibilities.
The EUDR Simplified Declaration can reduce repetitive reporting for eligible micro or small primary operators, especially producers with recurring sales. The process still depends on confirming eligibility, preparing accurate information, keeping the declaration current when required, and connecting the declaration identifier to relevant products and trade flows. Businesses should validate their position against the current EUDR rules and Information System guidance before using the simplified route.
Not every small business qualifies for a simplified declaration,eligibility depends on the applicable operator status, establishment in a low-risk country, and producing the relevant products itself, among other relevant conditions. A small trader is not automatically eligible.
For eligible operators using the simplified route, the SD replaces the per-shipment DDS approach described in the current Information System guidance. It is not a universal alternative available to every operator.
Current Information System guidance allows an SD production location to be represented by GeoJSON geometry, postal address(es) or cadastral identifier(s), subject to the applicable requirements.
If information changes after submission it may require an update. Operators should monitor relevant information and consult current Information System rules to determine when an update is necessary.
No,the identifier links products to the declaration record; it is not, by itself, proof that every applicable EUDR obligation has been met. The relevant requirements and responsibilities still apply.