Traceability Is Answering One Question Fast
A buyer calls: one lot of packed salad has tested positive and they need to know, within the hour, which growing zones it came from, what was applied to them, who handled them and where the rest of that lot went. Farms that can answer keep the customer. Farms that cannot lose the listing.
Traceability is not software. It is a numbering system, a set of records, and a discipline — and the software only makes it faster. This guide covers how to structure lot numbers for hydroponics, which records to keep and for how long, how to run a mock recall, and how to choose software without buying a system your team will not use.
Design the Lot Number First
Everything downstream depends on the lot being identifiable at every stage. A workable lot number encodes the information you will later need to retrieve.
| Element | Example | Purpose |
|---|---|---|
| Crop code | BTL (butterhead lettuce) | Identifies product and variety |
| Zone or house ID | H2-Z4 | Physical location of the plants |
| Transplant or seeding date | 20260412 | The anchor date everything else references |
| Batch sequence | 03 | Distinguishes multiple batches in one zone on one day |
| Full lot ID | BTL-H2Z4-20260412-03 | One string that travels from seeding to pallet |
- One lot per physical batch. Do not merge zones into one lot for convenience; you will pay for it during a recall
- Do not reuse lot numbers across seasons or years
- Carry the lot ID onto the physical product: crate label, bag code, pallet label, delivery note
- Record splits and merges. If a batch is split across two packing runs, or two batches are packed together, record the mass balance
- Keep the human-readable version. Staff must be able to write the lot on a crate by hand when the printer fails
Records to Keep, and for How Long
| Record | Content | Typical retention |
|---|---|---|
| Propagation record | Seed lot, supplier, sowing date, germination, cull counts | Crop cycle plus one year minimum |
| Transplant record | Lot ID, zone, plant numbers, operator, date | As above |
| Input records | Fertiliser batch numbers, acid and sanitiser, supplier | Commonly two years or more |
| Plant protection records | Product, rate, target, operator, date, pre-harvest interval | Commonly three years or more |
| Water and solution tests | Date, sample point, result, action taken | Two years minimum |
| Environmental logs | EC, pH, temperature, alarms, corrective actions | Crop cycle plus one year |
| Harvest records | Lot ID, zone, weight, crew, date, time | As above |
| Packing records | Pack date, packaging batch, best-before, quantity by lot | Retention usually extends past shelf life by a margin |
| Cold chain records | Cooler temperatures, dispatch temperatures, transport loggers | Retention past shelf life |
| Dispatch records | Customer, order number, lot IDs, quantities, vehicle | Two years minimum |
| Cleaning records | What, when, chemical, concentration, operator | One to two years |
| Training records | Person, topic, date, trainer | Duration of employment plus a period |
Confirm the exact retention period with your certification scheme and your buyers, because several require retention past the product’s shelf life by a defined margin, and some retailers impose their own longer periods.
The Mock Recall: Do It Before Someone Requires It
- Run it twice a year and time it. Auditors ask for the last exercise and the result
- Pick a real lot from the previous month and trace it forwards to customers and backwards to seed lot
- Reconcile mass balance: what was planted, harvested, packed, dispatched and discarded should add up
- Record the elapsed time to identify all affected customers — most standards expect this within a few hours
- Write down what failed and fix it. A mock recall that always passes is not being run honestly
- Involve the people who would actually do it, not just the manager who designed the system
Choosing Farm Management Software
| Capability | Why it matters | Question to ask |
|---|---|---|
| Lot tracking | The core function | Can I trace one lot from seed to pallet in one screen? |
| Activity recording at the point of work | Records created in the field are real records | Does it work offline on a phone or tablet in a greenhouse? |
| Sensor and controller integration | Avoids double entry | Which controllers and sensor brands does it already integrate with? |
| Harvest and pack-out | Feeds yield and quality KPIs | Can it capture rejection reasons by lot? |
| Input and chemical register | Supports certification | Does it maintain the approved product list and pre-harvest intervals? |
| Document control | Procedures and versions | Does it manage SOP versions and training sign-off? |
| Reporting and export | Audit and management use | Can I export any record set to a standard format? |
| Data ownership | Your data is an asset | Can I export everything, and what happens if I cancel? |
Be realistic about adoption. The best system is the one your crew actually uses at 6am with wet hands. Evaluate on a real shift with the actual staff before committing, and weight usability above feature count. For the hardware data layer, see our IoT and remote monitoring guide.
Levels of Implementation
| Level | Approach | Suits |
|---|---|---|
| Paper and spreadsheet | Numbered logbooks, controlled templates, weekly consolidation | Small farms, no certification requirement yet |
| Spreadsheet with discipline | Structured templates, version control, defined owner | Farms under roughly 1 ha preparing for certification |
| Entry-level farm software | Lot tracking and activity records, limited integration | Farms supplying retailers or processors |
| Full farm management platform | Lots, labour, inventory, sensors, reporting | Multi-site operations and large single sites |
| Integrated ERP | Production linked to finance, sales and purchasing | Groups with multiple businesses or sites |
Connecting Traceability to Certification
- Map every standard requirement to a record so an auditor can be shown where each one lives
- Keep the map current. Adding a record during audit preparation is visible and costly
- Make records auditable by exception: reviewers should look for missing entries and out-of-limit values, not read everything
- Link corrective actions to the record that triggered them so the loop is provable
- Use the same lot IDs in every system — controller, software, packing labels and invoices
The equipment side matters too: reliable sensors and a controller that logs consistently are what make the environmental record defensible, and our controller and automation guide covers what to specify.
FAQ
What is batch traceability in hydroponics?
The ability to follow one lot of product from retail pack back to the growing zone, the seed lot and every input applied, and forwards to every customer who received it. It rests on a consistent lot numbering system and complete records at each stage.
How should I number production lots?
Encode crop code, zone, transplant or seeding date and a batch sequence — for example BTL-H2Z4-20260412-03. Never reuse a lot number, and carry the same ID through packing and dispatch.
How fast should a traceability exercise be?
Most standards and buyers expect you to identify affected product and customers within a few hours. Run a timed mock recall twice a year, record the elapsed time, and fix whatever slowed it down.
Do I need software for traceability?
Not necessarily. A disciplined paper or spreadsheet system can satisfy certification for a small farm. Software becomes worthwhile when volume, staff count or buyer requirements make manual consolidation unreliable.
How long should hydroponic farm records be kept?
Confirm with your scheme, but commonly at least one crop cycle plus a year for production records, two years or more for input and dispatch records, and past shelf life for anything related to packed product.
What is the most common traceability failure?
Lots merged for convenience — pooling harvest from several zones into one packing run without recording the split. It makes a recall scope impossibly wide and is a frequent audit finding.
Get a Record System That Survives an Audit
Send your crop plan, buyer requirements and current record-keeping approach through the quote form. We will return a lot numbering scheme for your layout, a record list mapped to your certification standard, and a mock recall procedure you can run this quarter.