Between mid-April and the end of May, four releases went out across the Farmforce platform: two on Origin Web, one on Origin Mobile, and one on Orbit. Read together, they aren’t a list of features. They’re a coordinated step toward a platform where first-mile data doesn’t just get captured, it gets defended.
Procurement teams sourcing cocoa, coffee, rubber, and palm oil from smallholder supply chains have spent the last eighteen months wrestling with the same problem in different forms. EUDR readiness was the first version. CSRD reporting is the second. The third, less talked-about but increasingly material, is the question buyers are now asking suppliers directly: show us the procurement record and demonstrate how you’d defend it to an auditor. The four releases that shipped this spring move the platform’s center of gravity in exactly that direction.
Here’s what’s actually in them, organized by what changes in practice rather than by release number.
Procurement records that hold up to scrutiny
The Origin Web release on 17 April (108.90) shipped a coordinated set of changes to how procurement is recorded. Procurement ID and Acknowledged Status are now enforced for Company Sale. Lot Quality Check is restricted to procurement-linked lot numbers, so a lot can’t be quality-checked outside the procurement chain to which it actually belongs. A new Batch Number Procurement menu and workflow standardize the issuance and tracking of batch numbers. Warehouse Allowed Certification validation now runs on the Purchase screen, so a bag flagged with a certification the warehouse isn’t authorized to hold is caught at the point of entry, not three weeks later during reconciliation.
None of those line items would carry a press release on its own. Taken together, they move procurement records from “we recorded what happened” to “we recorded what happened with the controls in place to defend the record.” The difference matters when a buyer’s compliance team is the audience.
Two further changes reinforce the same direction. The new V2 API on Origin gives downstream systems a more structured way to consume procurement data. And the rule that blocks the import of harvest collections or bags when a farmer is Inactive or non-EUDR-compliant means non-compliant transactions can’t enter the platform in the first place, rather than being filtered out afterward.
Geospatial precision, on the map and in the file
Polygons are the artifact most likely to be audited. Two changes in the May Orbit release (0.9.34) raise the quality bar on that artifact.
First, the ‘Show neighbor fields’ view on the Edit Field map now displays External ID as an on-map label, with a hover tooltip showing Field ID and Name, Size, Mapped Size, Farmer ID, and Deforestation status linked to GFW Pro. Web parity with mobile, and faster identification of neighboring plots, particularly relevant in dense cocoa landscapes where farms abut. The view now also respects factory and group access controls for factory web users, so users only see fields belonging to their assigned factory group. A small but consequential closure of a cross-factory data exposure.
Second, mobile users can now edit existing polygons by tapping individual vertices to move or remove them, instead of redrawing the entire shape. In cocoa cooperatives where field staff have already recorded thousands of polygons, the inability to make minor corrections without a full redraw has been quietly absorbing time for years. That’s gone.
On the export side, GeoJSON files now carry an embedded watermark as metadata properties: user, timestamp, and system reference. Exported files can be traced back to their authorized source, which matters when they pass among traders, certifiers, and buyers. An optional Lot Number can be attached on export and applied uniformly to every row, so a GeoJSON file moving through the chain carries the procurement context with it. And exported files now list fields in ascending numeric order by Field ID, matching the on-screen order, which removes a manual sort step for customers using exports to print farmer documents.
The Origin releases added detailed error reporting to both Meridia and GFW Pro shape analyses (108.91), so when an analysis fails or returns ambiguous results, the team running it has something actionable to work from instead of a status code.
EUDR compliance, wired across the platform
The single most significant shift this spring is that EUDR compliance status is now a first-class attribute of a farmer record, and it follows the farmer wherever they go in the platform.
On Origin Web, Origin Mobile, and Orbit, a new EUDR Compliant Status attribute is available on Farmer across every farmer surface: add, edit, bulk update, import, export, and the Orbit-Origin API. Origin auto-defaults the status when a new field is added without an approved polygon, so the absence of a defensible polygon is reflected directly in the farmer’s compliance posture instead of sitting in a separate workflow.
On Orbit, two further attributes were added to the Field edit page: Field Legality Status and Field Legality Status Assurance Date. Customers can now record and maintain field legality information directly in Farmforce, including for fields located in protected areas, instead of carrying it in separate spreadsheets.
And on tenants where it’s configured, Polygon Quality Validation rules can now be applied at the country level, with localized strings across the supported languages. Country-level configuration matters because polygon quality expectations differ by geography in ways global rules can’t capture.
One attribute, three surfaces, one API. EUDR Compliant Status now flows through Origin Web, Origin Mobile, and Orbit, with non-compliant transactions blocked at the point of import. The compliance posture isn’t a report anymore. It’s part of the record.
Operational scale, less visible but felt every day
Three changes in the May Orbit release matter to operations, leading to running large tenants.
Bulk-updating field comments via Excel for more than ~200 fields no longer hangs the page or logs the user out without saving any data. Bulk updates now run through a deferred processing system across small, medium (200+), and large (1000+) selections, with results delivered by email notification. Bulk Assign Group operations, and other long-running bulk updates on Farmers, Fields, Persons, Cases, and Survey Responses, no longer hit session-expired errors before completing.
A new bulk import for Orbit Group assignments via Excel lets operations teams add or remove members (farmers, fields, family members, infrastructure, certifications, devices, users, staff, villages, surveys, workflow plans) and update group metadata in a single sheet. One row per ADD or REMOVE action.
And two new tenant settings give administrators direct control over user counts. Billable Users caps the total number of billable Orbit users (web and mobile combined). Mobile Users caps billable mobile users specifically. A related setting unlinks previous devices automatically when a user is linked to a new one, with a confirmation dialog covering unsynced data.
Three new interface languages also went live on Orbit: Lao, Khmer, and Burmese, across the General and Rubberway vocabularies. Field staff in Laos, Cambodia, and Myanmar now have a native-language interface where one didn’t exist before.
What this means for the next six months
Three implications worth flagging for sustainability and procurement leads working on first-mile data this year.
EUDR readiness is now a posture, not a project. Treating EUDR compliance as a finite project closing in December underestimates what auditors and downstream buyers will actually ask for in 2027 and beyond. The platform changes this spring assume the question is recurring: every farmer, every field, every transaction, all the time. If your internal process still treats EUDR as a Q4 sprint, the data won’t hold up.
Procurement records and traceability records are the same record. The market still treats these as two separate workstreams. The releases this spring bring them into the same data model: a procurement transaction can’t be acknowledged without a procurement ID, can’t be quality-checked outside its procurement chain, can’t be imported for a non-compliant farmer. The implication for procurement teams: if your trade documentation lives in one system and your sustainability documentation lives in another, you’re maintaining two versions of the truth.
Audit-grade data isn’t a future state. Watermarked exports, country-level polygon validation, blocked imports on non-compliance, enforced procurement IDs: each is small on its own. Together they describe a platform where the data is structured to be defended, not just produced. Buyers are starting to ask for this. Some are starting to require it.
More is shipping in Q3. The platform’s direction is clear: every record defensible, every polygon auditable, every farmer status flowing through the chain. The question for procurement and sustainability leads isn’t whether the data layer is ready. It’s whether the workflow around it is.
