Platform
What an obligation asks the record for
A standard is a demand for particular records, in a particular form, by a date. This maps the demands we are asked about most onto the nine steps that already produce them — and then says, separately and more narrowly, how much of it we have actually built and for which product.
01
An obligation is a records demand with a date on it
Read as a feature list, a standard is unanswerable — it appears to require a system per standard. Read as a records demand, most of it is already a by-product of running the scheme: the facts an auditor or a competent authority asks for are produced by steps the operation performs anyway, provided each was captured once, at the step that produced it, rather than assembled afterwards from systems that were never designed to be compared.
The mapping below runs in one direction only. It says which step produces the fact an obligation asks for. It does not say that we file that obligation on your behalf, or that holding the fact is the same as satisfying the requirement — the section after it is the honest account of the difference.
| What the obligation asks for | The step that already produces it |
|---|---|
| Geolocation of every plot where the commodity was produced, with the date or time range of production — EUDR Art. 9 | Plan and plant — the block and season a later record can point at |
| The quantity, as net mass — EUDR Art. 9 | Harvest and grade — lots, with the block they came from |
| The name and address of whoever supplied you, and of whoever you supplied — EUDR Art. 9 | Register, then Pack and consign — custody, unbroken across the handover |
| Adequately conclusive evidence that the commodity was produced in accordance with the law of the country of production — EUDR Art. 9 | Apply — who chose the product and the dose, and the interval that follows |
| A due diligence statement, lodged before the goods are placed on the EU market | Evidence — a pack whose every figure names the record it came from |
| The practice records behind a GLOBALG.A.P. IFA audit | Apply, and Harvest and grade |
| That an advance reached the producer and was recovered on stated terms | Advance, Net and Settle |
02
How much of that is actually built, and for which product
The table above is a mapping. This is coverage, and it is deliberately narrower, because the two are the easiest things in this market to conflate — and conflating them is how a vendor comes to sell against a standard it has written no code for.
Two distinctions carry most of the difference. The first is which product: the deforestation work is built on the livestock side, where the subject of a statement is an animal or a batch, and there is no crop equivalent today. The second is filing: producing a pack and lodging it with an authority are separate obligations, and we do only the first.
- A grazing polygon held as geometry, per site, on the serverDone — Livestock. Stored in the projection the regulation is read in, with area computed from the boundary rather than typed in beside it
- A due diligence statement that freezes the boundary it was made againstDone — Livestock. The statement carries a hash binding that boundary to its subject and period, so a later edit cannot be presented as the original
- The same, for cropNot yet — Not built. The statement's subject today is an animal or a batch — there is no crop due diligence statement to show you
- Lodging a filing with TRACES, or with the GLOBALG.A.P. databasePartial — The seam exists and a submission is recorded as queued. Without provisioned gateway credentials it stays queued and is never marked accepted on our own say-so
- A SIZA exportNot yet — Nothing is built. SIZA appears on this site as industry context, and context is not a capability
- Lot custody and the audit pack, end to endPartial — The lot register has no server loader, so it is one device's view. Stated the same way on who the platform serves
- Issuing a certificate, or a determination that an audit is metRefused — Certificates come from accredited bodies. A system of record that certifies its own output is worth nothing to the party relying on it
03
A pack whose every figure names the record it came from
This is what assembling evidence from the operating record buys, and it is the only part of the argument that a reviewer can test directly. Each figure keeps its provenance: a tonnage is the weighbridge entry that produced it, a product and dose is the application record and the person who chose it, a block is the boundary as it stood in that season rather than as it stands today.
Where the record cannot answer, the pack says so and names what is missing. That is the same rule as everywhere else here — a figure that was declared stays labelled as declared, and a blank is never left to read as a zero.
Sources
- The EU Deforestation Regulation applies to operators that are large or medium enterprises, and to downstream operators and traders of every size, from 30 December 2026 — and from 30 June 2027 for natural persons and micro-enterprises. European Commission — Access2Markets, on Regulation (EU) 2025/2650 · verified 2026-08-15
- Article 9 requires an operator to collect the geolocation of all plots of land where the commodity was produced, with the date or time range of production, alongside the quantity, the country of production, and the name and address of both the supplier and the party supplied. European Commission — EUDR implementation, “Understand due diligence” · verified 2026-08-15
- A GLOBALG.A.P. add-on lets a producer combine the SIZA Environmental and IFA audits rather than running them separately. GLOBALG.A.P. — Sustainability Initiative of South Africa · verified 2026-08-13
- SIZA recorded 147 environmental audits in Q2 of its 2025/26 year, 83 more than the same quarter a year earlier. SIZA — Monitoring & Evaluation report, Q2 2025/26 · verified 2026-08-13