Every time a European buyer sends a traceability document request, the first reaction at many estates is to form a dedicated team. In our experience, that is the wrong start. Most of what is being asked for is already produced by daily estate work — what is usually missing is only a way to store it so it can be retrieved on request.
An important note before continuing: this article is about data readiness, not legal advice. The details of the obligations and their effective dates have changed several times, so check the current requirements with your legal counsel and your buyers.
What is actually being asked
Simplified, the request revolves around three things: where the commodity was grown, whether the land converted from forest after the cut-off date, and whether production was lawful under local law.
What makes it feel heavy is not those three questions but the level of granularity. A company-level answer is not enough; what is required is a plot-level answer, complete with coordinates, traceable through to the lot shipped.
What daily work already produces
Estates whose operations are already recorded digitally usually hold most of the material without realising it:
- Block boundaries as polygons, from the mapping used for work planning.
- Dated harvest records per block, which form the basis of lot tracing.
- Dispatch notes and weighbridge tickets connecting blocks to shipments.
- Permits and land legality documents already held by the legal department.
What is usually missing is the link between the four. The polygons sit in map files owned by the mapping team, harvest records in the operational system, and legal documents in a filing cabinet. All three are correct, but they cannot be called up together for one specific lot.
Compliance rarely fails because the data is missing. It fails because the data cannot be retrieved in the form requested, at the time requested.
The hardest part: partner and smallholder estates
For the nucleus estate, plot mapping usually exists already. The real difficulty appears in supply from partner farmers: hundreds or thousands of small plots, often with no mapped boundary, whose deliveries are recorded in a notebook at the collection point.
Mapping partner plots takes time, so it is best begun long before the request arrives. The approach we have seen work is collecting coordinates during interactions that already happen — when a field officer makes a coaching visit, or when a farmer registers their first delivery of the season. Running mapping as a separate exercise is almost always slower and more expensive.
Storing it so it can be retrieved
The practical requirement is simple but often missed: every piece of evidence must attach to the same object as its operational transaction. If plot polygons, harvest records, and legality documents all attach to the same block or partner plot, assembling the file for one lot becomes minutes of work rather than weeks.
Two more things that make life easier later: version, do not overwrite — keep the history of plot boundary changes rather than replacing them, because auditors' questions often concern the state on a specific past date. And keep a trail of who recorded what, because evidence without clear provenance loses weight under scrutiny.
The order we suggest
- Start by making sure nucleus estate block polygons are complete and verified.
- Link harvest and shipment records to those polygons, not to vehicle numbers alone.
- Collect partner plot coordinates by piggybacking on interactions that already happen routinely.
- Keep the history of boundary changes; do not overwrite the old data.
- Test your readiness on one real lot before an actual request arrives.
Testing before you are asked
The cheapest way to find out where you stand is a dry run. Take one shipment that has already gone out and try to assemble its origin file: which plots contributed, what their coordinates are, when they were harvested, and which legal documents accompany them.
If assembling it takes more than one working day, that is not a sign you need a compliance project of its own. Usually it means one or two data links are broken — and repairing those is far cheaper than forming a new team.
The VarmOS compliance and traceability module gathers evidence from daily activity — see the module or talk through your data readiness with us.