EU Deforestation Regulation customs and import release readiness

Do not wait for the customs broker or import filing to discover an EUDR gap. Before a relevant product is placed on the EU market or exported, confirm that the product is in the EUDR scope, that the operator has completed due diligence or the applicable simplified declaration route, and that the release file includes the due diligence statement reference number or declaration identifier needed for the shipment.

A customs-release checklist should therefore be an evidence checkpoint, not a substitute for due diligence. If the required reference is missing, if the supplier cannot identify the operator responsible for the statement, or if new information suggests non-compliance, the product should be held from release planning until the EUDR owner resolves the gap.

The EUDR reference number is a handoff control. Operators submit the due diligence statement through the Article 33 information system after due diligence shows no or negligible risk, then communicate the reference number to downstream operators and traders further down the supply chain. Where a micro or small primary operator uses a simplified declaration route, the handoff should capture the declaration identifier instead.

For import release, the receiving team should match the reference or declaration identifier to the supplier, product, shipment, and internal evidence file before instructing release. The FAQ answer should not claim a specific customs declaration box, data element, or national filing format unless that mechanic is separately confirmed from an official customs source.

The handoff should be explicit about roles. The operator remains responsible for compliance when it makes a due diligence statement available, even if an authorised representative submits the statement on its behalf. Downstream operators and traders need supplier information and, where the supplier is an operator, the due diligence statement reference number or declaration identifier.

Customs brokers can help enforce release readiness, but they should not be made the owner of EUDR due diligence unless they actually hold that legal role. Give brokers the identifiers and release instructions they need; keep product scope, supplier evidence, geolocation evidence, risk assessment, mitigation, and authority-response ownership with the EUDR compliance owner.

Keep evidence that proves why the product was considered ready for release, not just a screenshot or shipment email. The EUDR due diligence file should show information collection, risk assessment, risk mitigation where needed, the submitted due diligence statement or simplified declaration route, and the reference or declaration identifier handed to downstream parties.

Retention should cover both the customs-release event and the EUDR evidence behind it. The grounded record set includes due diligence statements kept by operators, Article 9 information and evidence such as geolocation and documentation demonstrating deforestation-free and legal production, and Article 5 supply-chain information kept by downstream operators and traders.

The common mistake is to treat EUDR customs release as a filing-format problem. The official grounding supports due diligence statements, reference numbers, information-system workflows, and supply-chain handoffs; it does not justify unsupported claims about exact customs declaration fields, national data elements, or automatic clearance outcomes.

The safer operating model is to make customs release dependent on a matched EUDR reference or declaration identifier and a complete evidence file. That gives import, procurement, sustainability, and broker teams a practical stop point without pretending that a customs filing alone proves EUDR compliance.