Quick summary: EUDR outbound declarations explained: link ERP orders, batches and shipments to the DDS and pass reference numbers to customs before December 2026.
EUDR outbound declarations are the Due Diligence Statements (DDS) a company files for goods it places on the EU market or exports, together with the reference and verification numbers it passes on to customs and customers. Connecting them to your ERP means linking each sales order, batch and shipment to its supplier evidence, filing the DDS before customs clearance, and writing the returned reference number back onto delivery notes, invoices and the customs declaration under code C716.
EUDR outbound declarations are where EUDR compliance meets daily logistics. From 30 December 2026, large and medium operators cannot release relevant goods for free circulation, or export them, unless the customs declaration carries a valid DDS reference.
In plain language, an outbound declaration is the statement you file for goods leaving your hands, plus the reference number that travels with them to customs and to your customer.
Most ERPs already know the order, the batch and the container. What they lack is the link between that shipment, the plot-level evidence behind it and the reference number the EU Information System returns. This guide shows how to build that link so EUDR outbound declarations run on every shipment without re-keying.
Run your product list through TraceX’s free EUDR Scope Check to see which HS codes fall under Annex I after the September 2026 scope change.
The outbound side starts where your inbound evidence ends.
Inbound references are the DDS numbers your suppliers pass to you. Outbound declarations are the statements you submit yourself, which return a reference number and a verification number that you pass downstream. A trading company may receive many inbound references and group them under one outbound DDS for a shipment.
The December 2025 amendment placed DDS filing exclusively on the operator that first places relevant products on the EU market or exports them, usually the EU importer or the EU producer. Downstream operators and traders no longer file their own statements; the first downstream company records and keeps the upstream reference. For most supply chains, EUDR outbound declarations now sit with one company per product flow, which makes that company’s ERP the place where the chain is proven.
One number has to reach five places, and customs is the one that blocks the container.
| Destination | What it carries | Owner |
|---|---|---|
| Customs declaration | Code C716 plus the DDS reference number in the documents section; C717 plus the identifier for simplified declarations | Operator or customs broker |
| Delivery note and invoice | DDS reference and verification number per line or batch | ERP sales and billing |
| First downstream customer | Reference number, so they can record it against their goods receipt | Sales or customer portal |
| Freight forwarder | Reference per consignment before the vessel or truck arrives | Logistics |
| Audit archive | DDS, evidence and reference, kept for five years | Compliance |
One DDS can cover several customs declarations, and one declaration can cite several DDS, so the grouping logic you choose in the ERP matters. Authorities may also hold back a reference number to check a statement, which is why EUDR outbound declarations should be filed days ahead of clearance, not on arrival.
A repeatable sequence turns each shipment into a filed statement.
Flag every item whose HS code falls under Annex I, using the scope as amended by Delegated Regulation (EU) 2026/2102. A missing flag means a shipment never triggers EUDR outbound declarations, and the gap only shows up at the border.
Attach supplier details, plot geolocation, risk assessment results and any inbound references to the batch when goods arrive. EUDR outbound declarations are only as complete as the batch records behind them.
Choose whether one DDS covers a single shipment, a batch, or several shipments of the same product. Document the rule, because auditors will ask how each reference in your EUDR outbound declarations maps to physical goods in the warehouse and on the vessel.
Submit the DDS to the EU Information System, through its interface or an API connection, and write the reference and verification numbers back to the ERP as dedicated fields. From there, EUDR outbound declarations flow onto the delivery note, the invoice, the broker’s customs declaration and the customer record automatically.
DDS consolidation under EUDR can simplify compliance for businesses managing multiple suppliers, sourcing locations and upstream declarations. Discover how grouped Due Diligence Statements work, what the regulatory requirements involve and how consolidation can streamline supply-chain compliance. Read the Blog →

A container is only as clearable as the reference number on its customs declaration.
When one batch splits across three containers, or two batches merge in a warehouse, the reference logic breaks unless the ERP tracks it. References typed into free-text fields get lost before they reach the broker. Fixing these gaps is what makes EUDR outbound declarations scale from a pilot shipment to thousands a year.
How TraceX connects ERP, shipments and DDS
TraceX’s EUDR compliance solution, sits between your ERP and the EU Information System so EUDR outbound declarations run without re-keying. It connects to SAP, Oracle and Microsoft Dynamics through pre-built connectors, links inbound supplier evidence and validated GeoJSON plots to each batch, submits DDS data to the EU Information System via API and writes reference and verification numbers back to the ERP.
The legal methodology was validated by Maruszkin Law Firm, the platform is ISO 27001, SOC 1 and SOC 2 compliant, and EUDR clients in 8 countries already use it. Typical onboarding takes four weeks.

Copy-paste works for ten shipments a year, not for a thousand.
Five outbound steps compared side by side
| Outbound step | Spreadsheets and email | Integrated platform |
|---|---|---|
| Scope flagging | HS codes checked by hand per order | Annex I flags held in item master data |
| Evidence linking | Supplier files searched at shipment time | Evidence linked to batches at goods receipt |
| DDS filing | Data re-keyed into the EU Information System | API submission from shipment data |
| Reference distribution | Numbers emailed to brokers and customers | Numbers written to ERP fields and shipping documents |
| Audit trail | Scattered across inboxes | Order-to-reference lineage kept five years |
Score any vendor on these six questions before your next ERP release.
It is the DDS you file for goods you place on the EU market or export, plus the reference and verification numbers you pass to customs and your first downstream customer.
No. Since Regulation (EU) 2025/2650, downstream operators and traders do not file their own DDS. The first downstream company records and keeps the upstream reference number.
Code C716, entered with the DDS reference number in the documents section of the customs declaration. Simplified declarations use C717 with their identifier.
Yes. One DDS can cover several customs declarations, and one declaration can cite several DDS, as long as the goods are covered.
Before customs clearance, and ideally several days ahead, because authorities may delay a reference number while they check a statement.