Choosing the Right Product Codes for EUDR

In EUDR, “correct product coding” is not just customs classification. It determines whether your inputs, evidence, and declaration fields align from supplier intake through shipment submission.

In this article, a production plot is the land where coffee or rubber is grown; a shipment lot is one export shipment (often one container) those plots feed into.

Two code layers you usually meet

1. Harmonised System (HS) code: the international product code used in the due diligence statement.
2. EU customs coding (often Combined Nomenclature — CN): the code you may use in EU customs workflows, which you then need to map to the correct HS code for the statement.

If the HS code used in the statement is derived inconsistently (or if free-text entry is allowed), you can end up with “evidence is fine, but the declaration data is wrong”.

Annex I scope: not every code inside a chapter is eligible

EUDR is tied to Annex I. The practical takeaway:

• Not every code under the same chapter is in scope
• Only the branches / codes that fall under Annex I (sometimes marked as ex) should be used for EUDR commodity mapping and product description

So “correct chapter” is not enough — you need the correct Annex I branch.

The seven Annex I commodity groups to map

Most operational EUDR workflows revolve around these seven groups:

• cattle
• cocoa
• coffee
• palm oil
• rubber
• soy
• wood

When you normalize your catalog:

• keep codes mapped consistently from your operational catalog,
• map commodity to exactly one of the seven groups above,
• use the correct Harmonised System code in the due diligence statement for your product data.

A low-error way to run code picking

1. Pick codes from a curated list (avoid free-text entry).
2. Ensure the commodity belongs to the Annex I seven-group set.
3. Ensure the HS code inside the statement is mapped consistently across teams.
4. Handle ex branches by keeping the correct Annex I meaning (don’t substitute “similar” codes).
5. Understand that code changes can impact the shipment evidence pack and record ownership.

Quick checklist

• Code is detailed enough and belongs to Annex I (not just “right chapter”)
• Commodity is one of the seven Annex I groups
• Harmonised System code in the statement matches your product data
• Product description and declaration records use the same coding source
• If codes change, you know which shipment / lot records are affected

Where the Desk helps

If you work shipment by shipment, the Desk focuses on turning code selection and evidence packaging into a consistent workflow. That cuts rework before deadlines — while statement ownership stays with the EU operator.

Sources

• Regulation (EU) 2023/1115 (EUDR) consolidated text: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A02023R1115-20241226
  • Annex I: covered commodities and eligible product codes
  • Annex II: due diligence statement includes the Harmonised System code and product data