Skip to main content

​
The Path to EUDR Compliance

This page takes you from the first master data to reviewed evidence and, where required, a submitted DDS. The steps apply per article and transaction: you can request supplier data while working on other articles.
Open the relevant task in the EUDR dashboard. If the view is empty, first check All, Assigned to me and the active module. An empty personal task list does not automatically mean every article is compliant.
Request missing data early. First confirm the recipient and affected articles. After sending, check request history and delivery; automatic reminders follow your configuration.

​
The Six Steps

Step 1: Initial Setup

Set up your company account and clarify your role, responsibilities and DDS obligation. If you submit from Polygon One, configure your TRACES credentials, including the correct role and environment. The overview explains application dates and roles.Take care of email deliverability now, not once suppliers fail to respond:

Step 2: Import Master Data

Import suppliers and articles via CSV. For your own production, link output and input articles through the bill of materials; check weights and the supplier country.Check the preview, mappings and import result before inviting suppliers. Correct missing required values or failed rows specifically; starting an import does not mean all data has been imported.

Step 3: EUDR Relevance Check

The relevance check derives classifications from HS codes. Check missing or incorrect codes and unresolved material information, especially for ex-headings and composite products. Not EUDR-relevant does not confirm that your source data is correct.

Step 4: Data Collection (Art. 9 EUDR)

First check the origin route: your own origin data or coverage by an upstream DDS. For upstream coverage, use Incoming DDS; do not routinely request additional plots for an article covered exclusively by references. For outstanding origin and evidence data, use either route:
A draft saved by the supplier is not yet a submitted response. Check the request history before requesting the same information again.

Step 5: Risk Assessment (Art. 10 EUDR)

The risk assessment processes incoming data. Open pending reviews and risk mitigation: a submitted response or uploaded document may still await analysis or your decision. Conclusive results can be applied automatically; review open decisions per category or plot. Accept sufficient responses or request a specific correction. Reports document the assessment at that point in time.Simplified due diligence for origins in low-risk countries has conditions. New risk information can require further assessment; the country alone does not replace checking the individual case. Settings control the platform analysis. Legal basis: Article 13 EUDR.

Step 6: DDS & Orders (Art. 3 EUDR)

Create or import orders and check article assignments and quantities. Create any required due diligence statements (DDS). Create Draft saves without transmission; Create & Submit transmits after submission checks. Missing values can block submission even if the draft has been saved. Automatic assignment and creation follow your settings.Then check the TRACES response: Processing or Submitted is not yet Validated. If an error occurs, read the message, correct the existing record and check whether transmission already occurred before trying again.

​
Afterwards: Ongoing Operations

Once the process is set up, EUDR compliance becomes routine:
  • New articles and suppliers need a fresh check of relevance, origin and open tasks. An earlier approval does not automatically cover changed data.
  • Supplier requests ask for corrections and missing evidence exactly where risk mitigation finds a gap.
  • Notifications alert you whenever something needs your attention — e.g. new supplier responses or identified risks.
  • The dashboard remains your starting point: progress, bottlenecks, and the next sensible action.

​
Read Progress Correctly

For Data missing, add or request the named information. For Assessment pending, check running analyses and open decisions. For rejected responses, request the missing correction; for persistent technical errors, give support the record and error message. The status glossary explains each label.

Questions about the process?

Our team is happy to guide you through the setup personally.