We adapt the live EUDR platform to Rainforest Alliance, with 2–3 partners.
You shape what ships — and keep preferential terms for your entire contract duration.
Not ready?
Mandatory improvement
A six-year climb, and year one is the cheap one.
Geolocation requirements step up across audit cycles: points for everyone, then polygons for a tenth, a third, and eventually all of it. Groups that treat each step as a separate campaign pay for the same visit three times.
- Cycle 01CorePoints for everyoneGeolocation data for every farm, with a first tenth as polygons.
- By year 3ImprovementA third in polygonsYearly progress has to be shown against the target, not delivered on the last day.
- By year 6ImprovementPolygons for all farm unitsThe end state, and the point at which risk maps and yield estimates become worth having.
- Every cycleOngoingKeep it currentNew members, split plots and inherited land arrive constantly. The map carries the date it was last updated.
Thresholds and cycle lengths follow the Rainforest Alliance’s own Farm Requirements and its current version, which is what your certification body audits against.
How the standard reaches a farm
The requirements have to arrive at every farm.
Requirements and training travel down the group. Polygons, attendance and closed non-conformities come back up.
Three hundred and eighteen of 340 farms are complete. The other 22 are named, with what each one still needs before the audit.
How it works
Follow one farm through one cycle.
The same farm, the same number, from the day its boundary is walked to the day it sits in an audit pack with its evidence attached. Two products: the Field App inspectors carry, and the Dashboard the group ICS runs on.
Season 1 · Field App
The farm becomes a record, not a row.
The polygon is walked with the producer, and the farm data comes from the same visit. Everything the standard asks about this farm hangs off this one record.
Season 1 · Dashboard
The self-assessment shows the gap, farm by farm.
The requirements are mapped against what the record already holds. What is missing is a list of specific farms, not a percentage.
Season 2 · Field App
The inspection closes the two gaps it came for.
The inspector arrives knowing what is outstanding on this farm. Training attendance is taken on the spot, and the storage check is a photo, not a promise.
Season 2 · Dashboard
The audit pack is an export of the cycle.
Every farm in the group with its evidence, its inspection dates and its open items. The certification body reads a record that was built as the work happened.
The same polygons, farm records and inspection history already answer EUDR and an organic file. One deployment, one farm number, several standards.
The farm map
Keep one map, a dozen layers, dated.
The standard is specific about what the group’s map has to show, and most of it is not the crop. Every layer below is a thing somebody has to walk to, record, and keep current, with the date of the last update on the map itself.
Captured in the field appFrom imagery or registers
- Farm units and production zones
- Certified crop area
- Processing facilities
- Human habitation areas
- Schools
- Medical and first aid sites
- Agroforestry shade cover
- Water bodies
- Forests and natural vegetation
- Riparian buffer zones
- Protected areas
- Risk areas from the assessment
Internal inspection
Inspect every member, every year, before the auditor arrives.
Group certification runs on an internal inspection system: each member inspected yearly, all of them inspected before the first audit. On paper that is a filing cabinet. Here it is a queue with a state per member.
Assess and address
A risk found is a record, not a failure.
The standard’s approach to child labour, forced labour, discrimination and workplace violence is to look for it, then act and document. That only works if the looking and the acting are written down in the same place, on the same member.
- AssessAsk the questions where the work happensThe risk questions are put to members and workers in their own language, on a visit that was happening anyway.Held on the recordWho was asked, when, by whom, and what they answered.
- AddressAct, and write down what was doneRemediation is a case with steps and dates, not a note in a binder that nobody can find at audit.Held on the recordThe action taken, the person responsible, and the date it closed.
- MonitorCome back to it next cycleA risk found once is checked again, so improvement or persistence is visible rather than assumed.Held on the recordThe same member, the same question, a year apart.
Volumes and payments
Reconcile certified volume quarterly.
Volumes sold as certified go into the traceability platform shortly after each quarter closes, and buyers are expected to check them against invoices. Sustainability Differential and Investments have to be shown as paid. All of it comes out of delivery records that already exist.
- Quarter Q1 2026ReconciledCertified volume sold
- Recorded in the platform412 t
- Matched to invoices412 t
- Sold as conventional38 t
- Shared responsibilityPaidDifferential and investments
- Differential received$61,800
- Allocated to members$58,700
- Investment plan spend$3,100
The same delivery records feed the differential payout per member, so a group can show not only that the money arrived but who received it.
If you already collected data
Bring what you already have.
Member lists and boundaries assembled for Rainforest Alliance audits import in bulk — the data you already gave the certifier is your starting point here.
XLSX · 560 KB · one upload
1,214members imported
- From your audit files — the certifier packet is the starting point
- Certificates attached — documents land with the members they cover
- 0 duplicates — existing records matched, not doubled
CSV, XLSX or paste a list — templates for every format. Errors show before anything is saved.
Questions we get.
Are you a certification body?+
No. Certification bodies audit and the Rainforest Alliance owns the standard. Tracebud holds the group’s data between audits: the geolocation, the farm map layers, the internal inspections, the remediation cases and the volumes, in a form an auditor can be walked through.
Can we use this for the traceability platform?+
Volumes come out of the delivery and lot records, so preparing a quarterly submission is an export rather than a reconstruction. The submission itself is made in the Rainforest Alliance platform, by you.
We are UTZ-era and our member list is a spreadsheet.+
That is the normal starting point. The list imports, members are invited, and polygons and inspections fill in over the cycles the standard allows rather than in one impossible campaign.
Does this also cover the new regenerative standard?+
The plot-level records and practice history are the same evidence base, and we track practice adoption per plot per season. Which standard you certify against, and what it requires, stays between you and the Rainforest Alliance.
