Quick summary: Learn how importers can manage EUDR inbound goods by linking DDS references with suppliers, customs, purchase orders, batches, goods receipts and ERP systems.
EUDR Inbound Goods are becoming an important operational consideration for importers, manufacturers and traders preparing for the EU Deforestation Regulation. The challenge is no longer simply obtaining a Due Diligence Statement (DDS) from a supplier. Businesses need to connect the DDS reference, supplier, origin, geolocation, shipment, customs declaration, batch and goods receipt so that EUDR information remains traceable throughout the inbound process.
For companies importing EUDR-relevant commodities and products into the European Union, one of the most practical questions is what happens when the goods actually arrive. A supplier may have provided a Due Diligence Statement (DDS) reference number, but how does that reference move into the importer’s operational systems? Can it be linked to the purchase order, inbound delivery, goods receipt and batch? How does the business know which quantity is covered? And can compliance teams trace the material back to the supplier and production origin?
These questions turn EUDR from a regulatory exercise into an operational data problem. The European Commission states that for relevant products entering the EU market, due diligence must have been carried out, the DDS or simplified declaration submitted, and the reference number or declaration identifier obtained before the customs declaration is lodged. The customs declarant must include the applicable reference or identifier on the customs declaration.
For enterprise importers, that creates a critical connection between compliance data and the physical flow of goods.
EUDR inbound goods management is the process of connecting incoming EUDR-relevant materials or products with the information needed to demonstrate due diligence and manage the import workflow.
A useful operational chain is:
SUPPLIER → PURCHASE ORDER → INBOUND DELIVERY → DDS → CUSTOMS → GOODS RECEIPT → BATCH → INVENTORY
The exact system sequence will differ by organisation. In some businesses, customs clearance happens before the warehouse goods receipt; in others, an advance inbound record may be created before physical arrival. The important principle is that the EUDR reference should remain connected to the transaction and product records it supports.
This is often the first question procurement, logistics and compliance teams ask. The supplier may provide the DDS reference through a purchase document, shipping documentation, portal, email or another channel. The business then needs to capture it reliably.
A mature process should avoid leaving the reference only in an email or PDF. Instead, it should become a structured data field linked to the relevant supplier, product, shipment and quantity.
For example:
SUPPLIER → DDS REFERENCE → PURCHASE ORDER → INBOUND DELIVERY → MATERIAL/BATCH
This makes the reference searchable and gives compliance and logistics teams the same source of information.
A DDS reference number isn’t the end of the EUDR workflow. Can you quickly trace each reference back to the right supplier, product and shipment?Learn how to manage EUDR reference numbers effectively.
This is where EUDR becomes an ERP integration question. Buyers are increasingly asking whether the DDS reference can be connected to existing SAP, Oracle, Microsoft Dynamics or other ERP workflows rather than maintained in a separate spreadsheet.
The practical objective is not necessarily to make the ERP the EUDR compliance system. Instead, the ERP can remain the system of record for procurement, inventory and logistics while a specialised traceability layer manages EUDR origin, geolocation, due-diligence evidence and DDS relationships.
A connected architecture can look like:
ERP PURCHASE ORDER → TRACEABILITY / EUDR RECORD → DDS → CUSTOMS → ERP GOODS RECEIPT
The Commission has also updated the EUDR Information System’s technical framework and API specifications, supporting automated interactions with the system.

A buyer may ask whether a goods receipt should proceed if the relevant EUDR information is missing. This is primarily an internal control question rather than a rule that automatically requires every ERP goods-receipt process to be blocked.
Companies can define their own control points based on their legal role, import process and risk appetite. For example, an organisation may configure an EUDR status such as:
This provides visibility without assuming that the EUDR Information System itself is an ERP warehouse-control system.
Complex shipments can involve more than one DDS reference. The Commission confirms that where multiple DDS references or declaration identifiers apply, multiple references can be included in one customs declaration. It also confirms that where one DDS covers multiple shipments or batches, the same reference can be used in several customs declarations as long as the EUDR requirements are respected.
For enterprise systems, this means the data model should not assume a simple one-to-one relationship between shipment and DDS.
A more realistic model is:
SHIPMENT ↔ MULTIPLE DDS REFERENCES ↔ MULTIPLE PRODUCTS / BATCHES / QUANTITIES
This becomes particularly important when a container combines products from different origins or when several declarations support one commercial movement.
Managing multiple EUDR DDS records? Learn how to consolidate declarations, simplify traceability and maintain control across your supply chain.Read the guide on EUDR DDS Consolidation.
Yes, a single DDS can cover multiple physical batches or shipments where the legal requirements are met. The Commission specifically notes that the same DDS reference may be referred to in several customs declarations when a DDS covers multiple shipments or batches.
The operational challenge is quantity control. The importer should be able to determine which receipts or shipments draw on the declared quantity and whether the DDS still covers the relevant flow.
This is why quantity-level traceability matters as much as reference-number storage.
Consider an importer with a DDS covering 500 tonnes of a relevant commodity. If the material arrives in five deliveries, the compliance team needs visibility into the relationship between the declared quantity and the quantities received.
A useful model is:
DDS QUANTITY → SHIPMENT 1 → RECEIPT 1
→ SHIPMENT 2 → RECEIPT 2
→ SHIPMENT 3 → RECEIPT 3
→ REMAINING QUANTITY
The EUDR rules allow a DDS to cover multiple batches or shipments, but once the quantity covered by the DDS has been used, a new DDS is required for additional quantities.
This makes quantity allocation an important control for high-volume importers.
This is a common operational scenario, but it should be separated from the customs requirement. For imports, the reference number or simplified declaration identifier must be obtained before the customs declaration is lodged.
Therefore, receiving a reference after physical arrival is not the same as satisfying the import timing requirement. Companies should design supplier processes so the necessary information is available early enough for customs and internal controls.
An exception workflow can flag shipments where the physical goods have arrived at a warehouse or port but the relevant EUDR record is incomplete, allowing teams to investigate rather than relying on manual email follow-up.
This is arguably the most valuable capability for an enterprise importer. The DDS reference should be more than a customs field. It can be connected to the supply-chain evidence behind the product.
The ideal traceability chain is:
SUPPLIER → FARM/PLOT → GEOLOCATION → COMMODITY → DDS → SHIPMENT → BATCH → GOODS RECEIPT
This allows compliance teams to answer questions such as: Which production locations support this batch? Which supplier provided it? Which DDS covers the material? Which shipment received it? Which inventory or production records consumed it?
The European Commission also requires upstream operators to pass their DDS reference number to direct downstream buyers for traceability, while first downstream operators and traders have record-keeping obligations for the references they receive.
From geolocation to due diligence connect the EUDR dots. → Read More
Once an inbound material is received, the EUDR information should remain connected to the batch or inventory record where appropriate. This is especially important when the material is transformed or combined with other inputs.
For example, a manufacturer importing cocoa may need to connect the incoming cocoa batch to the production order and finished product batches that use it. The exact legal obligations depend on the company’s role and the products involved, but from a traceability perspective, preserving the upstream link reduces the effort required to answer customer, audit or compliance questions.
A practical model is:
INBOUND BATCH → PRODUCTION ORDER → FINISHED PRODUCT BATCH → OUTBOUND TRANSACTION
The strongest enterprise EUDR integrations are not about duplicating the ERP. They are about connecting systems around the events each system is best positioned to manage.
This creates a controlled data flow instead of requiring teams to copy EUDR references manually between systems.
Imagine an EU manufacturer importing natural rubber from several suppliers. Each supplier provides a DDS reference associated with the relevant production origins. The shipment arrives with multiple batches, and the manufacturer needs to connect the incoming material to its ERP purchase order, customs process and warehouse receipt.
A fragmented workflow might leave the compliance team searching emails to identify which DDS belongs to which batch.
A connected workflow can maintain:
SUPPLIER → ORIGIN → GEOLOCATION → DDS → CUSTOMS → INBOUND DELIVERY → BATCH → INVENTORY
When the rubber is later consumed in manufacturing, the upstream traceability relationship remains available for internal controls and downstream information requests.
The EUDR-specific timing requirement for imports is tied to customs: due diligence must be completed, the DDS submitted and the reference obtained before the customs declaration is lodged. Whether an organisation blocks its internal goods-receipt process is an internal control decision.
Businesses can design integrations that connect ERP procurement, material, batch and shipment data with a specialised EUDR traceability workflow. The Commission’s Information System also supports API-based automation.
Yes, where the legal requirements are met. The Commission states that the same DDS reference can be used in several customs declarations when the DDS covers multiple shipments or batches.
Yes. The Commission states that multiple DDS reference numbers or declaration identifiers can be included in one customs declaration.
The current roles-and-responsibilities guidance states that first downstream operators or traders must keep DDS reference numbers or simplified declaration identifiers for at least five years. The exact record-keeping obligation depends on the actor’s role.
TraceX EUDR Solutions can help enterprises connect EUDR compliance data with operational supply-chain events. Instead of storing DDS references separately from procurement and inventory records, TraceX can link supplier, origin, geolocation, product, shipment, batch and compliance information into a traceable record.
The goal is to make EUDR part of the operational supply chain rather than a separate compliance spreadsheet.
For enterprise importers, EUDR compliance becomes much easier to manage when the DDS reference is treated as part of the inbound supply-chain record. The strongest model connects supplier and origin information with customs, shipments, quantities, batches and goods receipts.
The practical chain is:
SUPPLIER → DDS → CUSTOMS → INBOUND DELIVERY → GOODS RECEIPT → BATCH → INVENTORY
Behind that operational chain sits the deeper evidence trail:
SUPPLIER → ORIGIN → GEOLOCATION → RISK/EVIDENCE → DDS
This approach helps teams answer the questions that matter: Which DDS covers this material? Which supplier and origin support it? How much quantity has been received? Which batch consumed it? Can we retrieve the evidence?
EUDR readiness is not just about filing a DDS. It is about making that DDS reference usable across the flow of goods.