Field data that can move to the systems that need it
Farmers and field agents collect plot data once, with consent. From there it is built to move: to buyers, to the EU, and, as we work toward it, to national traceability systems.
EU Information System (TRACES)
BetaTracebud prepares your due diligence statement in the format the EU Information System (TRACES) asks for, with plot maps as GeoJSON. You file it in TRACES, then paste the reference and verification numbers back into Tracebud. They stay with the shipment and go on to your buyers.
Data in and data out
A country or programme can bring in the registry data it already holds, such as farmer lists and plot boundaries, in GeoJSON, KML, shapefile, or CSV. It can take plot boundaries and records back out at any time in GeoJSON and CSV. Systems with permission can pull chain-of-custody and compliance data through the Tracebud API.
GeoID-friendly rails
Your team can add one optional AgStack GeoID per producer in the Dashboard. It is included in data exports, and duplicates are flagged for review. Tracebud does not create or register GeoIDs, and the Field App has no GeoID workflow.
What we are building next
In progressSending statements to the EU Information System straight from Tracebud, and looking up a statement by its reference and verification number. We also want to work with national traceability systems, so data can move both ways where a country wants it.
What Tracebud does not do
Tracebud does not own, host or run any national system, and it does not replace one. We are not an approved or registered provider for any national system.