One data structure for many parties in one chain
Cooperatives, enterprise value chains, producer groups — every organization type manages itself differently, but the data behind hundreds of Farms still needs to come together in one place to be seen, governed and proven.
This page describes the data architecture EdenHub is building for the Organization / Value Chain problem. The core data model already exists in the system; the interface to create an Organization or a Value Chain yourself is on the development roadmap and not yet open to users.
Flexible organization types
Cooperatives, enterprise value chains, producer groups — whatever the model, all of them are an "Organization" on the same data structure, instead of a separate system built for each type.
A Farm can join more than one chain
A farming household can be a member of one cooperative while also taking part in another enterprise's value chain — the same Farm, two independent relationships, instead of two duplicate production profiles.
Roles attached to each relationship
"Member" or "linked household" is a label for a specific relationship, not a fixed tag stamped across the whole platform — each organization names its roles its own way.
A Farm is a production asset, not an organization
The Farm is where the actual growing happens; the Organization is the coordinating party. A Farm is linked into an organization — it isn't itself a type of organization.
Data access scoped to each relationship
A coordinating organization only sees the production data a Farm has agreed to share for that specific relationship — the Farm can turn sharing off at any time without affecting its other relationships.
Roll-up by value chain
Each value chain — one crop, one season, one offtake arrangement — rolls up its household count, Farm count, total area and estimated output into one picture, instead of every report being tallied by hand.
A spreadsheet can't keep up with a hundred-household growing region
Once an organization coordinates dozens or hundreds of producing households, the question is no longer "which farm grows what" but "which Farm belongs to which chain, who's accountable, and how far can the organization see into the data". Without a clear data model, the answer ends up scattered across a pile of spreadsheets.
EdenHub separates the "governing party" (Organization) from the "specific program" (Value Chain) — an organization can launch a new crop chain without rebuilding anything, and a single Farm can stand inside several chains while keeping just one production identity.
See where Organization sits in the platform architectureOrganization and Value Chain sit between Farm and Buyer
From Farmer to Market, Organization is where many Farms are grouped together, and Value Chain is where one specific program actually runs.
Three stages to unlock the Organization / Chain layer
Open up participation to every organization type
In developmentNot just cooperatives — enterprises and producer groups will be able to invite households too, with roles and data access scoped to each relationship.
Manage a specific program / chain
In developmentCreate a value chain — a crop, a season, an offtake arrangement — assign Farms to it, and see a roll-up of household count, area and output for the whole chain.
Several organizations coordinating one chain
VisionFor chains with more than one party involved — for example, a buyer coordinating with several cooperatives across the same growing region.
Coordinating a growing region with many parties?
No card required · Cancel anytime