How to prepare plot geolocation for EUDR supply chains in Colombia

Useful readiness begins with a verifiable relationship among supplier, product, plot and evidence, not a folder of unrelated polygons. A Colombian company can organize these data to answer requests from European buyers, but this work does not make it a certifier or replace the due diligence of the operator or trader subject to the rule in the European Union.

The consolidated EUDR text covers specified products associated with cattle, cocoa, coffee, oil palm, rubber, soya and wood. The amendment establishing the application dates sets general application on 30 December 2026 and 30 June 2027 for EU actors covered by the deferred micro- and small-enterprise rule. Those dates apply to actors in the EU; they are not Colombian producer certification deadlines. Colombia supports supply-chain traceability and the quality of evidence requested by its customers.

Start with the traceability model

Assign stable identifiers to producers, properties, plots, production lots, purchases and shipments. A farm name or supplier document number should not be the technical key because it may be corrected or changed without breaking history. Every relationship should preserve source, capture date, owner and review status.

The minimum model should answer four questions:

1. Which product is connected to which lot or purchase?
2. Which supplier declared or confirmed the origin?
3. Which plot represents that origin, and how was its geometry obtained?
4. Which changes or exceptions occurred before delivery to the buyer?

Where products are mixed at collection points, document aggregation and separation. Do not assign a plot to a product when the commercial record does not support that relationship.

Review geometry as evidence

Validate CRS, coordinate order, geometry type, ring closure, self-intersections, duplicates and implausible areas. Compare file identifiers with the supplier master. Do not automatically turn a coordinate into a polygon, and do not describe a boundary digitised from imagery as a field-precision survey.

Keep received geometry, corrected geometry and correction reason as separate values. If the team transforms a file, record the tool, date, and source and target reference systems. This history explains differences without deleting original evidence.

Design a workflow that works in the field

For locations without connectivity, prepare forms and basemaps before the visit. Use short catalogues, justified required fields and an exception queue. After synchronisation, review missing records, repeated plots, producer-to-lot conflicts and unreadable files.

Avoid collecting personal information without a defined purpose. Roles, retention and buyer-sharing rules should be agreed before data are loaded. Offline field capture with QField can support this workflow, but it still needs a data model and reconciliation protocol.

Finish with an auditable sample

Before scaling, test a representative chain from collection through a reviewed export. Include correct, incomplete and contradictory cases. Measure completeness, unresolved exceptions and the ability to reconstruct every link. GeoSAT's geospatial EUDR readiness service structures this component; it does not certify compliance, interpret the full legal obligation or guarantee acceptance by a buyer or authority.