EUDR and cocoa: obligations for processors and distributors

This guide covers product scope, the specific obligations of processors and distributors, data flows from cooperatives, geolocation of small plots, how sector certifications fit in, and risk assessment by country of origin. For the general framework, see our complete guide to the EUDR.

In brief

Scope: which cocoa products fall within the EUDR?

The criterion is not the word “cocoa” in a recipe, but the product’s customs code, checked against Annex I of the regulation. This classification is based on the Harmonised System (HS, Harmonized System) and is broken down, at European level, into the 8-digit Combined Nomenclature (CN). So work at CN code level with your customs teams, not just at the 6-digit HS code.

The Chapter 18 codes concerned

Two practical consequences:

1. A processed product does not escape the scope. A bar (1806), a coating or a chocolate powder are covered if the code is listed in Annex I.
2. A product may contain cocoa without falling under Chapter 18 (for example a mixture classified elsewhere according to its composition). Have each item classified reference by reference, with the written justification for the classification.

Why cocoa traceability is harder than elsewhere

Cocoa combines several factors that make documentary evidence more demanding than in other plant-based supply chains.

These findings do not rule out compliance, but they explain why upstream data collection is the critical path of an EUDR cocoa project.

Processor obligations: downstream operator or operator?

For a processor (chocolate maker, manufacturer of powders or ingredients), the regime depends first and foremost on its position in the chain.

Three points of method:

• The 2025 simplification focused due diligence on the operator that first places the product on the EU market. A downstream processor no longer repeats “cascading” due diligence - but it still cannot ignore the origin.
• Traceability is still required: knowing who delivered what to you, and to whom you resold it, with the corresponding references.
• Registration in the EUDR information system may apply to non-SME downstream operators.

Obligations of distributors and traders

A distributor (wholesaler, trading company, retailer) in principle falls under the trader regime (trader): it makes a product available on the market without being the one that first placed it on the market.

The useful reflex: at product reference level, systematically link the DDS reference received from upstream to the batch and the item record, and plan a volume consistency check.

Data flows from cooperatives and smallholders

A cooperative does not take over the operator’s EUDR responsibility: it collects and consolidates information, but due diligence and the statement are the responsibility of the actor placing the product on the market. The cooperative’s operational role is nevertheless central.

What to obtain from the cooperative, producer by producer

• A producer / plot register with a unique identifier per farm and per plot.
• The area of each plot and its geolocation in the expected format.
• The delivery → plot link, to reconstruct batch → origin.
• The legality evidence (documents from the country of production) and information relevant to deforestation risk.
• Traceability of transfers: who delivered what, when, in what quantity.

A five-step collection method

1. Segment cooperatives and traders by criticality (origin, volume, indirect share, presence of forest risk).
2. Standardise the form and formats - including the required geographic format.
3. Equip field collection: mobile GPS survey tools, producer awareness, tracking of mapping progress.
4. Check on receipt: duplicates, consistency of coordinates, plausibility of the declared area against the volumes delivered.
5. Organise data sharing in compliance with the regulations applicable to the protection of producers’ personal data, and document the authorisations.

Some sector schemes make these data flows easier: cooperative digital programmes, national traceability systems set up in the main producing countries, and tools provided by sustainability standards.

Geolocation of plots: the case of smallholdings

This is the most technical point - and the one that most often holds up cocoa files, precisely because the plots are small. The general method is detailed in our guide geolocation of plots.

Useful clarifications for the cocoa sector:

• The threshold applies to each plot, not to a producer’s total land area or the size of the cooperative.
• A GPS point may therefore often be enough for cocoa - but a polygon improves the quality of the risk assessment and makes forest cover monitoring easier. Many buyers choose to collect polygons in advance.
• Geometries must be usable: GeoJSON in WGS 84, coordinates in decimal degrees, longitude then latitude order, closed polygon ring, with no self-intersection.

“[…] the geolocation of all plots of land where the relevant commodities that the relevant product contains, or has been made using, were produced, as well as the date or time range of production […]”Regulation (EU) 2023/1115, Article 9(1)(d) · consolidated text, EUR-Lex

Cocoa sustainability programmes and certifications: contributions and limits under the EUDR

Cocoa has an ecosystem of established programmes and certifications. They are useful, but none of them replaces due diligence or automatically proves EUDR compliance.

For the Cocoa & Forests Initiative reports, see the summary by the World Cocoa Foundation.

The golden rule of reconciliation

If you combine several certifications or programmes, reconcile them on a single foundation: one plot register, one definition of identifiers, one list of batches. Without this foundation, you multiply evidence without being able to demonstrate overall consistency. In substance, the logic is the same as for all supply chains: certification is an element of risk assessment, not a substitute for the obligation.

Supplier risk assessment by country of origin

Risk assessment is not a fixed score: it combines country risk, product risk and supplier risk.

Country benchmarking is set by the Commission (Implementing Regulation (EU) 2025/1093) and may be revised: check the version in force on the date of sourcing. The up-to-date list is available on the European Commission page.

A three-level method

1. Country of origin: official risk level, presence of forests, documented prevalence of illegal production.
2. Region and plot: deforestation risk is uneven within a single country - focus the analysis on areas close to classified forests or reserves.
3. Supplier and chain: chain complexity, share of indirect supply chain, reliability and verifiability of documents, risk of mixing, land rights issues.

If a risk above negligible remains, apply mitigation measures (additional requests, audit, change of origin); if it is not resolved, the product cannot be placed on the market.

Common mistakes in an EUDR cocoa project

1. Believing that processing cocoa exempts you. Status does not depend on processing, but on the first placing on the EU market. A processor that imports is an operator.
2. Thinking a certification is enough. Rainforest Alliance, Fairtrade or a company programme provide evidence, not legal compliance.
3. Forgetting chocolate and processed products. Codes 1806 and cocoa ingredients are in scope.
4. Accepting a GPS point for a plot of more than 4 hectares. A polygon is then mandatory, and a central point with a radius is not a polygon.
5. Decoupling geolocation from the batch. A coordinate not linked to the batch purchased does not become evidence.
6. Ignoring the indirect supply chain and mixing. This is where the biggest gaps between traceable volumes and purchased volumes lie.
7. Failing to retrieve and archive the upstream DDS reference. Without it, the product cannot be linked to the due diligence already carried out.
8. Neglecting producer data. Identifying and geolocating individuals requires a documented data-sharing framework.
9. Underestimating mapping lead times. Plot collection is the critical path, not writing the procedure.

Operational checklist for a cocoa processor or distributor

• Scope and roles
• List of cocoa references classified by CN code against Annex I (written justification kept).
• EUDR role documented per product: operator, downstream operator or trader.
• Size of the entity checked (impact on the applicable date).

• Upstream data
• Direct and indirect suppliers identified, segmented by criticality.
• Producer / plot register with unique identifiers.
• Geolocation collected in the expected format; polygon for plots of more than 4 ha.
• Traceable batch → plot of origin link, with volume checks.

• Evidence and compliance
• Upstream DDS reference retrieved and linked to each batch / item.
• Versioned document management (validity, owner, expiry date).
• Risk grid applied (country, region, supplier) and mitigations recorded.
• Retention guaranteed for 5 years.

• Programmes and management
• Certification(s) reconciled on a single plot and batch reference.
• Sharing of producer data controlled and documented.
• “Audit readiness” test carried out on the most exposed cocoa product (see our audit checklist).
• Dated action plan up to the applicable deadline.

Going further

In cocoa, the difficulty is not understanding the regulation: it is holding together heterogeneous plot data, aggregated batches and documentary evidence scattered across cooperatives, traders and internal systems.