Is EUDR Tools an official EU or TRACES service?
No. EUDR Tools is an independent preparation aid. It does not submit a Due Diligence Statement, does not connect to TRACES, and is not affiliated with the European Union.
Back to homeFAQ
Practical answers for importers using EUDR Tools.
Short answers about scope checks, supplier plot files, country risk, evidence requests, data boundaries, and what the public tools deliberately do not do.
Can this replace legal advice or an internal compliance review?
No. The pages are practical preparation tools and references. Final classification, due diligence, and filing decisions remain the operator's responsibility.
Why are the tools free?
The public surface is designed for narrow checks and repeat utility. Backend rules, source mappings, reusable validation logic, bulk processing, and raw datasets are not exposed.
Should I start with HS/CN scope or country risk?
Start with HS/CN scope. Country risk changes the route and review burden, but it does not replace the product classification and evidence workflow.
What happens if my HS code is too broad?
The checker should push you to a narrower subheading. Broad headings can contain both relevant and irrelevant products, so they are not enough for a final action result.
Does low-risk country status mean no evidence is needed?
No. Low risk may support a simplified route when conditions are met, but Article 9 information collection and product-level preparation still matter.
Why do tool result pages and library pages both exist?
Tool result pages are action views: what to do next. Library pages are reference records: source context, hierarchy, related rows, and source metadata.
What should I collect from a supplier first?
Start with product description, quantity, country of production, production plot geolocation, supplier identity, legality evidence, and deforestation-free support.
Can suppliers upload plot files here?
Yes — Map Studio imports supplier GeoJSON, KML, KMZ, Shapefile, GPX, GML, WKT, CSV, and Excel files, checks their readiness, and converts them to Commission GeoJSON. It is not a bulk processing API.
What if a supplier only sends coordinates, not a polygon?
That may not be enough for a plot boundary. Use the validator and supplier plot file reference pages to explain what is missing before the file reaches manual review.
Do evidence needs change by commodity?
Yes. The legal structure is shared, but cocoa, coffee, wood, rubber, cattle, soy, and palm workflows need different supplier wording and supporting examples.
Can I download the raw datasets?
No. Public pages provide readable findings and references. Raw source tables, bulk exports, and reusable API-style access are intentionally not exposed.
Why are some outputs limited?
Public pages return readable findings for one consignment at a time. Batch processing, bulk validation, and raw dataset access are intentionally out of scope for the public surface.
Where do source links live?
Use the Data & Sources page for official references, source groups, data inventory, and update-cadence notes.
Boundary reminder
Public outputs are intentionally limited. Saved workspaces, batch processing, large artifacts, and reusable backend engines are not exposed through free pages.