Food and beverage
Aquaculture and fish processing
Batches that merge at processing, and traceability you must be able to rebuild from the tray.
A fish processing plant faces traceability in its most awkward form: raw material comes in from several origins — own cages, the auction, imports — and product leaves in trays whose batch must be able to take you back to the water it came from.
Where the chain breaks
| Point | What merges | What to record |
|---|---|---|
| Harvest or landing | Several cages or several landings the same day | Which origin enters each intake, with dates |
| Processing | Different intakes in the same run | Which intakes make up each production batch |
| Packing | Production batches across different formats | Which batch goes into which format and with what date |
| Dispatch | Orders to several customers from one batch | Where each batch went |
Important
The second row decides everything else and is recorded worst, because plants work by shift rather than by batch. Without a record of which intakes made up each processing run, backward traceability stops being data and becomes an estimate based on dates — and an estimate does not answer a health alert.
The detail that usually fails an audit
Watch out
The health registration number on the label must be that of the **establishment that actually handled the product**, not of the company issuing the invoice. When processing or packing is subcontracted to another plant — common at seasonal peaks — that number changes and the label must follow. It is a failure invisible from the office and the first thing an inspector cross-checks.
What to hold per supplier and per batch
When an alert arrives
- 1
Narrow forwards first
Which customers received that batch. It decides the recall's size and is the most urgent.
- 2
And backwards afterwards
Which intakes made it up and what origin they came from.
- 3
Record the decision, not only the action
What was recalled, what was released and on what criteria, with a name and a time.
Worth knowing
It applies equally to canning, salting, smoking and chilled ready meals: the process changes, but the point where traceability is lost is always the same — where several intakes become a single run.
›What if we buy it already filleted?
Then your traceability starts at that purchase: ask your supplier for the origin batch and keep it.
›How long must records be kept?
Longer than the product's shelf life, with margin; for frozen that means years.
›Is a paper plant logbook enough?
It is if digitised the same day; at month end nobody can tell which run was which.
A real case
The situation
A plant receives an alert about a raw material consignment from three weeks earlier.
What you do
- Checks which processing runs included it and which customers got those batches
What you get
Recalls two specific batches instead of three weeks of production for lack of narrowing.
The situation
Batches merge at cutting and the trace breaks there.
What you do
- Records what went into each output batch
What you get
The backward journey survives cutting.
The situation
A client asks about one specific tray.
What you do
- Checks that tray's batch
What you get
You reach the intake.
The situation
Origin documentation arrives on paper with the box.
What you do
- Captures it on receipt
What you get
The paper stops being the only copy.
The situation
A batch must be flagged and nobody knows who received it.
What you do
- Checks what went out of that batch and where
What you get
Those affected are warned.
The situation
Supplier certificates expire without warning.
What you do
- Records validity on receipt
What you get
The warning arrives before the next purchase.
This article answers
- traceability in a fish plant
- aquaculture farming documentation
- fresh fish batch traceability
- processing plant health registration