EUDR Trace keeps the DDS reference numbers you receive, passes them on to customers and prints them on PDFs. Operators prepare due diligence statements from a purchase order and submit them through the official V3 API of the EUDR system (TRACES).
An EUDR tab on purchase orders, supplier invoices, receptions, sales orders, shipments, invoices and products. When a sales order, shipment or invoice is validated, the latest upstream reference of each relevant product is attached and printed on the PDF; an option blocks validation when a reference is missing.
A DDS is prepared from a purchase order or a reception with commodities, HS codes, computed net weights, species and the supplier’s plots. The Commission’s published rules and the embedded official XSD schemas are applied before any call: blocking points are listed on the declaration until they are fixed.
GeoJSON file, pasted text or a single GPS point. Closed polygon, no holes or self-intersections, duplicates after 6-decimal truncation, 4 ha limit for a point, property case, 25 MB limit: the common errors are detected locally, the area is computed and a schematic preview is drawn without any map service.
The banner recalls the obligation for the chosen profile and counts down to the application date retained for your company size. Counters: relevant products, purchases and sales without reference, register lines, available declarations, valid plots. A roadmap, the documents to complete and the recent activity follow.
Browse all screens →| Workflow | Trigger | Result in Dolibarr |
|---|---|---|
| Relevant products | Automatic detection from the native customs code field (Annex I), to confirm | Commodity (wood, cocoa, coffee, soya, palm oil, rubber, cattle), HS code and species for wood saved on each product. |
| Upstream references | Entered on the EUDR tab of a purchase order, supplier invoice or reception | Reference and verification numbers checked against the official format (DDS, simplified “S…”, customs contingency), linked to the document, product and supplier; duplicates rejected. |
| Downstream pass-on | Validation of a sales order, shipment or customer invoice | Upstream references attached automatically, printed on the PDF; optional blocking without reference; CSV export of the register with full partner identity. |
| Due diligence statement | “Prepare a DDS” from a purchase order or reception | Commodities, weights, plots and risk assessment; rules and XSD checked; submission through the V3 API in acceptance or production. |
| Reference numbers | Scheduled task every 30 minutes | Reference and verification numbers retrieved, amendment and withdrawal within 72 hours, grouped declarations, multi-operator accounts. |
| Country risk | Embedded benchmarking of Implementing Regulation (EU) 2025/1093 | Low, standard or high risk applied to each plot, overridable country by country with a justification. |
Choose the “downstream operator” or “trader” profile in the setup. The module then focuses on the register: keeping the reference numbers received from suppliers with their identity, and passing them on to your customers on orders, shipments and invoices. No DDS screen is required.
From the native customs code field of the product card, matched against the Annex I nomenclature by longest prefix. The “Relevant products” screen lists detected products to confirm, lets you correct the commodity and HS code, and asks for species for wood. Positions whose removal has been proposed (leather, retreaded tyres) are flagged.
The V3 services of the EUDR information system (EUDRDueDiligenceStatementServiceV3 and EUDRSimplifiedDeclarationServiceV3) with WS-Security UsernameToken authentication, in the acceptance (test) or production environment chosen in the setup. XML exchanges are archived with a masked digest.
Yes, within the 72-hour window shown on the declaration card: amendment and withdrawal are available, and the history tab keeps every step. After that window the declaration is final in the information system.
The “micro or small primary producer” profile prepares a simplified declaration (SD) with geolocation, postal address or cadastral reference, as provided by the amended regulation. A representative profile declares on behalf of operators.
No. GeoJSON checks, area computation and the schematic preview run on your server. Nothing is sent anywhere except to the official API when you submit.
Being published on Dolistore · version 1.0.0
The listing exists on Dolistore and is awaiting the marketplace approval. Write to us to receive the module today, with French and English translations and e-mail support; we will send the Dolistore link as soon as the listing is open for purchase.
