What should teams do before customs or import release under the EUDR?
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 reference number or declaration identifier needed for the shipment.
Article 26 requires the reference number, or the declaration identifier for an eligible micro or small primary operator, to be made available to before or export. Except where the statement is supplied through the Article 28 electronic interface, the person lodging the customs declaration provides that identifier. Article 26(4) excludes exports by downstream operators from this paragraph; the exclusion does not remove their separate Article 5 duties.
- Confirm the relevant product and commodity are in the EUDR scope before the shipment is approved for release.
- Record whether the party responsible is acting as operator, downstream operator, trader, importer, authorised representative, or customs broker support.
- Require the reference number or applicable declaration identifier before or export, subject to the downstream-operator export exception in Article 26(4).
- Keep the evidence file separate from the customs filing so teams do not mistake a reference number for proof that the underlying due diligence is complete.
Supports the customs-readiness gate: relevant products must meet Article 3 conditions and be covered by a due diligence statement or simplified declaration where required.
Supports the page's high-level EUDR context for proving products are deforestation-free before they are placed on the EU market.