EUDR Traceability
Chain origin, harvest date, and permit attributes required by EUDR through ZK attestations across the supply chain — no raw production records shared.
Who this is for.
You move EUDR-covered commodities into the EU — directly, or as the trader between producer and importer. The 2026 due-diligence deadline is here, your suppliers don't all speak the same language about what "geolocation evidence" means, and you're holding onto liability for chains you don't fully see.
-
Procurement and trade-compliance leads at EU-bound exporters of coffee, cocoa, palm oil, soy, rubber, beef, or timber
-
Cooperatives and traders aggregating producer-side data across smallholder networks
-
Importers carrying EUDR due-diligence liability on shipments composed of upstream they don't directly contract with
Hand over the source, or just the facts?
supplier raw records and transaction data
meets EUDR origin, harvest-date and permit attributes
Each tier of the chain — the producer (or the cooperative aggregating producers), the trader, the importer — issues an attestation against the EUDR-specific attributes: country of origin, geolocation polygon, harvest date, permit status, deforestation-free indicator measured against the regulation's reference date.
The attributes are signed against each holder's source data — the producer's plot data, the cooperative's aggregated records, the trader's chain-of-custody — and the proof reveals only the attribute, never the source. The importer's final due-diligence statement is a single composed ZK proof, not a folder of supplier-side spreadsheets.
For multi-smallholder chains, the cooperative pattern handles aggregation without forcing each producer to expose their plot data downstream. A producer can withdraw or update an attestation without rebuilding the chain.
Choose on three criteria.
Only work that needs all three at once — pass without exposing, independent verification, tamper-proof — is Lemma's domain.
| Method | Pass without exposing | Independent verification | Tamper-proof |
|---|---|---|---|
| Access control only | △ | ✗ | ✗ |
| Masking / anonymization | △ | ✗ | ✗ |
| Encryption only | ✓ | ✗ | ✗ |
| Lemma (ZK proof)the only one with all 3 | ✓ | ✓ | ✓ |
What's next
We enter through rollout support and a PoC, and stay alongside you through to operations.
- A 30-minute review — identify the commodity, producer tier, and stalled disclosure conversation where EUDR due diligence concentrates risk.
- Narrow to 1–2 decisions (results) to prove — e.g. "country of origin X," "harvest after the EUDR reference date" — the attributes passed into the filing. Not the source records (plot data).
- Design connection and aggregation pattern — connection to your trade-management / chain-of-custody systems, and the cooperative-level aggregation and reference attestation flow.
- Prove one path via a (quote-based) PoC — confirm chained verification works for one commodity along one import path.
- Hands-on support from rollout through operations — existing plan tiers (Civic / Critical / Compliance) serve only as a cost reference; the setup and pricing are designed together.
Tell us one path where EUDR due diligence concentrates risk, in the first 30 minutes. No producer-side data or methodology required.
The bigger picture
The bigger picture this use case belongs to.
We map use scenarios across industries and workflows by the four axes.
See use scenarios for Regulatory Attribute in Solutions →TRY LEMMA
Run it yourself.
No sales call needed — start hands-on with Lemma's products.