Operator vs Downstream Operator

The difference is the covered-input condition

An ordinary EUDR operator places relevant products on the market or exports them, excluding downstream operators. A downstream operator does so with relevant products made using relevant products that are all covered by due diligence statements or simplified declarations. The distinction comes from Articles 2(15) and 2(15b), rather than whether the company calls itself a processor.

The practical consequence is substantial. Ordinary operators follow Article 4, including due diligence and the ordinary statement route unless the targeted Article 4a primary-operator regime applies. Downstream operators follow Article 5, including information retention and, for non-SMEs, Information System registration.

Use this comparison within the complete supply-chain role framework. A trader is a third category, commonly relevant to unchanged resale. The current consolidated Regulation should control the assessment because older two-role explanations can misstate what downstream businesses must submit.

Compare two sourcing routes

Imagine a covered-product manufacturer sourcing all relevant inputs from EU suppliers with the necessary existing statement or simplified-declaration coverage. If the output and activity meet the definition, that manufacturing flow can qualify as downstream. The business should keep evidence linking purchased inputs to the production runs using them.

Compare a manufacturer importing an uncovered relevant input directly from a third country. Its ordinary operator obligations for that market-entry flow must be resolved before supply. It cannot apply downstream treatment simply because it processes the imported material after arrival or buys its other inputs from EU sources.

The difference is not domestic versus international ownership. A foreign-owned EU company can manufacture from covered inputs, while an EU-owned company can be the first relevant importer. Establish the responsible person, product and coverage rather than relying on the nationality of the corporate parent.

What each role does before release

The ordinary operator gathers production and supply information, assesses risk and mitigates it where necessary. It submits the ordinary due diligence statement before placing or export, assuming responsibility for Article 3 compliance. It cannot proceed with non-compliant products, non-negligible risk or an inability to fulfil the required obligations.

The downstream operator must possess the Article 5(3) supplier and business-customer information before its placing or export. Reference numbers or declaration identifiers are part of that supplier information only where its supplier is an operator. This is not a general instruction to generate another ordinary statement for the downstream output.

Both workflows require meaningful product identification. An operator's full assessment needs to cover the relevant goods, while downstream information must be usable for the goods actually handled. A generic supplier letter saying all products comply cannot replace the factual basis for either classification.

Separate system access from legal responsibility

Non-SME downstream operators must register in the Information System under Article 5(2). The obligation to register does not turn them into ordinary operators or require a new statement merely because the system has a statement submission function. Internal manuals should state which activity each system action supports.

An ordinary operator can mandate an authorised representative under Article 6 to submit on its behalf, but retains responsibility. A downstream company helping an upstream natural person or microenterprise with submission must distinguish representative activity from its own commercial role.

Within one company, assign separate workflow labels such as direct import and covered-input processing. This makes it easier to prevent an ordinary operator shipment from being released using only downstream records, and to avoid creating unnecessary downstream statements based on an obsolete compliance template.

Understand the shared duties and different triggers

Downstream status does not remove the Article 3 prohibition on non-compliant goods. Article 5 includes record retention for at least five years, authority cooperation and immediate notifications when relevant new information indicates that products already supplied risk non-compliance. Keep a process for linking alerts to both inventory and previous customers.

Non-SME downstream operators face the additional pre-supply Article 5(6) response, including verification in the event of substantiated concerns. The ordinary operator separately has Article 4 release and notification duties. Matching the right trigger to the right role is more useful than telling every department to perform generic due diligence.

A suspicious geolocation update from an input supplier is one example. Identify affected inputs, the output lots using them and the role in each transaction. A current reference number does not justify ignoring credible information that undermines the underlying compliance conclusion.

Record the decision and review it

Create a comparison record with the legal entity, relevant output, all relevant inputs, coverage basis, source route and proposed market or export event. Explain why Article 2(15b) is met or why the business remains within the ordinary operator definition. Have a named owner approve the classification before production or supply begins.

Review the record when recipes change, new suppliers enter, emergency procurement occurs or a new company takes over importing. These events can break the assumptions supporting downstream status even though the finished product name remains unchanged.

The article on manufacturers and processors under EUDR applies this comparison to bills of materials and production control. Preserve separate decisions for different flows instead of forcing the whole company into one permanent category.

Where a conclusion depends on upstream coverage, record which goods and production runs that coverage supports. This prevents a valid document for one material from being reused for an unrelated substitute.