Skip to content
Back to insights

Data

The EU Information System: what to expect when you connect to it

Statements are filed through a Commission system inside TRACES. Here is how it behaves and how to build against it sensibly.

2 August 2026 · 6 minute read

Due diligence statements are submitted through the EUDR Information System, which sits within the Commission TRACES platform. There is a web interface, and there is a machine to machine capability for organisations filing in volume.

Two practical characteristics matter more than the technical detail.

There are two environments, and they are not the same

The Commission runs an acceptance environment and a production environment. Acceptance is where you prove your integration works. Production is live, and a test submission arriving there is not a small embarrassment.

Any system you buy or build should make the current environment impossible to mistake, and should refuse to send development data to production rather than relying on a person to notice.

The specification moves

The system was in restricted mode during early 2026 following the legislative amendments, and the Commission reopened it in July 2026 with further functionality following. Technical documentation for economic operators is published and updated by the Commission.

The engineering conclusion is to isolate the integration behind a single interface, so a specification change touches one module rather than the whole product. It also means treating the specification as a versioned dependency with a review date, not a one off download.

Sources

  • European Commission EUDR Information System documentation, CIRCABC
  • European Commission notices on Information System availability, 2026

General information, not legal advice. Requirements change. Verify against the current official text before acting.

See this against your own orders

Thirty minutes, your product list, one supplier you are already chasing.

Book a walkthrough

Continue reading