The EU Deforestation Regulation (EUDR) rests on a single foundational idea: every commodity placed on the European Union market must be traceable to the precise plot of land where it was produced. Without that link, there is no way to prove deforestation did not occur after 31 December 2020, the regulation's hard cut-off date.
Geolocation is therefore not a data-management technicality. It is the legal bedrock of EUDR compliance. Operators who cannot collect, verify, and submit accurate geographic coordinates cannot legally place regulated products on the EU market or export them from it.
This guide covers every dimension of the geolocation requirement in plain terms: what data you need, how to collect it, what the polygon and point rules actually mean, the obligation to verify accuracy, and how satellite-based tools support the process at scale.
What is the EUDR geolocation requirement?
Article 9 of the EUDR requires operators and non-SME traders to collect, as part of their due diligence, the geographic coordinates of all plots of land where the relevant commodities that make up a product were produced.
Those coordinates must be included in every Due Diligence Statement (DDS) submitted to the EU Information System before a product is placed on the market or exported. If geolocation information has not been collected and submitted, the operator is prohibited from proceeding, PERIOD.
The seven regulated commodity groups subject to these requirements are: cattle, cocoa, coffee, palm oil, soya, wood, and rubber, along with a wide range of derived products (leather, chocolate, furniture, paper, tyres, and others listed in Annex I of the Regulation).
Geolocation traceability is required for every batch. It applies to imports, exports, and transactions within the EU single market, and covers both bulk-traded and composite products.
Polygons vs. single points: understanding the rules
The Regulation distinguishes between two acceptable formats for geolocation data, based on plot size:
Plots larger than 4 hectares
Geolocation must be provided using a polygon, a series of latitude and longitude coordinates that trace the perimeter of the plot. Each coordinate must be expressed to six decimal digits (e.g., 48.123456° N, 11.654321° E). A polygon describes one single plot of land, whether that plot is a contiguous area or not. Where multiple plots contribute to a single product batch, all polygons must be included in the same DDS.
Plots of 4 hectares or less
Operators may use either a polygon or a single geolocation point (one latitude and one longitude coordinate, again to six decimal places). The flexibility is designed to reduce the burden on smallholder-dominated supply chains, where the majority of plots typically fall below the threshold.
Cattle establishments
For products derived from cattle, the geolocation requirement is different: operators provide the coordinates of every establishment where the cattle were kept, not a production plot polygon. A single-point coordinate per establishment is sufficient.
File size limits
The EU Information System accepts polygon data with no fixed cap on the size of an individual polygon or the number of polygons per DDS. However, the total file size of a single DDS submission cannot exceed 25 MB. For operators with highly fragmented supply chains, this may require batching submissions.
How to collect geolocation data
The Regulation is deliberately technology-neutral on collection method. What matters is accuracy and verifiability, not the tool used to gather the data. In practice, the following methods are accepted:
- Mobile devices with GNSS capability, smartphones and tablets can collect GPS/Galileo coordinates directly in the field. No mobile network coverage is required, only a stable satellite signal.
- Handheld GNSS devices, purpose-built units provide higher positional accuracy and are well-suited to remote areas.
- GIS applications, desktop or cloud-based Geographic Information System software allows operators and their suppliers to digitize existing land boundaries from aerial imagery or cadastral data.
- Cooperative and certification systems, many cooperatives, certification bodies, and national traceability platforms already collect and store farm-level geodata; operators can draw on these where available.
There is no requirement for farmers or producers in third countries to hold formal land titles or be registered in a property system. If a producer is legally permitted to cultivate and sell under their domestic law, the absence of a formal title does not disqualify their geolocation data from being used. The geolocation of the plot itself, not proof of legal ownership, is what must be provided.
Who is responsible for accuracy?
This is one of the most commercially important aspects of the geolocation rules: the operator is responsible for accuracy, regardless of who collected the data.
An operator may rely on coordinates supplied by a producer, cooperative, or intermediary, but cannot transfer legal liability by doing so. If the submitted geolocation is incorrect, the operator is in breach of the Regulation. This creates a direct compliance obligation to verify, not simply pass through, whatever data comes from the supply chain.
Operators are therefore required to:
- Verify that the coordinates correspond to the actual plot where the commodity was produced.
- Be able to demonstrate that the geolocation is correct if requested by a Competent Authority.
- Support smallholder suppliers where needed, including through capacity building and investment in mapping tools, as one recognized form of risk mitigation under Article 11.
Verification: how geolocation claims are checked
The Regulation's enforcement mechanism is built on cross-referencing submitted geolocation data against satellite imagery and forest cover maps. EU Member State Competent Authorities (CAs) are explicitly authorized to:
- Cross-check DDS coordinate submissions against satellite images and reference forest maps to assess whether the declared plots are deforestation-free as of 31 December 2020.
- Conduct checks in third countries when a product is flagged as potentially non-compliant.
- Use remote sensing data (aerial photography, multispectral satellite imagery) to verify that production did not occur on deforested land.
This means geolocation coordinates are not just administrative entries, they are live, verifiable data points that can be cross-referenced at any time against publicly available deforestation maps and satellite time-series. Submitting incorrect coordinates is therefore not a low-risk act; it is a detectable breach.
For operators, the implication is clear: internally verifying coordinates before submission, including comparing them against satellite-derived forest cover and deforestation change maps, is not optional good practice. It is a core part of the due diligence obligation.
Mass balance is not permitted
The EUDR prohibits mass balance chains of custody. All products placed on the EU market or exported must consist entirely of deforestation-free commodities that have been traced to specific, verified plots. Mixing deforestation-free commodities with commodities of unknown origin at any step in the supply chain breaks the chain of compliance.
Full identity preservation is not required, but full segregation of compliant from non-compliant or unknown-origin commodities is. For operators handling high-volume, bulk-traded commodities such as soy, palm oil, or cocoa, this significantly raises the bar on supply chain data management.
Downstream operators and reference DDS
Not every operator in the supply chain must collect geolocation from scratch. The Regulation provides an efficient mechanism for downstream non-SME operators and non-SME traders:
- If a product has already been subject to upstream EUDR due diligence and the upstream operator has submitted a DDS to the Information System, the downstream operator may reference that upstream DDS (using its reference number and verification number) instead of re-collecting all the underlying Article 9 data.
- The downstream operator must still submit their own DDS, ascertain that upstream due diligence was properly exercised, and retain the obligation not to place the product on the market if they have reason to believe it is non-compliant.
SME operators and traders further downstream are not required to collect the underlying geolocation information, their obligation is to pass on the DDS reference numbers to their own customers.
The smallholder challenge
For supply chains with large numbers of smallholder producers, particularly in cocoa, coffee, rubber, and palm oil from Southeast Asia, West Africa, and Latin America, geolocation collection is the most operationally complex element of EUDR compliance.
Several factors compound the challenge:
- Lack of digitized farm records: Many smallholders have no formally registered plot boundaries, let alone digital coordinates.
- Plot sizes below the 4-hectare threshold: The single-point option simplifies the data format but still requires the GPS coordinate to be collected in the field.
- Intermediary layers: Commodities often pass through multiple traders and aggregators between farm and exporter, making it difficult to maintain traceability.
- Legal status of land: In many producing countries, smallholders cultivate land without formal title, raising both legality and traceability questions that must be resolved by the operator.
The Regulation acknowledges these realities. Operators are encouraged to invest in capacity building and direct farm mapping as risk mitigation. It also explicitly states that where domestic law does not require a land title to legally produce and sell, the absence of a title is not a disqualifier for EUDR compliance.
How satellite intelligence strengthens geolocation compliance
Satellite remote sensing is both a verification tool used by regulators and a compliance enabler for operators.
For operators building EUDR-compliant supply chains, integrating satellite intelligence into their geolocation workflows enables:
- Historical deforestation analysis: Cross-referencing submitted plot coordinates against time-series forest cover data (including historical maps from 2000 onward) to assess whether a plot was forested before 31 December 2020 and whether clearing occurred after that date.
- Plot boundary validation: Comparing collected GPS coordinates against high-resolution satellite imagery to confirm that declared coordinates correspond to the actual area of production, not a nearby field or forest patch.
- Ongoing monitoring: Tracking declared plots across crop seasons to detect any new land conversion activity.
- Risk tiering: Flagging high-risk sourcing geographies and prioritizing verification resources accordingly, based on deforestation prevalence, land tenure fragility, and satellite-detected change signals.
Cropin's enterprise intelligence platform applies exactly this logic. Its historical deforestation analysis capability cross-references plot-level geolocation data against multi-source satellite intelligence, including Planet Labs (3m resolution, 1–2 day revisit), Sentinel-2 (10m resolution), and NASA Landsat/MODIS for regional baselines, to generate compliance risk assessments at the plot level. The geo-coordinates captured are timestamped, which validates the authenticity of the data. These outputs connect directly into due diligence workflows, enabling operators to assess, document, and demonstrate deforestation-free status for every coordinate submitted in their DDS.
Cropin's platform provides regional and plot-level deforestation analysis. The regional assessment uses land-use land-cover and deforestation maps for historical deforestation analysis. This provides insights into changes in land-use over time. At the plot level, Cropin helps you identify plots that overlap with land deforested since Dec 2020, the EUDR baseline year. It provides a clear picture of the percentage of the plot area that is on deforested land, along with details on the year of deforestation.
Dashboard showing deforestation at plot-level
Application dates
The EUDR timeline has been updated twice through targeted amendments. The current application dates are:
| Operator category | Application date |
|---|---|
| Large and medium-sized operators and traders | 30 December 2026 |
| Micro and small enterprises (SMEs) | 30 June 2027 |
| Newly added products (Delegated Act) | 30 December 2027 |
The December 2025 amendment also modified certain due diligence requirements. Operators should review the updated legal text and the latest version of the European Commission's FAQ guidance (Version 5, 2025) alongside their legal counsel.
Key takeaways for operators
- Geolocation is mandatory for every batch. If you cannot collect the coordinates of all contributing plots, you cannot legally place the product on the EU market.
- Polygons are required for plots larger than 4 hectares; a single point is sufficient below that threshold (and for cattle establishments).
- Six decimal digits of precision are required for all coordinate submissions.
- You are legally responsible for the accuracy of the coordinates you submit, even if collected by a supplier or intermediary.
- Mass balance is not allowed. Deforestation-free commodities must be fully segregated throughout the supply chain.
- Satellite cross-verification is how compliance is enforced. Build internal verification into your process before submission, not after.
- Downstream operators can reference upstream DDS, but must still ascertain that due diligence was properly exercised upstream.
For enterprises managing commodity supply chains across multiple geographies and thousands of suppliers, meeting these requirements demands more than spreadsheets and certification audits. It requires systematic farm-level geolocation collection, satellite-verified plot assessment, and an audit trail that can withstand regulatory scrutiny, the kind of infrastructure that intelligent supply chain platforms are built to provide.
Frequently asked questions
Can I use geolocation data provided by my supplier, or do I need to collect it myself?
You can use coordinates collected by your supplier, a cooperative, a certification body, or any other intermediary. However, the legal responsibility for the accuracy of that data rests entirely with you as the operator. If the submitted coordinates turn out to be incorrect, you are in breach of the Regulation, not the party who provided the data. In practice, this means you must have a process for verifying supplier-provided coordinates, not simply forwarding them to the EU Information System.
Does the EUDR geolocation requirement apply to products sourced from low-risk countries?
Yes, the obligation to collect geolocation coordinates applies regardless of the country of production's risk classification. Even for products sourced from countries classified as low-risk under Article 29, geolocation data must be gathered and submitted as part of the Due Diligence Statement. The difference for low-risk sourcing is that operators are exempt from the full risk assessment and risk mitigation steps (Articles 10 and 11), but the information collection step, including geolocation, still applies.
What happens if a supplier refuses to provide geolocation data or the data is simply unavailable?
If an operator cannot collect the geolocation coordinates of all plots of land contributing to a product, the Regulation is unambiguous: that product cannot be placed on the EU market or exported. There is no provision for a waiver or partial compliance. Operators in this situation must either work with suppliers to obtain the missing data, including through capacity-building support, or stop sourcing from that supplier for EU-bound products until traceability can be established.
Do geolocation coordinates need to be re-submitted every time the same plot supplies a new batch?
Yes. The due diligence obligation, including the geolocation submission, is linked to each individual product batch, not to the plot itself. Every time an operator places a relevant product on the EU market or exports it, a new Due Diligence Statement must be submitted that includes the relevant geolocation data. That said, downstream non-SME operators may reference a previous DDS submitted by an upstream operator (using its reference and verification numbers), which avoids the need to re-enter the underlying coordinates from scratch for each transaction.