What Is a Downstream Operator Under EUDR?

The covered-input test determines downstream status

A downstream operator places on the market or exports relevant products made using relevant products that are all covered by due diligence statements or simplified declarations. This is the Article 2(15b) definition. Manufacturing or processing is relevant, but does not by itself establish the role.

The word all matters operationally. A production run containing several relevant inputs needs a sound basis for concluding that every relevant input falls within the required coverage. Buying most ingredients from compliant suppliers cannot cure an uncovered relevant ingredient introduced through another route.

Downstream operators fall under Article 5 rather than the ordinary operator statement workflow. This distinction is part of the EUDR supply-chain role model introduced by the amended Regulation. Check the current Articles 2 and 5, rather than assuming that older guidance for non-SME operators still applies unchanged.

Apply the definition to a manufacturing example

Consider an EU processor purchasing relevant cocoa inputs already covered by statements and making a covered cocoa output. If the actual relevant inputs are all covered, the resulting activity can meet the downstream-operator definition. The assessment concerns the input-to-output flow and its commercial event, not a general assurance about the processor's industry.

Now suppose the processor directly imports an additional relevant cocoa ingredient without existing coverage and blends it into the same output. It must resolve the operator obligations for that flow and cannot classify the batch as downstream merely because other ingredients have references. Mixing changes the evidence needed to support the role.

Non-relevant ingredients should be distinguished from relevant products used as inputs. A recipe containing sugar does not mean every ingredient becomes an EUDR commodity. Product classification, the relevant commodity relationship and the actual Annex I entries remain essential to defining what coverage must be established.

Article 5 requires information before supply

A downstream operator must possess Article 5(3) information before placing or exporting its relevant products. This includes the prescribed supplier identities and the identities of business customers to whom it supplies the products. The records must relate to the actual products and remain accessible for at least five years.

When the direct supplier is an operator, the required supplier information includes associated statement reference numbers or declaration identifiers. The statutory wording does not impose the same reference-collection requirement on every later buyer whose supplier is a downstream operator or trader. Extra contractual traceability arrangements should be labelled as such.

This limited reference rule does not weaken the definition's covered-input condition. A downstream operator still needs a supportable classification. Its supplier records, purchasing controls and production links should make that conclusion credible without pretending that the law requires every downstream party to recreate the original operator's full submission.

Registration is different from a new statement

Non-SME downstream operators register in the Information System before the relevant placing or export. Article 5(2) does not say they must submit an ordinary new due diligence statement for every downstream transaction. System registration identifies the business; statement submission communicates an ordinary operator's due diligence conclusion.

SME downstream operators are not given the same registration requirement by that paragraph. They still have Article 5 information, retention, notification and cooperation duties. A smaller company should therefore avoid both extremes: unnecessarily treating every sale as a new ordinary operator statement, or assuming it has no EUDR responsibilities.

A company may separately have operator transactions that require the operator workflow. System access and internal procedures should preserve that distinction. A processor can register as required for downstream activities while also managing ordinary statements for products it directly imports as an operator.

Respond to concerns about covered inputs

Existing coverage is not a guarantee that every later concern can be ignored. Article 5(5) addresses relevant new information about goods already supplied. Downstream operators must immediately inform the prescribed authorities and supplied downstream businesses where the information indicates the relevant risk of non-compliance.

For non-SME downstream operators, Article 5(6) also addresses information before placing or export. Substantiated concerns require verification that due diligence was exercised and found no or negligible risk. Products cannot proceed unless that verification supports no or negligible risk of non-compliance.

For instance, a reliable notice linking an ingredient to a disputed production plot should reach procurement and release control before the next affected batch ships. Record the information, affected products, verification, authority communication where required and the reason for the release or hold decision.

Keep downstream status reviewable

A practical record connects supplier, input code, batch, receiving date, coverage basis, processing order and output lot. This need not duplicate the original operator's entire evidence file, but should allow a reviewer to understand why the inputs used met the definition at the time.

Flag supplier changes, substitute ingredients and emergency purchases as review triggers. These are common points where a processor silently moves from covered-input manufacturing into a new operator flow. Do not let an enterprise-wide downstream label override the facts of the new route.

The comparison of operators and downstream operators helps document borderline situations. Record uncertain classification questions before supply, and seek a fact-specific authority clarification where the existing legal definition does not resolve an unusual arrangement.

Keep a record of the approved input list alongside the output assessment, so an auditor can distinguish the actual recipe used from a standard recipe that changed during production.