EUDR DDS V3 API Migration Checklist — Practical Automation Lab

Current timing: the EUDR applies from 30 December 2026 for large and medium enterprises and for micro/small enterprises already covered by the EU Timber Regulation, and from 30 June 2027 for most other micro and small enterprises. The Commission identifies V3 as the current operator API and states that V1/V2 service contracts are replaced by V3.

1. Replace legacy service contracts

Move DDS integrations to EUDRDueDiligenceStatementServiceV3.
Review namespace and endpoint changes instead of assuming V1/V2 payload compatibility.
Remove legacy request assumptions such as operatorType; V3 uses operatorRole.
Review identifier changes such as legacy ddsIdentifier versus the V3 uuid field.
Review renamed operations, including the V3 withdraw operation where older integrations used retract terminology.

2. Revalidate payload structure

Validate activity type, commodity structures, HS headings, descriptions and quantity fields against the current V3 contract.
Do not reuse a V1/V2 schema merely by changing an endpoint URL; V3 introduced new namespaces, operations and data structures.
Account for V3 declaration versioning and newer status/event values where your integration reads declarations back from the Information System.
If your workflow serves eligible micro or small primary operators, review the separate V3 Simplified Declaration service rather than forcing those records into a DDS-only model.

3. Check producer geolocation data

For DDS producer data, the current V3 reference describes geometryGeojson as Base64-encoded GeoJSON.
Check longitude/latitude ordering, supported geometry types and source precision before constructing the final payload.
The Commission's GeoJSON documentation states coordinates use latitude/longitude with at least six decimal digits; validate source exports before submission.
Keep supplier and geolocation data out of analytics, public tickets and source repositories.

4. Test migration leftovers before production

Search generated payloads and mapping code for V1/V2 field names and namespaces.
Test representative import, export and domestic payloads rather than only a single happy path.
Validate grouped-reference handling and retrieval flows if your process depends on upstream declarations.
Keep Information System credentials out of preflight files and browser analytics.

Run the free EUDR DDS V3 technical preflight

Need batch, team or recurring validation?

The public preflight remains free. Teams evaluating larger-volume validation, a team software license or recurring data-quality monitoring can send a software-access request without sharing supplier records, credentials or geolocation data.

Request EUDR software access

Primary technical sources

This page and the PAL preflight are technical software resources. They do not provide legal advice, determine whether a product or operator is in scope, assess deforestation-free status, or guarantee acceptance by the EUDR Information System.