Core concepts

Orijin has about eight words in it. Learn these and the rest of the product explains itself.

Supplier

A farm. In the dashboard a farm is shown as a Supplier, because from your organisation’s point of view that’s what it is - the thing you buy from.

This trips up nearly everyone at first, so it’s worth saying plainly: when this documentation, the menu, or the AI Assistant says “Supplier”, it means a farm and the farmer who runs it. There is no separate “Farms” page to go looking for.

A supplier has a short code - a unique identifier like REN-0042 - which is how the same farm stays the same farm across seasons, spreadsheets and staff changes. Short codes matter more than names, because names are spelled four ways and shared by cousins.

Person

A human being. The farmer, their spouse, a contact person, a field officer.

A supplier has a contact person - the farmer. That person exists in their own right under Persons, so if the same farmer is connected to two farms, or changes their phone number, there’s one place that’s true.

Phone numbers live on a person’s contacts, not on the farm.

Plot

A piece of land. A supplier has one or more plots, and a plot is where crops actually grow.

A plot becomes useful once it has a boundary - a polygon walked in the field or uploaded as a file - or at minimum a GPS point. A plot with a boundary is “mapped”, and mapping coverage figures count exactly this.

Mapping is the gate for compliance. An unmapped plot cannot be checked for deforestation, which means it cannot appear properly in an EUDR report.

Collection

A purchase from a farmer. One delivery: this farmer, this weight, this price, this day.

Collections are the atoms of everything downstream. They are also called lots, and you’ll see both words - a collection is a lot, at the point in its life where it has just been bought.

Lot

A batch of product moving through your operation. A collection is the first lot. As product is bulked, dried, processed and bagged, new lots are created from old ones, and Orijin records the parentage.

That parentage is what “traceability” means in practice: any lot can be walked backwards to the collections inside it, and therefore to the farms.

Season

A buying period. Most things you look at - collections, totals, analytics - are filtered by season, because comparing this year’s volumes to last year’s is most of what anyone wants to know.

If a page looks emptier than expected, check which season it’s showing.

Facility

A physical place where product is handled. A collection point, a washing station, a warehouse, a dry mill.

Facilities are what make a supply chain a map rather than a list: this collection was bought here, moved there, processed there.

Assessment

A check performed on a plot. In practice this is usually the satellite deforestation analysis - a request goes out, results come back, and the plot carries a risk level.

An assessment is evidence, with a date. It is not a permanent property of the land, and re-running it later can give a different answer.

Certification status

A property of a supplier, not a separate certificate record. Organic, Fairtrade, in-conversion, none - it’s a field on the supplier that you set, in bulk if needed.

Orijin deliberately does not model certificates as documents with expiry dates and scans. The status is what gates decisions, so the status is what it stores.

How they relate

Person ──is contact for──▶ Supplier ──has──▶ Plot ──has──▶ Assessment
                              │                 │
                              │                 └──has──▶ boundary (polygon or GPS)
                              │
                              └──sells──▶ Collection (a Lot) ──▶ Processing ──▶ Lot ──▶ Trade
                                              │
                                              └──settled by──▶ Payment

Next

• Getting access
• Add a supplier - the first thing most people do