How Downstream Businesses Use Reference Numbers

Start with the supplier's role

Under the revised EUDR, downstream operators and traders must collect the reference numbers or declaration identifiers associated with relevant products when their supplier is an operator. Article 5(3)(a) places that identifier requirement alongside the prescribed supplier identity information. It does not impose the same general identifier-collection duty where the immediate supplier is instead a downstream operator or trader. This distinction matters when designing receiving records.

A downstream business should therefore establish both its own role and its supplier's role for the transaction. The commercial label “wholesaler” does not answer that question. A wholesaler importing one product may be its operator, while selling another product already covered upstream as a trader. The identifier workflow should follow the particular flow rather than a permanent label attached to the supplier's company name.

Direct supply from an operator

Where the supplier is the operator, obtain the statement reference or simplified-declaration identifier associated with the goods, together with the required supplier details. Keep the association sufficiently clear to explain which purchased products the identifier relates to. An undated list of numbers in a general supplier folder is less useful than a record connected to the affected order, lot or delivery.

For example, a manufacturer buying covered timber directly from an importer should be able to identify the relevant upstream record for the purchased products. If the supplier provides several references without explaining their product coverage, resolve that uncertainty before treating the information requirement as complete. A syntactically valid number connected to unrelated goods is not a meaningful traceability record.

The Information System guide explains the difference between the main identifier and the associated security number. Use distinct fields so a receiving clerk does not accidentally enter a verification number as the statement reference.

Supply from another downstream business

Where the immediate supplier is a downstream operator or trader, Article 5 still requires the specified supplier and customer information, retention and the applicable cooperation or notification duties. The ordinary identifier-collection rule in Article 5(3)(a), however, is expressly tied to the case in which the supplier is an operator. Avoid presenting an uninterrupted transmission of references through every sale as a universal statutory obligation under the revised text.

Businesses may choose more extensive contractual traceability arrangements. A customer can ask for additional information to support a particular risk review or commercial requirement. Label those arrangements accurately and assess their practical and confidentiality implications. A contract asking for upstream references is different from a claim that every downstream seller must submit a new ordinary due diligence statement.

Registration does not mean resubmission

Non-SME downstream operators and non-SME traders must register in the Information System under Article 5(2). Registration provides the required participation in the regulatory framework. It should not be used to infer an ordinary statement duty that the revised Article 5 does not impose. Large company status alone does not convert every purchase into a fresh operator declaration.

This distinction is particularly relevant to legacy compliance software. A workflow built for the earlier actor model may automatically create downstream statements whenever an upstream number is received. Review the legal trigger before retaining that automation. The correct process may involve recording the supplier and associated identifier, retaining the information and addressing concerns rather than generating an unnecessary new statement.

Retention, concerns and authority cooperation

Article 5 requires the prescribed information to be kept for at least five years from the relevant placing, making available or export and provided to authorities on request. Keep records in a form that remains usable after supplier account changes, enterprise software migration or staff turnover. A portal link that becomes inaccessible when a contract ends may be an inadequate operational retention plan.

Receiving a number also does not justify ignoring later information about non-compliance. The revised law contains notification and action obligations when downstream businesses obtain relevant information or become aware of substantiated concerns. Record the concern, affected products and response rather than assuming the upstream statement prevents further responsibility. The presence of an identifier and the absence of a known compliance problem are different facts.

A practical receiving and release check

For each relevant purchase, identify the supplier role, collect the prescribed identity details, obtain associated identifiers where the supplier is an operator, and connect the record to the goods. Record customer information for the relevant onward supplies and the required retention period. Build an escalation route for missing information or a credible concern about the products.

The reference number guide helps explain what the code does and does not prove. A useful test is to select a delivery received six months earlier and reconstruct its supplier, legal role, product association and onward customer records. If that exercise depends entirely on one employee remembering an email, strengthen the information process before increasing the volume of transactions handled through it.

Agree how the supplier will communicate corrections to previously supplied identifiers or product associations. A buyer needs a practical route to update its records when a valid grouping or another relevant change affects the information already received. Retain the earlier communication and the correction together. This makes it possible to explain which information was held at the time of a transaction and how the business responded afterwards.