Skip to content
Orijin Docs

How Orijin fits together

One path runs through the whole system. Almost everything in Orijin is a step on it.

Field App              Dashboard                          Out
─────────              ─────────                          ───
register farmer  ──▶   Suppliers & Persons
walk plot        ──▶   Plots ──▶ satellite check ──▶ EUDR report ──▶ buyer
run survey       ──▶   Surveys & Field Services
record purchase  ──▶   Collections ──▶ Processing ──▶ Trades ──▶ Product Story
                       Collections ──▶ Payments   ──▶ farmer paid

1. The field captures it

Section titled “1. The field captures it”

A field officer opens the Field App, selects or registers a farmer, and records what happened - a new plot boundary walked on foot, a survey answered, a delivery weighed and bought. None of this needs a connection. The phone holds it until it can sync.

Because the field is where errors are cheapest to prevent, this is also where Orijin is strictest: a farmer has one record with one short code, and a purchase is attached to that record, not to a name typed from memory.

2. The dashboard receives it

Section titled “2. The dashboard receives it”

Synced data appears in the dashboard under Supply Base (suppliers, persons, plots) and Traceability and Production (collections). The office checks it, fixes what needs fixing, and fills in what the field can’t know.

Every change is recorded. Events, under Configuration after Settings, shows the log, split into Info, Field App, Warning and Error, so a disagreement about what happened has an answer.

3. Compliance runs on top of it

Section titled “3. Compliance runs on top of it”

A plot with a mapped boundary can be sent for satellite analysis. The result is a deforestation risk level for that specific piece of land, stored against the plot.

Once your plots carry results, you can generate an EUDR due-diligence report covering a set of suppliers or an entire lot’s chain - the farms, their boundaries, the checks, and the ancestry of the lot itself. That report is the artefact your buyer’s compliance team actually wants.

This is why mapping matters more than it looks. An unmapped plot can’t be checked, and an unchecked plot weakens the report.

4. Production carries it forward

Section titled “4. Production carries it forward”

Collections don’t stay collections. They’re combined, dried, hulled, graded, bagged and eventually sold. Processing, Warehouse and Trades track that, and Orijin keeps the ancestry: a bag leaving the warehouse knows which collections it contains, and therefore which farms.

At the end of that chain, a Product Story can publish a public, shareable page about a specific lot - which is the same traceability data, pointed outward at a consumer instead of an auditor.

5. Money goes back down it

Section titled “5. Money goes back down it”

Payments are recorded against the collection they settle, so “was this farmer paid for this delivery?” is a question with one answer. Where mobile money is enabled, payment happens through the wallet system and the events are logged alongside everything else.

The shape of it

Section titled “The shape of it”

The value isn’t in any one of those steps - other tools do each of them. It’s that they share one record. The farm you registered in step 1 is the same farm in the compliance report in step 3 and the payment in step 5, without anyone re-typing it. That’s the whole idea, and everything that feels strict about Orijin is in service of it.

Next

Section titled “Next”