21 Aug, 2026
A coffee shipment can be commercially ready and still get delayed by one missing detail: the EUDR due diligence statement reference number.
For coffee importers, that number is more than an administrative code. It links a submitted due diligence statement to a specific coffee lot, shipment file, supplier dataset, and the evidence behind the import. If a customs broker, buyer, auditor, or competent authority asks for it, your team needs to know not only where the number is stored, but exactly what it covers.
The practical rule is straightforward: the EU operator first placing the in-scope coffee on the EU market usually files the EUDR due diligence statement. Once the statement is submitted, the system generates a reference number. The importer then needs to retain that number, connect it to the correct shipment, and pass it on where required.
Coffee makes this harder than it sounds. The industry often moves through small farms, collectors, cooperatives, exporters, warehouses, processors, and freight partners before a shipment reaches Europe. A single container may include coffee from many production plots. That is why the EUDR due diligence statement reference number coffee importers receive is useful only when the underlying data is organized before the container arrives in the EU.
The EUDR due diligence statement, often called the DDS, is the formal statement an operator submits before placing covered products on the EU market or exporting them from the EU. Coffee is one of the commodities covered by the regulation.
For coffee importers, the DDS is the moment when internal due diligence becomes a formal regulatory declaration. Before submitting it, the importer should have collected the required information, assessed deforestation and legality risk, and confirmed that any non-negligible risk has been addressed appropriately.
In practical terms, the file behind a coffee DDS should make the shipment understandable to someone who was not involved in the purchase. It should show what coffee product is being imported, which shipment, container, contract, or lot it relates to, where the coffee was grown, and which farms or production plots are included. It should also show whether the origin data is complete enough to support the statement, what documents support legality in the country of production, who supplied the data, and when it was checked.
The reference number is created after submission. It identifies the submitted DDS, but it does not replace the supporting evidence. If the reference number sits in one system while supplier files, farm data, and shipping documents sit somewhere else with no clear connection, the importer still has a compliance problem.
Coffee importers should treat the DDS reference number as a traceability key. It should unlock the right compliance file, not float around as an isolated code.
The party that files depends on the role in the transaction, not simply the name on the coffee bag.
In a typical direct import, the EU-based coffee importer is the operator placing the coffee on the EU market for the first time. In that case, the importer usually files the EUDR due diligence statement. The non-EU supplier provides essential data, but the supplier does not normally submit the EU importer’s DDS.
That distinction matters. A Vietnamese, Brazilian, Colombian, Ethiopian, or Ugandan exporter may provide farm geolocation data, product specifications, lot records, harvest or production details, and supporting documents. The EU importer then uses that information to conduct due diligence and file the statement.
A simple import example
A French importer buys green Robusta coffee from a Vietnamese exporter. The coffee is shipped to an EU port and released for circulation in the EU.
The exporter provides the product details, lot references, origin information, and traceability documents. The French importer checks whether the data is complete, reviews risk, and keeps the evidence file. Before placing the coffee on the EU market, the importer submits the DDS through the relevant EU system. The submitted statement receives a reference number, which the importer stores and shares with the customs broker or downstream buyer if needed.
The exporter supports the process. The importer owns the filing obligation when it is the EU operator first placing the coffee on the market.
When a coffee company may not file the first DDS
Not every EU coffee business is in the same position.
A roaster that imports coffee directly from outside the EU may need to file the DDS. A roaster buying from an EU importer may instead receive and retain the reference number connected to the coffee already placed on the market. A trader selling coffee already on the EU market may need to pass on reference information and keep records, even if it did not file the first statement.
Before each shipment, the trade flow should answer four plain questions: who is importing the coffee into the EU, who first places it on the EU market, who has the farm-level and supplier evidence, and who needs the DDS reference number after filing. Those answers should be clear before the shipment is already moving.
The filing importer should keep the DDS reference number because it forms part of the compliance record for the coffee placed on the EU market. It should also be shared with other parties that need it for customs clearance, onward sale, or their own record-keeping duties.
Think of the reference number as custody information. The importer should know who received it, which shipment it covers, and where the supporting due diligence file is stored.
A good internal record connects the reference number to the supplier name, contract, product type, HS code or product classification used by the business, shipment references, container details, invoice, bill of lading, lot or batch numbers, country and region of production, farm or plot geolocation data, risk assessment notes, mitigation records, DDS submission date, and the person or team responsible for approval.
Reference numbers should not live only in an email thread. Email may be useful for handoff, but it is weak as the main control point. Store the reference number in a structured system, shipment folder, ERP field, compliance tracker, or shared register with access controls.
Retention also matters. EUDR record-keeping is not only about having the number on import day. Importers should be prepared to keep due diligence records and reference information for the required retention period and make them available if authorities request them. In daily operations, that means the system should still make sense years after the shipment has been sold, blended, roasted, or split across multiple customers.
A reliable EUDR process does not start with filing. Filing comes near the end. The better workflow starts when the purchase is planned.
Step 1: Confirm your role before buying
Start by confirming whether your company is the EU operator first placing the coffee on the market. If yes, prepare to file the DDS. If you are buying from another EU operator, ask how the reference number will be passed to you and what records you must keep.
Do this by trade flow, not by company habit. The same business may be a direct importer for one coffee and a downstream buyer for another.
Step 2: Collect supplier and origin information early
Ask the supplier for the data before shipment deadlines become tight. For coffee, the most sensitive information is usually farm or plot-level traceability. You may need geolocation points or polygons, lot composition, supplier chain records, production period details, and documents connected to legality in the country of production.
Be specific about format. A vague request for “EUDR documents” often leads to missing fields, mixed file types, and late corrections. A clear supplier checklist works better because it tells the exporter exactly what the importer needs in order to review the shipment and prepare the DDS.
Step 3: Connect the coffee lot to the evidence
The due diligence file should show how the physical coffee connects to the origin records. This is especially important for aggregated coffee, where many smallholder plots may feed into one export lot.
Use consistent lot IDs across supplier files, contracts, invoices, warehouse records, and import documents. If a lot is split, blended, or re-bagged, keep a record of what changed and which DDS reference applies to which portion.
Step 4: Check data quality
This is the step that prevents a last-minute DDS problem. Do not wait until filing to discover that farm coordinates are incomplete, a lot number does not match the invoice, or the supplier file covers only part of the shipment.
Check whether coordinates are in the correct format, whether production plots match the claimed origin, and whether the supplied volume makes sense against the lot being shipped. Look for duplicate farm entries, missing producer names, unexplained changes between supplier spreadsheets, and documents that refer to a different crop year or exporter.
For coffee importers, data quality is also about commercial reality. If one container includes several lots, each lot needs a clear evidence trail. If coffee from different origins is blended before import, the due diligence file must still support the full composition. If your broker asks for a reference number, your team should be able to identify the exact DDS without reopening a long chain of emails.
Step 5: Assess risk and document the decision
The importer should assess whether the coffee presents deforestation or legality risk under the EUDR framework. If risk is found, record what mitigation was done. This could include asking for corrected data, requesting stronger supplier evidence, excluding unsupported lots, or delaying filing until gaps are fixed.
Keep the reasoning. A short, dated decision note is much stronger than an undocumented assumption, especially when the person reviewing the file months later was not part of the original sourcing conversation.
Step 6: File the DDS before the coffee is placed on the EU market
Once the due diligence file is ready, submit the DDS through the required system. The filing should reflect the actual product, quantity, origin, and shipment details. After submission, capture the reference number immediately and store it in the compliance record.
Make sure the person filing is working from the latest approved data, not an old supplier version.
Step 7: Share and retain the reference number
After filing, send the reference number to the parties that need it, such as a customs broker, internal logistics team, buyer, trader, or downstream customer. Keep a record of when it was shared and for which coffee.
This is where many teams lose control. They file correctly, but the number is forwarded without context. Add enough detail in the handoff so the recipient knows the shipment, lot, and product covered by the number.
The most common mistake is treating the DDS reference number as the whole compliance task. It is only the identifier for a statement. The real work is the due diligence behind that statement.
Another mistake is assuming the exporter “has EUDR covered” without checking whether the data is usable for the importer’s filing. Supplier support is essential, but the importer still needs to review the file, assess risk, and keep records.
Coffee importers should also be careful with mixed or changing lots. If a shipment changes after the initial supplier file is prepared, the evidence and filing plan should change with it. Old lot documents should not be used to support a different shipment simply because they are already on hand.
Finally, avoid unclear internal ownership. Someone should be responsible for collecting data, someone for reviewing it, someone for filing, and someone for sharing and archiving the reference number. In small teams, that may be one person. In larger companies, it may involve sourcing, compliance, logistics, and customs. Either way, the handoffs need to be visible.
A good supplier makes the importer’s DDS process easier by providing complete, organized, and consistent information. That support may include farm-level traceability, lot records, product specifications, origin documents, packaging information, and timely answers when EU buyers ask follow-up questions.
For coffee, this cooperation is especially important because origin data often sits far upstream. The importer may file the DDS in Europe, but the evidence starts with producers, collectors, cooperatives, exporters, and processors.
Suppliers should not promise that they can remove the importer’s legal responsibility. A better and more credible role is practical support: provide data early, keep lot records clear, explain the supply chain, and help resolve documentation gaps before the shipment reaches the filing stage.
If your team needs a Vietnam-based supplier for wholesale coffee, bulk coffee, OEM/private-label supply, or MR.VIET branded products, MR.VIET can support practical B2B sourcing conversations around traceability, packaging, PPWR, and EUDR-related documentation requests. The useful next step is to contact the team with your target product, volume, destination market, and the buyer documentation you need to discuss.
Is the DDS reference number the same as EUDR compliance?
No. The reference number shows that a due diligence statement has been submitted. It does not replace the evidence behind the statement. Importers still need traceability records, risk assessment, and supporting documents.
Does the coffee exporter file the DDS for an EU importer?
Usually, no. In a standard direct import, the non-EU exporter provides the data and documents, while the EU operator placing the coffee on the market files the DDS. The exact answer depends on the trade structure.
Who should receive the DDS reference number?
The importer should keep it and share it with parties that need it for customs, onward sale, or record-keeping. This may include brokers, logistics teams, traders, roasters, or downstream buyers.
What should coffee importers do first?
Map the trade flow. Confirm whether your company is filing the DDS or receiving a reference number from another EU operator. Then build a shipment-level checklist for origin data, supplier documents, risk review, filing, and reference-number storage.
