EUDR compliance software priced for a 12-person team

The Regulation makes five demands of an operator: know the plots, show they were clear of deforestation after 31 December 2020, show production was legal, file a Due Diligence Statement, and keep the record. Bindu covers them in that order. Plot geolocation arrives as a GeoJSON upload or typed coordinates and is validated on entry, a six-decimal point for plots under four hectares and a polygon above, the format the geolocation rules demand.

Each plot is then checked against forest-cover data for the 31 December 2020 cutoff and carries its own verdict, and the legality evidence, permits, supplier declarations, certificates, is recorded on the same dossier. When the shipment moves, the Due Diligence Statement is assembled from the record and filed to TRACES, the returned reference number is stored, and a receipt PDF documents what was filed and when.

You collect a supplier’s documents and coordinates into the dossier once. Every later shipment of the same supplier and commodity, coffee from the same cooperative, rubber from the same plantation, reuses that record rather than restarting it, and only what changed needs touching. The seven commodity guides set out what each commodity needs collected.

Behind the record sits an append-only, hash-chained audit trail: every upload, edit and filing is logged in sequence, and no entry can be quietly rewritten. That is the shape of evidence the Regulation’s five-year retention expects: an authority asking in 2031 about a 2026 filing gets the record as it stood, not a reconstruction.

The code is open source under AGPL-3.0, at github.com/GetBindu/Bindu, so what the software does with your data is inspectable rather than asserted, and self-hosting stays open to you. Pricing follows the work, from €19 per dossier with no subscription and no platform fee, so a quiet quarter costs nothing.

Hosting is in the EU, and each company’s data lives in its own sovereign workspace node rather than in a shared pool. The rest of the small-importer lane, the later 30 June 2027 date, the size test that decides it and the reliefs, is on EUDR for SMEs.

A spreadsheet is where most operators start, and it genuinely can hold coordinates. What it cannot do is validate the geometry it holds, check a plot against forest-cover data for the 2020 cutoff, or file anything to TRACES; at each of those points it hands the work back to you. A consultant can do all three, per shipment, at consultant prices, which is a fair trade for a one-off filing and a poor one for a flow that repeats every month.

The software’s claim is deliberately narrower than either: it does the repeatable part, validation, the forest check, assembly, filing, retention, and keeps the evidence in one place. What the Regulation leaves to the operator stays with the operator, above all whether the legality evidence is sufficient. Bindu prepares the statement and files it; it does not decide compliance for you.