Rules, source mappings, and reusable validation logic stay server-side.
Back to homeHow it works
Use the tools in the same order an importer prepares an EUDR file.
EUDR Tools is not a one-page explainer. It is a sequence of focused checks: classify the product, verify geolocation, understand origin context, request evidence, and keep the final filing boundary clear.
Public pages return limited findings and human-readable references.
The tools help preparation only. Nothing is sent to TRACES.
01
Check whether the product code matters.
Start with the HS/CN code. The checker returns a narrow action result: in scope, out of scope, excluded, or too broad and needing a more specific subheading.
Open HS checker02
Validate supplier geolocation before it becomes manual work.
Import supplier files into Map Studio — GeoJSON, KML, KMZ, Shapefile, GPX, GML, WKT, CSV, Excel — and catch structure, polygon, and coordinate issues before the file reaches a filing workflow.
Open Map Studio03
Read origin and risk context without treating it as an exemption.
Country risk changes the route and review burden. It does not remove the need to understand product scope, production origin, and Article 9 information.
Open country lookup04
Collect the evidence the origin country actually requires.
Every country page carries the Article 9 evidence checklist and manual TRACES filing steps — and for major producer origins, the national registry that proves legality there.
Open a country page05
Package the real thing in Map Studio.
The shipment pack is built from your actual plots: the official TRACES GeoJSON behind a readiness gate, the plot register, a manifest and checksums — not a preview.
Open Map StudioEnd state
A human-readable preparation file: product scope known, supplier plot issues caught, origin context understood, and evidence requests ready before any official submission step.