Lot-level traceability: from plot to shipment
Traceability is not a document you produce at the end. It is a property of how records were linked as the coffee moved — and it either exists when asked for, or it does not.
- Published
- 6 October 2026
- Reading time
- 8 min
The chain, and what links it
Coffee traceability runs along a chain of records. Each link is a relationship that has to be created at the time, because it cannot be reconstructed afterwards from paper with any reliability.
| Link | What it records |
|---|---|
| Producer | Who grew or supplied the coffee, with identification and contact |
| Plot | Where it was grown — region, area, altitude, coordinates |
| Purchase | The delivery as received: supplier, weight, price, date and quality |
| Lot | What the processing batch produced, with derived yield and grade |
| Inventory | Where the lot is held, and every quantity change against it |
| Shipment | Which consignment the lot left in |
Forward and backward tracing are different questions
Backward tracing answers where a shipment came from. It walks from a consignment back through the lots it contains, the purchases behind those lots, and the plots and producers behind those purchases.
Forward tracing answers the opposite: given a lot, which shipments contain it, and which buyers received them.
Both are asked, by different people, for different reasons. A buyer asking for origin evidence needs backward tracing. A quality problem needs forward tracing. If lots are held as linked records, both are queries. If not, both are reconstruction exercises.
Why the lot is the hinge
The lot is the point where traceability either holds or breaks. It is the first record that represents tradeable green coffee rather than incoming cherry, and everything downstream — inventory, invoices, shipments — refers to it.
Because the lot is created from a processing batch, and the batch is linked to the purchases that fed it, the lot inherits origin without anyone entering it separately. That inheritance is what makes the chain continuous rather than a series of separately maintained lists.
Deriving the lot from the batch is what makes traceability automatic. Asking an operator to also record origin on the lot is asking for the one field that will be skipped under time pressure.
Where traceability usually breaks
In practice the chain fails at predictable points:
- Origin recorded on paper at receiving and never entered against the lot
- Supplier recorded as an individual rather than against a producer and plot record
- Blending at the warehouse not reflected as a documented change to lot composition
- Plot coordinates collected in the field but not attached to anything downstream
- Stock issued to a shipment without the issue referencing the lot
Building it where the work happens
The reliability of traceability is decided at the station, not at head office. If the producer and plot are captured with the delivery, on the device the receiving clerk is already using, the link exists. If it is captured later from a notebook, some of it will be missing and none of it will be trusted.
This is why offline capability matters more for traceability than for almost anything else. Cherry receiving happens in places with unreliable connectivity, and a system that requires a connection at that moment will produce gaps.
Exporting the evidence
Traceability data is usually requested in a structured form. Plot geolocation is commonly required as GeoJSON for deforestation-free and due-diligence submissions, and quality or origin reports as PDF. The format matters less than whether the underlying links are complete enough to generate it without manual assembly.
Common questions
Traceability is the ability to reconstruct the chain of custody from evidence. Certification is an attestation by a scheme or authority. Traceability supports certification; it is not the same claim.
See it against your own operation.
Tell us how your stations, paperwork and reporting work today.