For natural rubber lots, the first downstream operator still needs a usable record set. Reference numbers help, but they are not the whole file.
Matheus Peguim
Before a natural rubber lot moves into a buyer review flow, teams often focus on one question: is there a due diligence statement reference number attached to the file?
That number matters where it applies, but it is not the whole job.
For mills, exporters and industrial buyers handling rubber lots, the more useful question is narrower and more operational: what should the first downstream operator or trader actually keep so the lot remains readable after the latest EUDR changes?
Regulation (EU) 2025/2650 did not turn the downstream file into a single reference number exercise. It clarified a differentiated set of obligations. For natural rubber supply chains, that means teams still need a record structure that connects supplier identity, quantity, lot logic and the evidence path behind the material.
Article 5 of Regulation (EU) 2023/1115, as amended by Regulation (EU) 2025/2650, distinguishes downstream operators and traders from upstream operators. For the first downstream actor, one key point is easy to miss: the duty to collect reference numbers of due diligence statements or declaration identifiers applies when the direct supplier is an operator.
That is useful for administrative continuity. It is not a substitute for the rest of the file.
The same downstream article still points to other information that has to stay with the relevant products, including supplier identity and quantity. In practice, a natural rubber lot remains hard to defend if the team can show a reference number but cannot explain which supplier supplied the material, which intake records support the quantity, and how the lot moved toward shipment.
For a mill or exporter, the first downstream file should start with four visible blocks.
First, supplier identity. Keep the legal or commercial identity of the supplier that delivered the relevant products, along with the contact details the regulation points to. If the supplier is an operator, this is where the due diligence statement reference number or declaration identifier belongs.
Second, quantity. The lot file should show the quantity linked to the relevant products in a way that matches intake, production logic and shipment logic. If the commercial invoice says one thing and the internal lot balance says another, the file is already weak.
Third, lot readability. The downstream file should make it clear which physical lot or shipment the records refer to. Internal lot code, product description, date window, processing unit and shipment reference should line up. If the material was merged, split, reworked or reclassified, that should not stay hidden in separate spreadsheets.
Fourth, supporting path. Even where the downstream actor is not repeating the upstream due diligence process, the file should still let a reviewer understand how the material connects back to the records already in circulation. A reference number can point to a declaration, but it does not explain the operational story of the lot on its own.
The first mistake is treating the reference number as if it closes the review. It does not. It helps the next actor find an upstream declaration. It does not explain intake discrepancies, supplier corrections, mixed lots or missing shipment logic.
The second mistake is keeping a commercial file and an operational file that never really meet. Procurement may hold supplier records. Production may hold batch logic. Logistics may hold shipment papers. When those pieces are not reconciled before dispatch, the downstream file looks complete until someone asks a harder question.
The third mistake is dropping exception history. If a supplier name changed, a lot was reclassified or a quantity was corrected, keep the old and new state readable enough to explain the decision. A clean final line with no history can be harder to trust than a file that openly shows what was corrected.
Before a natural rubber lot is handed over downstream, teams should be able to answer five basic questions without opening ten systems.
If those five answers are scattered, the problem is not legal theory. It is file design.
Peguim is best framed as infrastructure for organizing supplier records, lot history, quantity checkpoints and evidence status in one readable flow. That can help a mill, cooperative or buyer-facing team prepare a cleaner downstream file and reduce avoidable friction during review.
That is a narrower claim than "guaranteeing compliance," and it is the safer one. The value is not that software replaces EUDR obligations. The value is that a structured record set gives downstream actors fewer blind spots when a lot has to be explained quickly.
European Commission - Regulation on Deforestation-free products: https://environment.ec.europa.eu/topics/forests/deforestation/regulation-deforestation-free-products_en
European Commission - Implementing the EU Deforestation Regulation: https://green-forum.ec.europa.eu/deforestation-regulation-implementation_en
EUR-Lex - Regulation (EU) 2023/1115: https://eur-lex.europa.eu/eli/reg/2023/1115/oj
EUR-Lex - Regulation (EU) 2025/2650: https://eur-lex.europa.eu/eli/reg/2025/2650/oj
Keep reading
