The EUDR Information System is open: what changed on 13 July 2026

Every due-diligence statement is filed through the EU's Information System. That system reopened on 13 July 2026, the same day the Commission adopted the Implementing Act governing it, with further functionality arriving through the summer ahead of the 30 December 2026 application date for large and medium operators. Both environments are available: production for real filings, and acceptance for testing and conformance work. The relaunch was first announced in the Commission's May 2026 simplification package (press release IP/26/941).

The four changes named by the Commission

• A simplified declaration form for MSPOs, aligned with the existing DDS format rather than a separate schema.
• Updated API specifications for system-to-system filing, which is how compliance software submits on an operator's behalf.
• A contingency plan for when the system is unavailable, so an outage does not block goods at the border.
• A voluntary grouping feature, letting operators group multiple submissions.

In parallel, the Commission is working with member states to let data already held in national databases flow into the system directly, which for many of the smallest producers removes the need to interact with it at all (Art. 4a(4)).

What to do before December

• Do the work the system does not do for you: plot geolocation, deforestation screening, the legality record per supplier and the risk assessments are the due diligence, and the statement is only the last step of it.
• Use the acceptance environment while there is no deadline pressure. It is the cheapest place to find out that a boundary fails validation or a field is missing.
• Make sure whatever software you use files against the renewed API rather than the older specification, and ask to see it submit.
• If you buy from suppliers who might qualify as MSPOs, learn the declaration-identifier flow now; their identifier replaces a DDS reference in your records.

Konstata is built to the reopened system's API and ready to file. The case file behind each statement, which is where the real work sits, is built long before the statement is assembled, and that is the part worth starting now.