How to Handle Commodities From Multiple Plots

Aggregation requires a complete origin relationship

When a product contains relevant commodity produced on different plots, Article 9(1)(d) requires the geolocation of all those plots. Combining material into one lot does not remove the underlying production origins. The operator needs a defensible explanation of which plots contributed and how the physical flow preserves that relationship.

This is both an information problem and an operational problem. A complete plot file is useful only if intake, storage and processing records connect it to the product. A warehouse can hold goods from well-mapped farms and still create an unresolved batch if it also receives unrecorded purchases into the same stock.

Define the physical lot before mapping its sources

Identify the lot used for the assessment and how it is created: a farmer delivery, cooperative collection, storage bin, mill run or export consignment. Record how that lot changes through aggregation and splitting. A supplier's commercial invoice number may not be the same as the physical stock unit whose origins must be established.

For example, an export consignment can be assembled from several warehouse lots. Its origin set needs to reflect those contributing lots and their own source evidence. Taking the most recent supplier farm list without examining the assembly records can omit earlier purchases still present in stock or include farms unrelated to the goods.

Connect intake to known production sources

At intake, record the producer or intermediary, quantity, relevant production period and source locations associated with the delivery. Where an intermediary combines farmers' material, obtain the evidence explaining that earlier aggregation. The location of the collection centre is not the production origin merely because every delivery passed through it.

The multiple-plot recording guide describes how linked records can preserve this structure. A many-to-many relationship is often necessary: one plot can supply several lots and one lot can contain multiple plots. Keep the supporting delivery records rather than relying solely on a manually created mapping table.

Control additions from unknown origins

Suppose a coffee cooperative collects from registered farms but occasionally buys from independent agents when volumes are low. The regular members' coordinates cannot establish the origins of those additional purchases. An assertion that “most supply is mapped” does not answer the requirement for the relevant product being assessed.

The response should investigate the agent deliveries, identify their production sources and evaluate whether they can be included reliably. If the missing origins cannot be resolved, the operator cannot repair the file by adding unrelated approved plots. Keep unresolved material from being treated as covered solely because it has been blended into a larger known lot.

Follow transformations without losing the source set

Processing can combine, separate or transform material. Record the input lots, output lots, quantities and processing dates sufficiently to explain the relationship. Expected yields and losses can help identify implausible stock associations, although they do not independently prove production origins or substitute for required documents.

For a mill producing outputs from several intake batches, determine which sources can contribute to each output. The answer should follow the actual process and records. A software system that assigns the same small group of farms to every output regardless of intake does not establish traceability merely because all the identifiers resolve to valid maps.

Splitting requires controlled inheritance

When a known mixed lot is split into smaller consignments, preserve the documented origin relationship appropriate to those goods. Do not casually narrow the origin set to create a more attractive country-risk profile. A split that is only an administrative allocation may not physically separate one production origin from another.

Conversely, where the process genuinely preserves separate source streams, the records can demonstrate the narrower origins of an output. The key is evidence of the physical and documentary relationship. Operational staff should understand the difference between separate storage, stock accounting and an actual identified source stream.

Assess mixing and complexity as risk factors

Article 10 includes supply-chain complexity and the risk of mixing with unknown-origin or non-compliant products among risk criteria. Mapping all known plots does not resolve uncertainty about how the material moved between them and the final product. The operator should examine whether controls prevent unrecorded inputs and whether the records are reliable.

Where needed, mitigation can include additional source evidence, checking intake controls, investigating discrepancies or changing the sourcing arrangement. The measure should address the actual weakness. A new satellite report on already known farms does not resolve the separate question of whether unknown material was introduced at a warehouse.

Test the product-to-origin explanation

Ask a reviewer to select one output lot and reconstruct its contributing plots using the original records. Then choose a production plot and identify the products that may be affected by a concern there. These tests expose missing links that a general map dashboard can conceal.

The EUDR geolocation pillar explains the location duty, while Articles 9 to 11 establish the information and risk framework. Keep geolocation and chain-of-custody work connected. The objective is an evidenced origin relationship for the actual goods, rather than a large directory of farms whose connection to the shipment is uncertain.

A useful operational check compares the origins reported by the supplier with a recent period of intake records, including exceptional purchases. If a location appears on every export file but never in any associated receipt record, ask why. The discrepancy may have a reasonable explanation, but it should not pass merely because the map file is technically complete.