How Sankora works, from plot to export file.

The principle: one chain of evidence

The EU Deforestation Regulation (EUDR) requires proof, for every exported lot, of where the product comes from and that the plot of origin was not deforested after 31 December 2020. That proof is built throughout the season, not the day before shipment.

Sankora therefore organises the work as a chain: a farmer, their plots, their checked boundaries, the purchases made from those plots, the lots built from those purchases, then the shipment and its file. Each link relies on the previous one: a lot can never be more compliant than the plots it comes from.

The same platform serves the cooperative, the exporter and, if they wish, the final buyer. Each sees only their own data and what their partners choose to share.

The farmer and plot register

Everything starts with the register. Farmers and plots are imported from your existing files or entered directly; likely duplicates are flagged so the same person does not appear twice.

Each plot gets a unique identifier, a commodity, a locality and, as soon as it is available, its boundary. Boundaries come from your existing surveys (GeoJSON, KML or GPX files) or from field collection. For small plots a GPS point can be enough, as the regulation allows.

The register can be viewed as a list or on the map, filtered by section, programme, commodity or status. Nothing is erased: a deactivated plot or a replaced boundary stays in the history.

Polygon checks

A poorly surveyed boundary is the first reason a file gets rejected. That is why every polygon is checked as soon as it is uploaded, before it is used anywhere else.

The check covers the geometric consistency of the outline, its location, its area compared with the declared area and its overlaps with neighbouring plots. The rules are grouped into profiles that each organisation can adapt.

• Compliant: the polygon can be used as is.
• Compliant after correction: a simple error was fixed automatically, and the original version is kept.
• Reservations: a point needs human review.
• Rejected: the boundary must be surveyed again.

Doubtful polygons can be quarantined: they remain visible but no longer count in lots or files until the issue is settled.

Deforestation risk analysis

Each located plot is compared, inside Sankora, with the reference forest cover on 31 December 2020 and with cover loss observed by satellite since then. The result is shown plot by plot: no deforestation detected, to be checked, or probable deforestation.

The analysis runs again whenever a boundary changes, and plots to check appear in the alerts. The final decision stays human: Sankora shows the evidence, your team decides and the decision is recorded.

Flows: purchases, payments, stock and lots

Purchases are recorded at the warehouse or collection point: farmer, plot of origin, weight, quality, price. Payments cover every method used in the field, cash, mobile money, transfer or cheque, without ever blocking a payment while waiting for proof.

Purchases then form lots. Sankora continuously computes the share of each lot coming from compliant plots: a lot is EUDR-compliant only if all its weight is. Lots are shipped, linked to sales contracts and loadings, then received by the customer.

Volumes are compared with each plot's estimated output, to spot purchases that do not match what a plot can produce.

EUDR compliance: risk assessment and due diligence

For each lot or shipment, Sankora prepares the risk assessment required by Article 10 of the regulation. Criteria are computed from your data; your team completes the legality elements, decides on mitigation measures and concludes.

An assessment covers a frozen scope: it only covers a shipment if all its plots are included. And it follows the four-eyes rule: the person who drafts it is never the one who approves it.

Then comes the due diligence statement, with every Annex II element and geolocation in the format expected by the EU information system. You submit it in TRACES and record the reference in Sankora: the file, its versions and its supporting documents remain available for any inspection.

Season steering

Dashboards track purchases, traced share, located plots, amounts due and deforestation risk, with a volume map. Every table can be filtered, sorted and exported for your reports.

Alerts flag what needs action: a rejected polygon, a plot to check, an incomplete lot, an overdue payment. They arrive before the problem blocks a shipment.

Who sees what

Each organisation works in its own space and sees only its data. Rights are given by role: data entry, quality control, approval, management. Sensitive operations, such as approving a document or an assessment, require a second person.

Your buyer can have access to view the lots that concern them and their evidence, without seeing the rest of your business.

Getting started with Kaada Group

Kaada Group imports your existing data, sets up sections, programmes and check profiles, then trains your teams, in the office and in the field. Roll-out follows your season calendar.

This page describes how Sankora works in general. Detailed check rules, data sources and how Sankora adapts to your organisation are shown in a demo, on your own cases.