Traceability · lots, history and the public QR page
Traceability means being able to tell the story of a grain lot: which field it came from, which inputs were applied, when it was harvested, when it was received and where it went. This page covers how to create the lot, how to build up the event history and how to use the QR token, which opens a public page with the lot's origin and nothing commercial.
What a lot is here
The lot is the unit of traceability: a volume of grain identified by a code of your own, with a commodity, a volume, a unit and a harvest date. It can point to a grower, a field of origin and a season. When it is created pointing at a field, the system already records that origin as the first event in the history, and that origin is never rewritten later.
Creating the lot
- Open the Agribusiness menu and go to the Traceability tab.
- Pick the grower. Their list of lots appears.
- Fill in the Lot code, the commodity, the volume, the unit and the harvest date.
- Add a note if you want one.
- Click New lot. The lot starts with the status open and already has a QR token of its own.
- Click the lot in the list to open its detail.
The event history
In the lot detail you add events. Each event has a type, a product name, a reference and a date. The available types are field origin, input applied, harvest, receiving, transport and a free type for whatever does not fit. The history is cumulative: events are appended, not edited over.
The detail also shows a calculated summary: total events, whether the origin is recorded, the date of the first and the last event, and the list of distinct inputs applied. That answers at a glance the most common question, which is whether that lot has a complete chain or a gap in it.
The interval between application and harvest
The minimum interval between the last application of an input and the harvest is what a prescription calls the pre-harvest interval, and it comes from the label of the product recorded on the Prescriptions tab. When the application date, the harvest date and the label interval all exist, the system compares the days and says whether the harvest respected the interval. If any of the three is missing, the answer is undetermined, never compliant. The system does not assert compliance without a basis.
The lot's status
- Open: the lot is being built and still takes events.
- Shipped: the lot has left.
- Closed: the lot is finished.
The QR token and the public page
Every lot is created with a traceability code of its own, shown in the lot detail as QR token. That code is the key to a public page anyone can open without signing in, and it is meant to be printed as a QR code on the packaging, the invoice or the scale ticket. The address is the tracking page followed by the code.
The public page is deliberately limited. It shows the lot code, the commodity, the harvest date, the status, the summary and the timeline of events, in ten languages according to the visitor's language. It shows no price, no market quote, no credit, no amount, no grower name and no commercial data at all, because the service behind it simply does not return those fields.
Where else the lot shows up
- In the grower portal: an authorized grower sees their own lots and the traceability code of each one.
- A malformed or nonexistent code returns the lot not found page, without revealing whether the code exists in another organization.
- Deleting a lot also deletes its history, and the QR token stops resolving. A QR code already printed will lead to the not found page.
Permissions
Creating a lot, adding an event and changing the status all require access to the Agribusiness module with write permission. Internal reading respects isolation by organization: you only see your own lots. The public page is the one deliberate exception, and it is opened by the code, not by a session.