Excel / CSV → TRACES
Excel to TRACES-ready EUDR geodata — without rejections
Most suppliers send plots as an Excel or CSV with latitude/longitude columns. TRACES can’t read that — and the usual manual conversion quietly introduces errors that either get the upload rejected or, worse, are accepted with the wrong data.
Fix your file — freeEUDR is mandatory for medium & large operators from 30 December 2026 — get your supplier files TRACES-ready now.
Files never leave your browser · no upload
The traps in a supplier spreadsheet
Swapped latitude/longitude, commas used as decimal separators, an area typed as text (which TRACES reads as 0 ha), points over 4 ha that must be polygons — these pass a human glance but break the declaration.
DDSpass auto-detects the columns, fixes what it safely can, and clearly separates “what we fixed” from “what your supplier must correct and re-send”.
From spreadsheet to submission
Drop the .xlsx or .csv in. You get a TRACES-ready GeoJSON, a map preview to eyeball the plots, and a supplier report in EN/ES/PT/FR/DE/NL/DA. Nothing is uploaded.
Questions
Which columns does it need?
Latitude and longitude at minimum; it also detects area, producer name and country columns automatically.
What if a plot is a single point over 4 ha?
It is flagged: under EUDR Art. 2(28) plots over 4 ha must be sent as a mapped field boundary, not a point.