The EUDR Information System went live on 4 December 2024, with registration open since November 2024, and it sits in the same EU ecosystem as TRACES NT. Integration work is less about connecting to a new portal and more about keeping three data sets in agreement: product classification, due diligence records and declaration data.
Map the boundaries between systems
Classic TRACES handles sanitary and phytosanitary control under Regulation (EU) 2017/625, using health certificates, CHED and establishment codes. EUDR handles deforestation-free proof under Regulation (EU) 2023/1115, using the DDS and geolocation data. Model them as separate obligations against the same consignment, so a single shipment can carry two independent statuses.
Keep one source of truth for product scope
Both workflows depend on knowing exactly what the product is. Classification drives EUDR scope through Annex I, and it drives declaration data everywhere else. If classification lives in two places, the systems will disagree at the worst moment. iCustoms supports HS code confirmation across 32 or more countries, document data extraction at 99% accuracy, declarations across the UK, Ireland and 22 EU nations, and bulk establishment code validation through iTraces, and the wider architecture is described in this EUDR Information System guide.
Then wire the reference through
The last integration step is small and easy to forget: carry the DDS reference number into the declaration payload and validate it before submission.
FAQs
Is EUDR filed inside TRACES NT? No. It is a separate workflow in the same EU ecosystem.
What is iTraces for? Validating establishment codes in bulk against the EU database, which supports the SPS side rather than EUDR.
Does iCustoms submit the DDS? No. That obligation stays with the business.
Top comments (0)