Excel → TRACES · EUDR
How to import Excel (XLSX) supplier data into TRACES for EUDR
TRACES only lets you pick .geojson or .json in the "Import Geojson" dialog — an .xlsx or .csv file cannot even be selected. There is no Excel import for EUDR geolocation: the spreadsheet has to be converted to GeoJSON first.
EUDR is mandatory for medium & large operators from 30 December 2026 — get your supplier files TRACES-ready now.
Files never leave your browser · no upload
Why Excel will not import into TRACES
The EUDR geolocation import accepts a single format — a GeoJSON FeatureCollection. The file dialog filters to geojson/json, so your supplier's coordinate spreadsheet is simply not selectable. This is a format wall, not a settings problem.
Turn the spreadsheet into TRACES-ready GeoJSON
Drop the .xlsx or .csv into DDSpass. It auto-detects the latitude/longitude/area/producer columns, converts to GeoJSON, and fixes the traps a manual conversion introduces — swapped coordinates, comma decimals, an area typed as text that TRACES reads as 0 ha. See Excel to TRACES for the column details. Nothing is uploaded.
Which Import button to use in TRACES
Verified on TRACES build 8.2.0.2: upload the converted GeoJSON with the top-level Import button (next to “Add Production Place”) — that path fills the producer name, country of production and place description from the file. The Import GeoJSON inside “Add Production Place” reads only the geometry and leaves the country on “No country selection”.
Questions
Can TRACES import Excel or CSV directly?
No. The EUDR "Import Geojson" dialog only accepts .geojson/.json files — Excel and CSV cannot be selected. Convert to GeoJSON first.
What columns does my spreadsheet need?
Latitude and longitude at minimum; DDSpass also detects area, producer name and country automatically.