EUDR Plot-to-Shipment Traceability: Common Data Errors and How to Resolve Them

Reviewed 18 October 2026. Technical traceability QA checks whether records support a relationship; it does not establish the legal compliance or deforestation-free status of the commodity.

Begin with an explicit chain of identifiers

A workable evidence pack connects the source plot, producer or supplier, aggregation lot and shipment using documented identifiers. Depending on the buyer, the consignment may be defined by a Bill of Lading or a contract within it. Preserve the buyer's definition before joining files. Harvest dates and quantities also need compatible units and periods.

Errors that a successful spreadsheet join can hide

• Duplicate plot IDs can cause one geometry to be attached to two unrelated suppliers.
• Blank supplier records can turn a plot into an orphan even if its geometry is valid.
• Reused lot numbers across seasons can create a false match to the wrong harvest.
• Different contract and Bill of Lading granularities can create ambiguous many-to-many joins.
• Quantity, area and date mismatches can signal incompatible source boundaries.
• A row appearing in two files does not prove that the plot supplied that shipment.

Resolve only what original records support

Ask the authorised source owner to confirm ambiguous IDs against original supplier, production and consignment records. Keep a crosswalk with original IDs, approved standardised IDs, source references, correction rationale and reviewer status. Version the working copy and preserve the submitted baseline. Do not invent provenance to fill a blank cell or silently assign an unmatched plot to a nearby farm.

Some buyers describe alternative traceability approaches. EFICO's policy discusses full chain of custody and declaration in excess at organisational level. The allowed scope and supporting evidence must be agreed with the buyer and responsible operator; these are not interchangeable shortcuts or proof of compliance.

What a useful technical handover contains

Deliver the source manifest, crosswalk, geometry-validation results, issue register, supported corrections and residual exception log together. Explain which joins are supported, which are unresolved and which require a source-owner response. An independent technical reviewer should retest blocking errors before handover. Buyer acceptance, legal due diligence and any required declaration remain with the responsible parties.

Soilo's Professional monthly allowance covers one Express Shipment Pack of up to 100 existing plot records after accepted intake. Larger or complex supplier rescues need an accepted cap and reviewer capacity. Separately quoted jobs are distinct from monthly entitlements; work already included is not charged again as a one-off fee.