Mapping Your Supply Chain Before Brussels Does — SPK DDMS2000:2026 Section 10.19

Quick Read

The EU Deforestation Regulation requires organisations to demonstrate geolocation-level traceability for in-scope commodities (cattle, cocoa, coffee, palm oil, rubber, soya, wood) and their derivatives—a materially more demanding standard than supplier-level attestation, as it must verify that specific production plots were deforestation-free since the regulation's reference date. SPK DDMS2000:2026 Section 10.19 addresses this distinct obligation separately from general supplier due diligence, requiring product-level applicability determinations and commodity-level traceability with formal regulatory filing and geolocation data. Organisations that treat EUDR compliance as a variation on existing due diligence programmes typically discover operational gaps only when a filing deadline approaches.

Why This Whitepaper Exists

The EU Deforestation Regulation asks a question most supply chain due diligence programmes have never had to answer with any precision: not just who supplied a commodity, but where, specifically, it was grown. SPK DDMS2000:2026 addresses this at Section 10.19, distinct from the standard's general supplier human rights and environmental due diligence module, because the evidentiary bar EUDR sets — geolocation-level traceability and a formal regulatory filing — is a genuinely different kind of task from a supplier risk assessment, and organisations that treat it as a variation on existing supplier due diligence tend to discover the gap only once a filing is actually due.

Core due diligence and traceability obligations remain intact despite simplification, though compliance costs have been reduced through scope and process simplification.

What Is In Scope

Section 10.19.1 requires the organisation to determine whether it places, makes available, or exports products in scope of an applicable deforestation regime, and to record this determination and the applicable obligation in the Applicable Obligations Register. The regulation covers a defined list of commodities — cattle, cocoa, coffee, palm oil, rubber, soya, and wood — and products derived from them. This determination has to be made at the product level, not the organisation level: an organisation can be fully in scope for some of its product lines and entirely out of scope for others, depending on which specific commodities are actually involved, and a company-wide applicability conclusion risks either over- or under-scoping the actual obligation.

The Core Test: Deforestation-Free Since the Reference Date

Section 10.19.2 requires that, where a deforestation regime applies, the organisation maintain commodity-level traceability sufficient to demonstrate the product is deforestation-free as of the regime's reference date, legally produced under the laws of the country of production, and covered by a due diligence statement or equivalent filing, including geolocation data for the plot or plots of production where required.

This is a materially more demanding standard than the supplier-level attestation that satisfies many other due diligence regimes, and the gap between the two is worth stating precisely. A supplier's general statement that its sourcing practices are sustainable answers a question about the supplier's overall conduct. EUDR asks a different, narrower, and more specific question: whether the particular plot of land a particular shipment's commodity came from was, as a verifiable factual matter, free of deforestation after the regulation's reference date. These are not the same claim, and a due diligence file built to answer the first does not automatically answer the second.

Why this cannot be retrofitted

Traceability at the geolocation level generally cannot be reconstructed after the fact. Once a shipment has moved through a supply chain without plot-level data being captured at the point of origin, that data is usually unrecoverable — there is no equivalent of going back to check a source more carefully, the way an analyst might revisit a corporate registry. This makes EUDR traceability fundamentally a procurement and sourcing data-capture design problem, not a due diligence research problem to be solved after goods have already moved.

Filing Is Not Optional Documentation

Unlike many due diligence regimes addressed elsewhere in this standard, where the underlying obligation is to conduct and document due diligence, EUDR requires an affirmative regulatory filing — a due diligence statement submitted through the EU Information System. This changes the practical stakes of a traceability gap materially. A missing or incomplete geolocation record is not only a due diligence file weakness that might be flagged on review; it is a blocking gap in the organisation's ability to make the required filing at all. Section 10.19 of this standard reflects that distinction — traceability data is treated as a precondition for making a filing, not supplementary evidence supporting one that could otherwise proceed.

Where Deforestation and Forced Labour Risk Overlap

Section 10.19.5 requires the organisation to integrate findings from this module with the forced labour and import compliance module at Section 10.9 and the supplier human rights and environmental due diligence module at Section 10.8, where a supplier or commodity presents risk across more than one regime, rather than running duplicative, siloed assessments.

This integration requirement reflects a genuine, recurring pattern in commodity supply chains: certain palm oil, cocoa, and rubber supply chains carry both deforestation risk and forced labour risk simultaneously, often concentrated in the same growing regions and even on the same plots of land. An organisation that runs its EUDR traceability exercise and its forced labour due diligence as two entirely separate workstreams, collecting overlapping supplier and geolocation information twice through different teams, is both meaningfully less efficient and more likely to miss a finding that only becomes visible once the two pictures are combined — a plot flagged for deforestation risk and a labour-risk indicator from the same growing region are each more significant in combination than either is alone.

Conflict Minerals: A Related But Separate Discipline

Section 10.19.3 addresses a second, distinct commodity category within the same module: where a conflict minerals regime applies, the organisation must conduct supply chain due diligence to the smelter or refiner level for tin, tantalum, tungsten, and gold, consistent with the OECD Due Diligence Guidance for Responsible Supply Chains of Minerals from Conflict-Affected and High-Risk Areas, retaining evidence of smelter and refiner identification and risk assessment.

This traces to a different point of chain-of-custody control than agricultural commodity traceability. Minerals traceability generally converges at a smelter or refiner rather than a specific plot of land, because minerals from many different mine sites are typically consolidated before further processing — the smelter or refiner is the practical point at which meaningful traceability control exists. This shares the same underlying discipline as EUDR's plot-level approach — tracing a supply chain to its actual point of highest risk rather than stopping at the immediate supplier — but the specific unit of traceability differs by commodity type, and organisations should not assume the same traceability infrastructure automatically serves both commodity categories.

Staying Current: This Regime Moves

Section 10.19.4 requires the organisation to monitor regulatory scope changes — product lists, thresholds, filing systems — for applicable deforestation and conflict minerals regimes at intervals not exceeding 12 months, consistent with the Annex D review cadence, given the frequency with which these regimes have been amended and postponed. EUDR's own application date has already moved more than once since the regulation's original adoption; an organisation's compliance planning should build in periodic reconfirmation of the current effective dates and scope as a standing practice, rather than working from a single point-in-time reading of the regulation established at initial implementation.

Building Traceability in Practice

Design data capture at the point of origin, not at the point of filing

Geolocation data needs to be captured as part of the procurement transaction itself — built into supplier onboarding and purchase order workflows — rather than requested retroactively once a due diligence statement is due.

Segment product lines by commodity before assessing applicability

Because scope is determined at the product level, organisations should map their full product catalogue against the regulation's commodity list explicitly, rather than making a single company-wide applicability judgement that risks missing an in-scope product line buried within a broader, largely out-of-scope business.

Build a single integrated supplier risk view for overlapping commodities

For commodities carrying both deforestation and forced labour risk, maintain one integrated supplier and geolocation dataset feeding both modules, rather than two separate, uncoordinated data collection exercises covering the same underlying suppliers.

Common Misconceptions Worth Correcting

• “Our suppliers' general sustainability certifications satisfy EUDR.” The regulation requires plot-level geolocation traceability, which a general sustainability certification does not, by itself, provide.

• “We can assemble the geolocation data once a filing deadline approaches.” Plot-level data generally cannot be reconstructed after goods have moved through the supply chain without it having been captured at origin.

• “EUDR and forced labour due diligence are unrelated workstreams for us.” For several commodities, the same growing regions carry both risks, and siloed assessment risks missing findings only visible in combination.

• “We checked EUDR's scope once at implementation, so we're covered.” The regulation's product list, thresholds, and filing mechanics have changed before and require periodic reconfirmation.

Common Gaps Worth Checking

• Product-level scope determination has not been performed — the organisation has assessed EUDR applicability at the company level only.

• Supplier traceability data exists at the country or regional level, not the geolocation-of-plot level the regulation actually requires.

• Deforestation and forced labour due diligence for the same commodity supply chains are run as entirely separate exercises, with no integration point.

• Regulatory scope and effective-date monitoring has not been performed within the past 12 months.

• Conflict minerals traceability infrastructure is assumed to also cover agricultural commodity traceability, despite the different unit of traceability each requires.

How Speeki Sentinel Certification Assesses This

Certification against SPK DDMS2000:2026 tests whether product-level scope determination has been performed, whether traceability data actually reaches geolocation level where required, and whether the organisation's deforestation and forced labour due diligence for overlapping commodity supply chains show evidence of genuine integration rather than duplicated, siloed effort.

Speeki Sentinel is the certification product through which this assessment is delivered. Organisations may build their own commodity traceability and filing capability on a self-assessed basis, without ever seeking Speeki Sentinel certification. Speeki Sentinel certification — the independent verification of that DDMS against the standard — is available once an organisation believes its capability is ready to be independently tested.

Speeki is an accredited certification body. For current information on the specific accreditations Speeki holds and their scope, please refer to speeki.com rather than relying on this whitepaper, as accreditation status and scope are maintained centrally and can change.

Closing Note

A supplier attestation answers the question “do you say your sourcing is clean.” EUDR asks a different question: can you show, plot by plot, that it actually is. Section 10.19 exists because this is a traceability problem before it is a documentation problem, and an organisation that only starts building the traceability once a filing deadline is close will generally find the data was never captured at the point it needed to be — by which point there is no way to go back and capture it.