EUDR 2026 Checklist for U.S. Suppliers: Product Codes, Origin Data, and Geolocation

Does a U.S. supplier have to file under EUDR?

The short answer is no—not simply because it sells coffee, cocoa, wood, rubber, soy, cattle, or palm oil products into an EU-facing supply chain.

The European Union Deforestation Regulation (EUDR) does not automatically make every producer outside the EU a direct filer. The answer changes, however, when a U.S. company itself places a relevant product on the EU market. According to the European Commission’s implementation FAQ, a non-EU company in that position may be treated as an operator.

If the EU importer or customer handles first placement, the U.S. supplier may function primarily as a data provider rather than the party submitting the due diligence statement. That distinction does not eliminate commercial exposure: an EU operator that cannot obtain the required information may be unable to place the product on the market.

Separate the question into two tracks:

• Legal responsibility: Who first places the product on the EU market or exports it from the EU?
• Data dependency: What information does that party need from the U.S. supplier to complete due diligence?

A supplier can have limited direct filing responsibility and still be essential to its customer’s compliance process.

What changes in 2026?

EUDR covers cattle, cocoa, coffee, oil palm, rubber, soy, and wood, along with certain products listed in Annex I.

The European Commission’s published application schedule distinguishes among business categories:

Business category	Application date
Large and medium operators	December 30, 2026
Micro and small operators	June 30, 2027
Micro and small operators already covered by the EU Timber Regulation	December 30, 2026

A U.S. supplier should not apply these dates solely by looking at its own headcount or revenue. First identify the operator, downstream operator, and trader in the relevant EU transaction.

If the U.S. company directly places the product on the EU market, its role and size may affect the analysis. If an EU customer is the operator, that customer’s deadline and onboarding schedule may determine when supplier data must be ready.

First check: Is the EU product code in Annex I?

The first question is not whether the product contains a relevant commodity. It is whether the product’s EU classification appears in EUDR Annex I.

The international Harmonized System uses six-digit codes. The EU Combined Nomenclature (CN) extends those classifications to eight digits, and EUDR Annex I defines covered products through CN references. A more detailed TARIC code may also appear during EU import processing.

This distinction prevents a common scope error. A finished product can contain natural rubber or wood without being covered if its classification is absent from Annex I. Another processed product may be covered because its code is specifically listed.

For each EU-bound product, confirm:

1. The eight-digit CN code used by the EU importer.
2. Whether that code appears in EUDR Annex I.
3. Whether processing changes the code or the parties’ supply-chain roles.

Do not treat an old classification spreadsheet as permanent. Classification records should be reviewed when product specifications or applicable EU nomenclature change.

Second check: Who first places the product on the EU market?

Contract labels alone do not establish the EUDR role. The operational transaction matters.

Question	Why it matters
Who performs EU import clearance and release for free circulation?	This is a key indicator of first placement on the market.
Does the U.S. company place the product directly on the EU market?	It may be treated as a non-EU operator.
Does the company have a valid EORI connected to an EU member state or Northern Ireland?	This can affect access and filing arrangements for a non-EU operator.
Who is the first EU-based recipient or supplier?	That party may also have operator responsibilities in a direct non-EU placement structure.
Is the EU customer distributing a product already placed on the market?	Downstream-operator or trader requirements may apply instead.

EUDR distinguishes among operators, downstream operators, and traders. Their obligations are not identical.

Operators generally need a due diligence system covering information collection, risk assessment, and risk mitigation when required. Downstream parties may have different information and recordkeeping duties depending on their size and position in the chain.

Third check: Can the required data be connected to a shipment?

The practical problem is rarely that no records exist. More often, the records exist in separate systems and cannot be tied back to the same shipment or lot.

Data category	What the supplier should be able to show
Product identity	Product name, lot or batch identifier, and EU CN code
Quantity	The amount connected to the shipment or due diligence record
Trading parties	Direct supplier and direct commercial customer information
Country of production	Where the relevant commodity was produced, rather than merely processed
Production period	Harvest date, harvest range, or other applicable production period
Production location	Geolocation of the production plot or relevant cattle establishments
Legality	Verifiable evidence addressing applicable laws in the country of production
Record linkage	A documented connection among the coordinates, evidence, quantity, and lot

Imagine a supplier receiving a customer questionnaire with fields for CN code, production country, harvest period, and plot coordinates. The company may have each item somewhere, but if the coordinates cannot be matched to the beans, timber, rubber, or other material in that shipment, the data package may still be unusable.

The better readiness test is therefore not “Do we have coordinates?” It is “Can we reconstruct the path from this shipment to the relevant production locations?”

Fourth check: Are the geolocation records usable?

Operators must obtain geolocation information for the land where the relevant commodity was produced. Low-risk classification does not automatically remove that traceability requirement.

The Commission FAQ describes the basic format as follows:

• For commodities other than cattle, a production plot larger than four hectares requires a polygon describing its perimeter.
• A plot of four hectares or less may be represented by a polygon or a single latitude-and-longitude point.
• Establishments where cattle were kept may be represented by a single geolocation point.
• Coordinates are expressed using latitude and longitude with six decimal digits.

Possessing a coordinate file is only the first step. Where material is aggregated, mixed, or continuously processed, the supplier must be able to identify the production locations that could be associated with the relevant product.

This is where I would slow down during a readiness review. A folder full of maps and certificates can look complete while still lacking the one connection an EU customer needs: which locations correspond to this lot and quantity.

Fifth check: Do origin records identify the production country?

For EUDR purposes, the relevant production country is where the commodity was grown, harvested, raised, or otherwise produced. It is not necessarily the country where the commodity was processed or the finished product was manufactured.

For example, cocoa harvested in one country may be processed into cocoa powder in another before entering the EU. The legality analysis still needs to address the laws of the country where the cocoa was produced.

Supporting materials may include government records, contracts, judicial decisions, impact assessments, or audit documentation. Their existence alone is not decisive. The EU operator must consider whether the information is verifiable and reliable.

Keep these fields separate:

• Commodity production country
• Intermediate processing country
• Final manufacturing country
• Legality evidence connected to each production location
• Issuing authority and applicable period for each record

An operational sequence for responding to EU customers

1. Narrow the product list

Start with the CN codes used for EU imports. Separate potentially covered products from products whose codes are not listed in Annex I, and retain the classification basis for that decision.

2. Map the role for each transaction

The same company may be a foreign supplier in one arrangement and a non-EU operator in another. Identify who conducts import clearance and first placement rather than relying on a general contract label or Incoterm alone.

3. Run a lot-level traceability test

Choose one representative EU shipment and trace it backward to the production locations. The first break in quantity, origin, production-period, or coordinate linkage is the most useful indicator of the current data gap.

4. Define the customer data exchange

A contract promising to “provide EUDR information” is too broad for reliable execution. Agree on required fields, accepted file formats, submission timing, corrections, retention expectations, and notification of supply-chain changes.

5. Separate filing ownership from data ownership

Legal or customs teams may own the filing analysis, while procurement, quality, and supply-chain teams collect the underlying records. Both sides should use the same shipment and lot identifiers.

Three mistakes to avoid

The first is stopping at “EU law does not apply to U.S. companies.” A producer outside the EU is not automatically a direct filer, but a non-EU company can take on an operator role when it directly places covered products on the EU market. Customer data requirements may also become a condition of trade.

The second is treating every product containing a relevant commodity as covered. Annex I product classifications determine scope.

The third is assuming that one certificate of origin or sustainability certificate satisfies the entire information requirement. Product identity, quantity, production country, production period, geolocation, and legality evidence must remain connected well enough for the operator to assess risk.

What should suppliers monitor next?

The most decision-useful developments will come from EU customers’ operating procedures rather than broad statements about the regulation. Monitor:

• The CN codes each customer classifies as covered
• The designated operator and filing party for each transaction
• Required geolocation file formats and validation rules
• Treatment of mixed material and multiple production locations
• Correction deadlines and shipment-hold criteria for missing data
• Reassessment procedures after product or supply-chain changes

The immediate checkpoint is straightforward: select one EU-bound product and attempt to trace a real shipment from its CN code and quantity back to its production period, country, and geolocation. That test will show whether the main issue is legal-role analysis, missing data, or broken record linkage.

Official sources

The application timeline and implementation criteria used here come from the European Commission’s EUDR overview and FAQ on EUDR implementation.