Grovetrace holds one chain: the land a batch grew on, the lot it was blended into, the shipment it left in, and the statement filed for it. Everything below exists to keep that chain intact when the data arrives badly.
One consignment from the demo dataset, drawn from plot to filed statement. The references and states are the product’s own, and they are what you will see on the call.
GH-WR-0142ValidatedPolygon, SRID 4326. Parsed and rejected on the way in if it is not valid geometry, then checked against satellite deforestation alerts, which record their own verdict, date and confidence.
Two more plots feed the same lotGH-WR-0143GH-AH-0311
BCH-2026-016BlendedThree farmer deliveries become one lot, and Grovetrace records the join itself, so the plots behind it are still individually named downstream.
SHP-2026-0431CoveredCoverage is tracked against the tonnage on the purchase order, so a partially covered consignment shows the shortfall in tonnes.
DDS-2026-0288FiledThe statement names every plot behind the consignment. Five years later the evidence is one click from the shipment instead of a reconstruction.
Grovetrace connects to seven kinds of source: SQL Server, AS/400, FarmForce, a REST API, SFTP, a webhook, or a CSV upload. You map each one once (which column is the farmer, which is the plot, which is the lot) and it keeps pulling on a schedule.
Records land in a raw staging table first and are promoted from there, so a re-run over overlapping source data collapses to one row instead of silently doubling everything downstream. Idempotent ingestion is the unglamorous half of this, and it is where most of the engineering went.
How ingestion works in detailCompliance software fails when its model is thinner than the supply chain it describes. Grovetrace stores six objects and the links between them, and each one is there because leaving it out breaks a real filing.
A due diligence statement asserts a conclusion about risk. Grovetrace records the assessment behind it against each of the EUDR Annex I factors, so the conclusion can still be defended three years after the container cleared.
Earlier versions of an assessment are retained, and so is the satellite provider’s verdict on a plot. Resolving a flagged plot records what you decided and why; it never rewrites what the provider reported.
Submit, amend and withdraw are all implemented, for domestic and import declarations alike. The reference TRACES returns is stored against the shipment, so the statement behind a consignment can be produced years later without going back to the regulator’s portal.
A rejection is recorded with its reason and the shipment returns to the worklist as an item to act on, instead of arriving as an email nobody owns. Most rejections trace back to the same few fields being absent or imprecise, and that is where the platform concentrates its effort.
Six screens, grouped by the job they do. Every one of them is a route in the running product today.
Shipments in red, amber or covered, with the enforcement date counting down beside them and a priority alert naming whatever runs out of time first. It answers the arrival question directly: is anything about to reach customs with no statement filed?
Purchase orders and shipments ordered by what expires soonest, coverage measured in tonnes, one action per row. Orders that cannot move are grouped under what they are waiting for, so a blocked order never reads as an urgent one.
Each with its own list and detail page, cross-linked in both directions: a plot names the batches it feeds, a shipment names the plots behind its blend, and a statement names both.
Draft, risk-assess, submit, amend and withdraw, with the regulator’s status on the statement and the TRACES reference stored against it.
Certificates and permits with version history, archive and confidentiality flags, held in signed storage. Behind them, an audit trail scoped to your organization.
Administration has its own context in the application, entered by route. Access flows from policy to group to person, with no per-user role anywhere to drift out of step with your org chart.
A platform that claims everything is hard to evaluate. Five things Grovetrace deliberately leaves out, so you can rule it in or out quickly.
Twenty minutes, screen shared, on your own supply chain. Bring the thirty cooperative formats, the plots that will not reconcile, or the blend nobody can trace back.