Data engineering · Agriculture
EUDR compliance and plot-level traceability software
We build EUDR compliance and plot-level traceability software for producers, traders and processors of in-scope commodities: collection and validation of plot geolocation, supplier onboarding and documents, deforestation and legality checks, chain of custody from plot to product, risk assessment and the preparation of due diligence statements. The software works with your existing ERP and supply chain data, and you own the code.
Checklist · Agriculture
Agri ERP and traceability requirements checklist
A requirements checklist for farm management, dealer, grain and field systems, with the records and geolocation that deforestation and food traceability rules ask for.- 01Eight requirement areas from the field register to compliance records.
- 02What plot-level geolocation and chain-of-custody records need to contain.
- 03Items for field apps that work without a mobile signal.
- 04Seven questions to put to any vendor or development partner.
Free download
Get it on screen in a few seconds.
What the system does, module by module.
- 01
Product and commodity scope mapping
Classification of products and components against the regulation's commodities and derived products, to show which shipments need due diligence. - 02
Supplier and producer registry
Onboarding of suppliers, cooperatives and farmers with identity, location, documents and their place in the chain. - 03
Plot geolocation capture
Collection of plot coordinates or polygons through a field app, file upload or supplier portal, with the format and precision the regulation requires. - 04
Geodata validation
Checks for valid geometry, overlaps, implausible areas and coordinates in the wrong country, with feedback to the supplier to fix errors. - 05
Deforestation and protected-area screening
Comparison of plots with forest cover and change data and protected area boundaries, using the reference dates the regulation sets, with evidence recorded. - 06
Legality and documentation checks
Collection and review of land tenure, permits, labour and tax documents against the relevant laws of the country of production. - 07
Chain of custody
Linking of lots from plot through collection, storage, processing and shipment, with segregation or mass-balance rules applied and recorded. - 08
Risk assessment and mitigation
A risk score by country, supplier and plot, mitigation actions where risk is not negligible and a record of the reasoning. - 09
Due diligence statements
Preparation of statements with the required data, submission through the EU system interface and storage of references and supporting records.
Reference architecture.
Standards and interfaces
What we design against.
- Regulation (EU) 2023/1115 (EUDR)
- The EU regulation on deforestation-free products, covering commodities such as cattle, cocoa, coffee, oil palm, rubber, soya and wood, as amended, with application dates to be confirmed against the current text.
- Geolocation requirements
- Coordinates or polygons of plots of land in the specified format and precision, with polygons for larger plots.
- EU information system for due diligence statements
- The interface through which operators submit statements and receive reference numbers, with API and file options.
- Open forest and land data
- Public datasets on forest cover and change, and protected area databases, used for screening with documented limits.
- GeoJSON and OGC standards
- Open formats for plot geometry and exchange with suppliers and systems.
- Certification and chain of custody schemes
- Voluntary schemes whose records can support, but do not replace, the operator's own due diligence.
Data model
The core entities.
- Supplier and producer
- Identity, role, country, documents, risk rating and relationships in the chain.
- Plot
- Geometry, area, commodity, country, tenure documents and validation status.
- Screening result
- Plot, datasets used, reference date, finding, evidence and reviewer.
- Lot and movement
- Quantity, commodity, origin plots, location and the transformation or transfer.
- Shipment and product
- Product code, quantity, lots included, customer and destination.
- Risk assessment
- Criteria, score, mitigation measures, decision and date.
- Due diligence statement
- Content, submission time, reference, status and linked evidence.
When custom development is the right call.
Controls designed in, not added later.
Supplier data protection
Farmer identities and locations are personal and sensitive, so access is role-based, data is minimised and sharing is controlled.Evidence integrity
Geodata, screening results and documents are stored unaltered with versions and hashes for later inspection.Controlled submission
Statements are reviewed and approved before submission, and every submission is logged with its reference.Retention
Records are retained for the period the regulation requires and then handled according to policy.Audit trail
Decisions on risk, screening and mitigation record who decided and why.
From discovery to a system you run.
- 01
Scope and supply-base review
We map which products and shipments are in scope and how the supply base is organised, with compliance, procurement and sourcing teams. - 02
Data and process design
Data to collect, validation rules, screening datasets, chain of custody approach and the interfaces to the ERP and the EU system are agreed. - 03
Build supplier onboarding and geolocation
Registry, plot capture and validation are built first and tried with a group of suppliers. - 04
Screening, custody and risk
Screening, chain of custody and risk assessment follow, tested on live shipments. - 05
Statements and scale
Statement preparation and submission go live, and more suppliers and products are onboarded.
Relevant work
Where to see our work.
Related
Keep reading.
Common questions.
- Who does the regulation apply to?
- To operators and traders who place relevant commodities and products on the EU market or export them, with different duties for large, medium and small companies. Check the current text and your legal advisers for your position and the application dates.
- What geolocation data is needed?
- The geolocation of the plots of land where the commodity was produced, as coordinates for small plots and as polygons for larger ones, in the format the regulation specifies. We build collection and validation to those rules.
- Can software prove a product is deforestation-free?
- Software cannot give the legal conclusion, but it assembles the evidence: plot data, screening against forest and land data, documents, chain of custody and the risk assessment, so that the operator's due diligence is documented and defensible.
- How do you handle mixed lots and processing?
- By recording each transformation and applying the segregation or mass-balance rules you use, so a shipment can be traced back to the plots it came from.
- Who owns the code and the data?
- You do. The code, the geodata and the records stay yours.