In short
- The core dataset is geolocation of the plots of land, evidence of legal production in the country of production, and a documented risk assessment and mitigation.
- There is no emissions field anywhere in it. EUDR never asks for a tonne of CO2e.
- A downstream operator's dataset is one field: the due diligence statement reference number or declaration identifier from upstream.
Four things, and none of them is a carbon number. An operator's file rests on the geolocation of the plots of land where the commodity was produced, evidence that production complied with the law of the country of production, a documented risk assessment and risk mitigation, and a due diligence statement filed in the EU information system. A downstream operator's file is far smaller: for the first one in a chain, the reference numbers of somebody else's due diligence statements, or the declaration identifiers. Which list you are working from is decided by your role, not your size.
What does an operator actually have to hold?
Four data objects, and the first is the hard one.
Geolocation of the plots of land. Not a country, not a region, not a supplier address. Coordinates for the land where the commodity was produced. This is what makes EUDR a supply chain data project rather than a compliance form. It has to come from counterparties, sometimes several tiers upstream, and for tree crops it may relate to a growing season that has already closed.
Evidence of legal production. Proof that production complied with the law of the country of production. That is documentary evidence from a jurisdiction whose paperwork conventions you may not control or read.
A documented risk assessment and risk mitigation. Documented is the operative word. The reasoning has to be written down and reproducible, not held as a judgement somebody made once.
The due diligence statement itself, filed in the EU information system, which is what converts the file into a permission to place the product on the market.
What does a downstream operator have to hold?
Almost nothing, and this is the most useful thing on the page for an EU manufacturer.
Since Regulation (EU) 2025/2650, downstream operators and traders are not required to submit due diligence statements, and are not required to ascertain that due diligence was exercised. Two administrative duties remain. Those above SME size must register in the EU information system before placing products on the market. The first downstream operator or trader in a chain, of any size, must collect and keep the reference numbers of the due diligence statements or the declaration identifiers.
So the dataset is a field on a goods receipt. The engineering problem is not gathering it; it is making sure your purchase-to-pay process retains it rather than discarding it on the way through, and that you can produce it later against the shipment it belongs to.
Which dataset does your role point to?
| Data item | Operator | Downstream operator, first in chain | Downstream operator or trader, not an SME |
|---|---|---|---|
| Plot geolocation | Required | Not required | Not required |
| Legality evidence from country of production | Required | Not required | Not required |
| Documented risk assessment and mitigation | Required | Not required | Not required |
| Due diligence statement filed in the information system | Required | Not required | Not required |
| DDS reference numbers or declaration identifiers, kept | Generated by you | Required | Required if also first in chain |
| Registration in the EU information system | Required as an operator | Only if not an SME | Required |
| Any greenhouse gas figure | Not required | Not required | Not required |
The last row is not padding. It is the row people are most surprised by, and the one that most often gets a carbon project attached to a deforestation budget.
Is any of this an emissions dataset?
No. There is no emissions field anywhere in the requirement.
EUDR creates no greenhouse gas accounting obligation of any kind. It asks for coordinates, legality, documented reasoning and a statement. Greenhouse gases appear only in the recitals, as the reason the legislature acted.
Where the confusion comes from is genuine, though, and it is worth being precise about it. The two datasets share a source. Ingredient purchase data at supplier and origin level is the raw material for both a scope 3 category 1 footprint and an EUDR file. Once you know which mill or which plot a batch of cocoa or palm oil came from, you can defend a specific emission factor for that ingredient instead of a national average or a spend proxy. The traceability is reusable. The obligation is not, and nothing in EUDR obliges you to do the second piece of work.
Where does the data come from, and how long does it take?
Four sources, and they arrive on very different timescales.
| Source | What it gives you | Realistic lead time |
|---|---|---|
| Your own purchase ledger | Which product lines contain covered commodities, and which supplier each came through | Days. It is already in the ERP |
| Direct suppliers | The role question answered: did they already file, and can they give you a reference number | Weeks, and it is a conversation not a form |
| Upstream tiers and origin | Plot coordinates and legality documentation | Months, and it is season-dependent |
| The EU information system | Registration, statement filing, reference numbers | Process time, once the rest exists |
That ordering is the plan. The purchase ledger tells you which lines are even in question. The direct supplier conversation tells you whether you are an operator or downstream of one, and therefore whether the third row is your problem at all. Most companies discover at row two that the expensive part belongs to somebody else.
What does good evidence look like?
Reproducible, attributable and dated, which is a higher bar than most carbon data is held to.
An emissions figure survives on method: state your factors and your boundary and a reader can follow the arithmetic. A deforestation file has to survive as a set of documents about specific land and specific consignments. The question it answers is not "is this number reasonable" but "which plot, and can you show me". That means version control, a link between each document and the shipment it supports, and a record of when you checked what.
The practical consequence for tooling: a carbon platform is built for the first kind of evidence and not the second. Do not assume the audit trail transfers. On our own platform, a mid-market reviewer on G2 in July 2026 noted that applied conversion factors and distance calculations are not exposed to the user, so a customer cannot always trace how an input became an entry. That is a fair observation about a carbon tool, and it is exactly the property that would be unacceptable in a legality evidence file. Different jobs, different systems.
What should you collect first?
One product line, traced backwards.
Pick your largest line containing cattle, cocoa, coffee, oil palm, rubber, soya or wood, and check it against Annex I as amended by Delegated Regulation (EU) 2026/2102. That act took cattle hides, skins and leather off the list in September 2026, and soluble coffee and a list of palm oil derivatives join it from 30 December 2027. Follow the line back to the point at which it entered the EU. If that point is you, the plot-level dataset above is your project and the lead time is the reason to start now. If somebody upstream did it, ask them for the reference number today and see what comes back. The answer to that one email is worth more than a scoping study.
Then check the calendar honestly. The obligations apply from 30 December 2026, and from 30 June 2027 for operators that were micro or small undertakings by 31 December 2024, with former timber regulation products excluded from that deferral. If your notes carry an earlier date, they were written against a superseded version of Article 38.
If the ingredient data you dig up on the way is also meant to feed a footprint, that second job is scope 3 consulting or a build on the Hedgehog platform, which reports 5,000+ users. Sequence it after the traceability, not before, because the supplier-specific factors are the entire point. If a customer is pressing you for both at once, the value chain cap on ESG questions sets out what can reasonably be demanded of you.
Sources: Regulation (EU) 2023/1115, Regulation (EU) 2025/2650 and Delegated Regulation (EU) 2026/2102 as published in the Official Journal, and the European Commission EUDR page. Hedgehog facts from the Hedgehog platform and Hedgehog on G2. Verified 22 November 2026.
Facts on this page were last verified on 2026-11-22.


