Each item below is a running endpoint or screen in the product today. Nothing here is
planned work.
A lot code on every harvest, with its timeline
Seeding, transplant, harvest, QA result and despatch land against a lot code as
they happen, so the trace record is a by-product of running the farm rather
than a separate binder someone has to remember to fill in.
Recall query, both directions
Give it a lot code and it answers what went into that lot and where the lot
went — the one-back and one-forward the CFIA asks for, as one query
instead of two afternoons of paperwork.
Reverse trace from a supplier’s batch
When the call comes from upstream — a supplier reporting a bad batch —
you can go the other way and list every lot that came off it, across every
flush and every zone. A batch that produced nothing says so plainly rather
than looking like a missing record.
A recall drill that times itself
Run the drill and the screen clocks it. We are deliberately not printing a
number here — your farm, your records, your time. Run it once and you will
have a figure you can put in front of a buyer and stand behind.
The rehearsal becomes a record
Who ran it, on which lot, when, how long it took — and what was missing.
The gaps the drill exposed are written down verbatim, so a drill that found
four missing record types says so permanently. That is the half an auditor
actually reads.
An audit packet you can hand over
The drill result exports as a single printable packet carrying the trace
report, the elapsed time and the recent rehearsal history — the artefact to
attach to a supplier questionnaire or put in front of a certification body.
An SFCR export for the CFIA
A date-ranged export of the trace ledger as CSV or JSON, carrying producer
name and address, seed source, harvest date, weight, zone, QA result,
customers and the retention date for each record.
Food-safety input records
Water tests, sanitation, inputs and the rest captured as CanadaGAP V9 input
records, validated so a record that looks complete but carries no evidence is
rejected instead of filed.
A scannable barcode for the lot code
Light Engine renders the lot code as a Code 128, Code 93, EAN-13 or UPC
barcode image for your own labels and internal scanning.