EUDR due diligence statement example
EUDR due diligence statement: Annex II fields, with an illustrative example
Direct answer. Under Regulation (EU) 2023/1115 Article 4, operators must not place relevant products on the market or export them without first submitting a due diligence statement through the information system in Article 33. That statement must contain the information in Annex II plus a declaration that due diligence found no or only a negligible risk. The table below is an illustrative reading aid of those Annex II headings — not a real statement, not a filing form, and not a substitute for the Information System. This page is not legal advice.
EUDR Records Manager (Shopify App Store · Write a review) keeps a supplier and commodity-lot registry with DDS reference numbers per product, flags missing supplier, country or DDS fields, and retains an audit trail of supplier, lot, document and export changes. It does not file the due diligence statement in the EU information system. Storing the reference you received is EUDR DDS lot registry.
Related: CRALedger Duty Records — CRA duty records before an Article 14 incident. Does not file ENISA notifications.
Free check first: EUDR product scope check runs in your browser and sends nothing. Type a product or HS code and see which EUDR Annex I lines it may touch.
What the regulation says a statement contains
Article 4(2) of Regulation (EU) 2023/1115 as consolidated requires an electronically available statement with the Annex II information and a declaration that the operator exercised due diligence and that no or only a negligible risk was found. Operators keep a record of those statements for five years from the date of submission. Confirm the live articles, including amendments, before you treat any SKU as in scope. Dates and roles are on who is in scope on 30 December 2026 vs mid-2027.
Annex II currently lists, in paraphrase:
- Operator name, address, and (when products enter or leave the market) the EORI number
- Harmonised System code, free-text description including the trade name and, where applicable, the full scientific name, and quantity
- Country of production and the geolocation of all plots of land where the relevant commodities were produced (with the cattle-establishment rule in the same point)
- The confirmation text set out in Annex II
- A signature block in the format Annex II specifies
Read the live Annex II text; this list is a reading aid. A later amendment struck a former Annex II point, so numbering on older copies may not match the current annex.
Illustrative example — not a filing
Illustrative only. The values below are invented for reading Annex II. They are not a real operator, product, plot, EORI, or statement. Do not submit them. Filing happens only in the Commission Information System.
| Annex II heading | Illustrative value (not real) |
|---|---|
| Operator name and address; EORI if entering or leaving the market | Example Operator Ltd, 1 Example Street, 1000 Example City. EORI: XX000000000000 (placeholder) |
| HS code, description, trade name, scientific name where applicable, quantity | HS 0901 (illustrative heading only — confirm Annex I); roasted coffee, trade name “Example Blend”; quantity expressed as required for that code |
| Country of production and geolocation of all plots | Example country; plot geolocation supplied in the Information System (map, coordinates, or GeoJSON), not as a storefront string |
| Confirmation text (Annex II wording) | “By submitting this due diligence statement the operator confirms that due diligence in accordance with Regulation (EU) 2023/1115 was carried out and that no or only a negligible risk was found that the relevant products do not comply with Article 3, point (a) or (b), of that Regulation.” |
| Signature block | Signed for and on behalf of / Date / Name and function / Signature — completed in the Information System, not on this page |
The Information System, not this table, assigns a reference number (and a verification number) after submission. Downstream actors keep that reference; they do not paste this example into a customs field.
Where the official Information System guidance lives
The Commission describes the Information System as a TRACES tool in which operators and authorised representatives create and submit due diligence statements and simplified declarations. Official pages to open:
- The Information System of the Deforestation Regulation — production vs acceptance servers, geolocation options, dashboard, API note, and the user guide link
- Understand due diligence — points to Annex II as the DDS template and to the Information System guide
- Commission Implementing Regulation (EU) 2024/3084 — functioning of the Information System, including assignment of a reference number and a verification number
The Green Forum Information System page states that submissions on the production server have legal value and can be checked by competent authorities, and that the acceptance server is for training and testing only. This website is neither server.
Storing a reference is not filing a statement
Operators submit the statement in the Information System and receive a reference number. Downstream operators and traders keep the reference they received. A catalog lot registry stores SKU or lot, supplier, country, and that reference. EUDR Records Manager stores records you enter; it does not file a statement or replace the Information System. Start path: store the DDS reference against each supplier lot.
What this page is not
- Not a real due diligence statement, not a filing form, and not access to the Information System.
- Not legal advice, a role determination, or a decision that a SKU is a relevant product under Annex I.
- Not the lot-registry start path. That is DDS reference numbers on supplier lots.
- Not the 2026 versus 2027 scope split. That is who is in scope on which date.
Related pages
- EUDR product scope check — type a product or HS code
- EUDR DDS lot registry — store the reference against each lot
- EUDR scope: 30 December 2026 vs mid-2027
- Weekly EUDR gap review
- Regulation (EU) 2023/1115
- Commission Information System guidance
- EUDR Records Manager — live App Store listing
- Shopify apps hub
- Tools
Not legal advice. Not a compliance guarantee. Not a DDS filing. The example on this page is illustrative only. Confirm Regulation (EU) 2023/1115 as amended, Implementing Regulation (EU) 2024/3084, and the live Commission Information System pages before you treat a statement as complete. The app stores lot and DDS records you enter; you choose what to record.