Four modules covering the full Article 4 due-diligence cycle — plot verification, DDS generation, audit retention and supplier registry. No bolt-ons, no third-party stitching. One workflow, one login, one bill.
The supplier submits GPS coordinates of the harvesting plot. The platform requests Sentinel-2 imagery for the EUDR baseline (31 December 2020) and the present, runs multispectral analysis, cross-references Hansen Global Forest Change, and returns a verdict in five minutes.
From the verified data, the platform produces a Due Diligence Statement that satisfies the requirements of Articles 4 and 16.1 of Regulation (EU) 2023/1115. The file exports as XML for upload — and PDF for the customer’s archive.
Article 12 of the Regulation requires DDS and supporting materials to be retained for five years. WoodComply implements this with secure cloud storage, cryptographic timestamps and a single-screen dashboard — so a regulator audit takes thirty seconds, not thirty days.
Compliance is not a one-off task. WoodComply re-checks every plot at scheduled intervals, scores supplier risk against a transparent rubric, and pushes alerts the moment a status changes. The operator keeps full visibility of the chain — without spreadsheets.
No proprietary data sources, no closed satellite contracts. WoodComply runs on European public infrastructure — the same data the regulator uses.
Multispectral satellite imagery at 10-metre resolution, refreshed every five days, free API access. The flagship Earth-observation programme of the European Space Agency.
The DDS file produced by WoodComply matches the EUDR Information System format. The customer uploads it through their own TRACES NT account — we never submit on their behalf.
Independent peer-reviewed reference dataset from the University of Maryland, used in IPCC and FAO reports — a second source that strengthens the evidential weight of every verdict.
Four design principles drive the architecture — each one is a direct response to the rate at which EUDR rules and the TRACES NT specification still evolve.
The platform is split into functional components with clear contracts. Modules can be replaced without rebuilding the system — critical when the EUDR Information System schema shifts.
All components run in cloud infrastructure (AWS or Azure). The platform serves twenty customers and three hundred and forty-four customers from the same horizontal architecture.
An abstraction layer sits between the platform core and external APIs (Copernicus, TRACES NT, Hansen). Business logic stays isolated from changes in external contracts.
Every plot verification is recorded in the platform’s own database. Twelve months of verifications across the customer base form a competitive barrier no new entrant can match without time.
Target performance is set by the operator’s user journey: nobody waits more than five minutes for a standard shipment. Most of that time is the satellite call — and a repeat verification of the same plot completes in under a minute.
| Stage | Expected time | Optimisation |
|---|---|---|
| Coordinate validation | < 1 second | Synchronous processing |
| CDSE image request | 30 to 120 seconds | Caching of frequent requests |
| Raster preprocessing | 10 to 30 seconds | Operation vectorisation |
| Vegetation index calculation | 5 to 15 seconds | numpy, parallelisation |
| Hansen integration | 5 to 20 seconds | Pre-loaded tiles |
| Result classification | < 1 second | Rules + ML |
| DDS generation | 10 to 30 seconds | Template cache |
| Total per shipment | 1 to 5 minutes | Most time spent on CDSE |
The free EUDR audit runs on your real suppliers and returns a personalised PDF report. After that, a thirty-minute platform demo — same data, same operator, end-to-end.