How this tool's fields map to the EU's own DDS / TRACES NT filing system
A screening report is not a filable Due Diligence Statement. Here's exactly what carries over, what doesn't, and why — sourced directly from the Commission's own FAQ, not summarized secondhand.
The one thing to know before anything else
The Commission's own Information System accepts bulk geolocation uploads in GeoJSON only — confirmed twice, directly in the Commission's own FAQ ("Why is only GeoJSON format allowed for uploading geolocation data in a file? ... The exclusive use of GeoJSON was announced in April 2024") and independently via the Information System's own page.
What carries over, and what doesn't
Three kinds of fields: ones that map directly onto a real TRACES/DDS requirement, ones that inform your own Article 10/11 risk-assessment paperwork without being a TRACES field themselves, and one real format gap.
| This tool's field | Maps to | Notes |
|---|---|---|
| lat, lon | DIRECT Geolocation point (Art. 2(28)) | TRACES requires ≥6 decimal digits; short values are silently zero-padded by the system rather than rejected (FAQ 7.17) — check your own precision before filing, don't rely on the padding. |
| geometry_wkt | DIRECT, format gap Polygon (plots ≥4ha) | Plots ≥4ha (any commodity except cattle) legally require a perimeter polygon, not a center point + radius (FAQ 1.16). This tool's WKT already carries that boundary — but needs converting to GeoJSON to actually file. |
| location_source = "geocoded" | CONTEXT MSPO postal-address exemption (Art. 9(1)(h)) | The Commission allows micro/small primary operators to substitute a postal address for coordinates. This tool's geocoded-address path is the same idea, but for screening precision, not a substitute for the operator's own MSPO declaration. |
| country | DIRECT Country of production (per Production Place) | Each country of production must be its own separate "Production Place" entry in the DDS (FAQ 7.13) — relevant if one shipment sources from more than one country. |
| flag, flag_reason | CONTEXT ONLY Not a TRACES field | RED/AMBER/GREEN is this tool's own risk-screening output, not something entered into TRACES. It's evidence you can keep on file to support your own Article 10 risk assessment — it isn't the assessment itself. |
| due_diligence_label, due_diligence_note | CONTEXT Country risk tier (Reg. 2025/1093) | Tells you whether simplified due diligence is even available for this origin — informs which Article (10 full vs. 13 simplified) applies to your own filing, but isn't itself a TRACES data field. |
| nearby_pressure_tier, confidence | CONTEXT ONLY Not a TRACES field | Supporting evidence for your own risk-assessment file (Art. 10/11 mitigating-factors documentation) — not something TRACES asks for directly. |
| (bulk upload format) | GAP GeoJSON-only requirement | This tool's CSV/Excel/WKT input is not directly filable. Converting your final, verified geolocation set to GeoJSON before submission is a step this tool does not perform. |
Screening and filing are two different steps
This tool answers "where should I look harder?" — a fast, cheap first pass across your supplier list. Filing a Due Diligence Statement is a separate, later step with its own stricter format (GeoJSON, 6-decimal precision, polygon-only above 4ha) and its own legal weight. Confusing the two is exactly the kind of gap that leaves an operator underprepared at the actual filing stage — we'd rather tell you where the line sits than let you assume this report is the finish line.