This guide covers practical seed lot traceability systems for EU microgreens farms, linking seed logs, production batches, and sales records for compliance and recall readiness.
Seed lot traceability on a microgreens farm is not about creating a binder for inspectors. It is about being able to answer a difficult phone call with facts instead of guesswork.
If a chef reports an issue, if a customer questions freshness, or if your competent authority asks where a batch came from, you must move from packed punnet back to seed lot in minutes. For raw, fast-turnover crops like microgreens, that ability protects both public health and your business.
Under Regulation (EC) No 178/2002, traceability is mandatory across the EU. You must know one step back and one step forward. The regulation does not prescribe software or complexity. It requires control.
Start With the End in Mind
You must be able to:
- Identify the seed lot used for a specific harvested batch.
- Identify the production window (planting and harvest dates).
- Identify the customers supplied with that batch.
- Withdraw or recall affected product quickly.
If your system cannot answer those four questions within 10–15 minutes, it needs tightening.
The Core Structure: Three Linked Records
The simplest effective system contains:
- Seed Log
- Production Log
- Sales Log
They do not need to be complex. They do need to connect.
Layer 1: Seed Log (One Step Back)
Records what enters your farm.
Minimum fields:
- Supplier name and contact
- Seed variety
- Supplier lot number
- Date received
- Quantity received
- Storage location
Create an internal working code for each lot, for example:
- SUN-24-01
- PEA-24-03
Use this internal code throughout production.
Layer 2: Production Log
This links seed to planting and harvest.
Group trays planted from the same seed lot on the same day into a production batch.
Example Batch ID: B2024-0212-SUN
Production log fields:
- Batch ID
- Seed Code
- Variety
- Planting Date
- Number of Trays
- Harvest Date
- Staff Initials
If harvest splits across days, record separately.
Layer 3: Sales Log (One Step Forward)
This links batch to customer.
For wholesale:
- Date
- Batch ID
- Customer
- Quantity
- Invoice or delivery note
You must be able to filter by batch ID and identify all customers supplied.
Preventing Common Failures
Mixing Seed Lots
Never top up containers with new lots. Empty fully before switching.
Combining Harvests
Harvest by batch only. Use colour-coded crate tags if needed.
No Delivery Records
No delivery leaves without paperwork, even if unpaid.
Relying on Memory
Adopt a “No Pen, No Harvest” rule. If batch ID is not recorded before cutting, harvesting stops.
Paper vs Digital Systems
EU law does not require electronic systems.
Paper works if:
- Low volume
- Few clients
- Single operator
Spreadsheet recommended if:
- Regular restaurant supply
- Multiple varieties per day
- Scaling operation
Cloud-based systems allow rapid recall simulation and filtering by batch.
Recall Readiness
If food may be unsafe, you must withdraw it and inform authorities.
Simple recall plan structure:
- Trigger decision authority
- Identify batch via logs
- Isolate remaining stock
- Contact customers
- Notify competent authority
- Record actions
Run one annual recall drill. Time it. Aim for under 20 minutes.
Scaling Without Losing Control
- Use whiteboard batch overview
- Pre-print tray labels
- Standardise harvest days
- Avoid cross-batch confusion
Integrating Traceability With HACCP
Link batch records to:
- Cleaning schedules
- Water testing
- Staff shifts
- Environmental checks
This demonstrates systematic control during inspection.
What Inspectors Look For
- Identifiable seed suppliers
- Forward traceability
- Up-to-date records
- Recall procedure
They do not expect barcodes. They expect clarity.
One-Day Implementation Plan
Morning: Create seed intake log and assign codes.
Midday: Create batch ID structure and label active trays.
Afternoon: Build sales log and draft recall plan.
Evening: Test system on one real batch.
Why This Protects Your Farm
Strong traceability limits recall size, protects relationships, reduces waste, and speeds inspections.
For microgreens, eaten raw and cycled quickly, traceability is operational insurance.
References
- Regulation (EC) No 178/2002 – General Food Law
- European Commission Guidance on Food Withdrawals and Recalls
- EFSA Journal – Annual reports on foodborne outbreaks
- Riggio et al., Microgreens: Food safety considerations along the production chain
- Xavier et al., Microbial hazards and control points in sprouts and microgreens