The dates that anchor everything
forest
31 Dec 2020
Deforestation cut-off date. Land cleared after this can never comply.
event
30 Dec 2026
Obligations apply to medium and large operators.
event_upcoming
30 Jun 2027
Lighter regime begins for micro and small enterprises.
The three tests, every batch
The statement is your signature on all three.
Filing a DDS in EU TRACES means declaring, per consignment, that these tests were passed. Fail any one upstream and the statement is indefensible when a competent authority asks for the working.
forest
Deforestation-free
No deforestation on the plot after 31 Dec 2020, evidenced by geometry checked against forest-cover baselines.
gavel
Legally produced
Compliant with the origin country's laws: tenure, permits, and applicable local law.
description
Covered by a DDS
Statement filed in EU TRACES before placing. A precondition, not a follow-up.
See how your statement gets built from evidence
Book a DDS walkthroughHow the DDS is compiled
Follow one batch from the farm gate to the filed statement.
Every stage of the end-to-end chain contributes a specific piece of the statement. The right-hand panel at each stage shows exactly what it feeds into the DDS, so when the filing happens, nothing in it is unverified.
01
Confirm your scope and role
Match your products to the EUDR Annex I codes, then assign each company in your group to importing, producing, or exporting. You declare the role, the platform never guesses it. Every filing entity gets its own submitting identity, and non-EU operators can file through an authorised representative.
south_eastFeeds the DDS
Who is filing, for what activity, on every statement.
02
Bring in your commercial data
Your purchase orders, products, and suppliers are imported from your existing systems via spreadsheet upload, direct connection, or straight from SAP. No re-keying, and nothing to install. The purchase order serves as the backbone to which every piece of evidence attaches.
south_eastFeeds the DDS
Commodity, quantity and supplier, exactly as they appear in your own records.
03
Capture verified origin at the first mile
For smallholder-sourced commodities, the geolocation does not exist until someone stands on the plot and captures it. Field teams map each plot, and every gate purchase becomes a signed, timestamped record tied to that plot, submitted through the Supplier Portal on behalf of farmers who cannot self-report.
south_eastFeeds the DDS
Plot coordinates and production dates, captured once, reused for every filing.
04
Validate the geolocation before it goes anywhere near a statement
Plots over 4 hectares must be polygons, not points. Broken shapes are rejected, overlaps and duplicates are flagged, and files are checked against the 25 MB TRACES limit before submission, not after a rejection. A plot that fails goes back to the supplier; it is never buried in a filing. You also decide who can see your plot data, company-wide or statement by statement.
south_eastFeeds the DDS
Clean geometry only.
05
The evidence finds the order by itself
Geolocation files are stored once per supplier and product and automatically matched to the right purchase order line by supplier, country, and contract. When something does not match, you are told. Nothing fails silently, and no analyst manually pairs files to orders.
south_eastFeeds the DDS
The right plots, in the right order, with a record of how they matched.
06
The evidence follows the product through processing
Every processing step, blending, milling, and manufacturing, is recorded, linking what went in to what came out. So the plot evidence collected at origin travels with the product all the way to the batch you place on the market, and you can inspect that chain before you ever generate a statement.
south_eastFeeds the DDS
An unbroken line from the plot to the batch on the statement.
07
Screen every plot, resolve every failure
Every polygon is checked for forest-cover change after 31 December 2020, weighted by the Commission's country benchmark. Every plot, not a sample. Plots that fail take one of three recorded routes: gather more evidence, exclude and re-verify, or resolve with the supplier. The batch proceeds only once the finding is of negligible risk.
south_eastFeeds the DDS
A documented, negligible-risk finding per batch. This is the gate to filing.
The mandatory dataset
Five data points. The DDS stands on all of them.
| Data point | What it means in practice | Where Agridence compiles it |
|---|---|---|
| Geolocation | Polygon coordinates for plots above 4 hectares; a GPS point is acceptable below 4 ha. One geometry per plot of production. | Captured in AgriTrace, submitted via Supplier Portal, validated before use. |
| Production dates | Time or range of production tied to the plot, used to test against the 2020 cut-off. | Recorded at first-mile capture, carried on the plot record. |
| Commodity & quantity | HS code, description, and net mass (and volume/units where relevant). | Linked from your commercial data at the purchase order. |
| Country of production | Where grown; drives the country risk benchmark. | Set on the plot and inherited by every batch it feeds. |
| Supplier & chain | Supplier identity, plus upstream DDS references where they exist (optional, never a substitute for geolocation). | Held as one connected record, plot to shipment, by reference number. |
Geolocation is where most programmes stall: aggregated lots have to be broken back down to the individual plots that fed them, one GeoJSON file per plot.
monitoring
Filing is not the finish line. Control of the statement is.
checkEvery DDS tracked across every state TRACES can return, from missing data through to accepted
checkAmendments supported inside the 72-hour window; the record locks after
checkFindable by report name, report ID, PO number, business reference, DDS reference or lot reference
cable
If you run SAP: built on your ERP, not beside it.
checkNothing installed in your SAP, no ABAP development required
checkPurchase orders, materials, suppliers and events flow in via IDocs or the REST API
checkReference and verification numbers returned to your SAP through a webhook
checkTwo supported patterns, whether SAP holds batch genealogy or is commercial-only
DDS questions, answered
The operational detail, without a call.
When do EUDR obligations apply?
Following the December 2025 amendment (Regulation (EU) 2025/2650), obligations apply to medium and large companies from 30 December 2026, and to micro and small enterprises from 30 June 2027 under a lighter regime. Micro and small primary operators may file a one-time simplified declaration rather than running full due diligence per consignment.
Can I amend a DDS after submitting it?
Yes, within 72 hours of submission, consistent with the EU TRACES limitation. After 72 hours the statement is locked.
How many plots can go into one DDS?
Enough for virtually any consignment. The binding constraint is the 25 MB limit on the geolocation file per statement, which ConnectHub validates before submission and splits across statements when a batch exceeds it. EU TRACES also sets upper bounds, up to 10,000 production places per statement.
Whose EU TRACES credentials are used?
Yours. They are configured once, held securely, and used for each submission. Agridence does not file under its own identity. If you appoint an authorised representative under Article 6, filings can be made on your behalf through that arrangement.
I process products already placed on the EU market. Do I file a full DDS?
No. Under the December 2025 amendment, due diligence falls to the first company to place the product on the EU market. If you buy from that operator, you keep the DDS reference they pass you and share it with your own customers; there is no separate filing. Larger downstream companies must still register in the EU Information System. ConnectHub captures those references, links them to your shipments and keeps the audit record.
What if my SAP holds the commercial data but not the traceability?
You are still covered; this is one of the two supported patterns. Your SAP sends what it holds, purchase orders, materials and suppliers, and your own integration layer supplies the link back to origin, since that knowledge lives in your sourcing records rather than in SAP. Agridence cannot rebuild that chain for you, but it is the only part you own. From there, everything is handled: validated geolocation and risk are matched to your orders, the statement is generated and filed, and the reference comes back to your systems automatically. Nothing is installed in your SAP, and no ABAP development is needed; if your SAP later gains batch-level traceability, you can move to the fully automated pattern without changing the integration.
Not on SAP?
The same templates and REST API work with any ERP or middleware.
Can I rely on my supplier's DDS reference instead of geolocation?
No. Due diligence is personal to the company filing: the regulation provides no mechanism to inherit a supplier's compliance through their reference number, and every statement requires the plot geolocation itself. A supplier's reference is worth keeping, and ConnectHub stores it alongside your evidence, but it never substitutes for the plots.
This is why the chain matters. The geolocation captured at origin through AgriTrace and the Supplier Portal is validated, matched to your orders, and ready for your statement, so you are never left holding a reference number you cannot file.
This is why the chain matters. The geolocation captured at origin through AgriTrace and the Supplier Portal is validated, matched to your orders, and ready for your statement, so you are never left holding a reference number you cannot file.
Who can see my plot data?
You decide. Visibility is set once as a company-wide default and can be overridden statement by statement, including how geolocation is treated in EU TRACES. Nothing is shared beyond what you configure.
What happens if a plot is flagged as non-compliant?
Three routes: gather additional evidence that resolves the flag, exclude the non-compliant plot or supplier from the EU-bound lot, or remediate and re-verify. The decision and evidence are recorded as an auditable step, and the assessment re-runs until the batch reaches negligible risk.
How long is my due diligence record kept?
At least five years, in line with the regulation. Competent authorities can request evidence at any time; the practical test is speed of retrieval.
See one batch go from farm gate to filed statement.
Thirty minutes, your commodity, your supply chain shape. We walk the full path and file the DDS at the end of it.