What question does hygiene answer

Hygiene control focuses on the conditions and practices that keep food from becoming contaminated during production, processing, packaging, and storage. For coffee, that can involve raw material, contact surfaces, equipment, water, the production area, the warehouse, and handling practices.

The goal of this layer of control is to prevent or reduce risks that can arise during operation. A properly cleaned machine doesn't mean a batch of raw material has a clear origin; conversely, a batch with a well-documented origin still needs to be processed under suitable conditions.

Hygiene, then, is a story about the state and conditions of the process. It asks: is the surface clean, was the equipment properly cleaned, is the raw material protected, is the area suitable?

These questions matter a great deal, but they don't tell the product's whole history. To know which batch a bag of coffee came from, which steps it passed through, and which source it's tied to, you need a different layer of information: traceability.

Traceability answers where the product has traveled

The FAO defines traceability in a food control system as the ability to follow food through specified stages of production, processing, and distribution. Traceability, then, isn't a form of hygiene — it's a system for identification and linking information.

In the coffee chain, a batch code can link incoming raw material to the intake date, processing, roasting, packing, and distribution. The level of detail depends on the facility's scale and goals. But the general principle is that each step needs to leave behind enough information to be traced when necessary.

The value of traceability shows most clearly when something goes wrong. If a batch has an issue, the facility needs to know which products are affected, where they currently are, and which other batches share the same source or process. The FAO treats traceability and recall as important components of a food control system.

A good traceability system, then, doesn't make a product physically “cleaner.” It makes the product's history and scope of control clearer.

These two layers complement each other

A simple example shows the difference. Suppose a facility has very clear batch codes and knows exactly where a bag of coffee came from and when it was roasted. If the grinder or the packing area wasn't cleaned properly, traceability can't substitute for hygiene.

The reverse holds too. A production line with good hygiene conditions but very vague batch records will struggle when it needs to identify a product's source or narrow down an issue. Without knowing where a product came from, investigation and recall become far harder to carry out accurately.

So the two layers should be built side by side. The hygiene layer controls production conditions; the traceability layer preserves information about how the product moved. One focuses on “what conditions was the product handled under”; the other focuses on “where did this product come from and where has it been.”

This is also why sentences like “we have traceability, so we're clean” or “our facility is clean, so we must be traceable” don't hold up. Both conclusions go beyond what each system actually proves.

Where can a small facility start

Traceability doesn't have to begin with complex software. A small facility can start with a consistent batch-coding system and records linking key points: raw-material source, intake date, quantity received, roast batch, packing date, and quantity shipped.

On the hygiene side, a facility can maintain a cleaning schedule for equipment, areas, and tools, and record who performed each task and when. These two kinds of records serve different purposes, but they can be linked through the batch code or production date.

When something goes wrong, a facility faces two questions. First: was anything unusual about the production conditions at that time? Second: which products are tied to the same batch or timeframe? Hygiene and traceability records working together help answer both.

The value of a system doesn't lie in the number of forms it has. A small system that's recorded accurately, consistently, and can actually be used during an investigation is far more useful than a thick set of records that doesn't reflect real activity. From hygiene to traceability, the ultimate goal is always the same: making the control process visible and verifiable.

References

• FAO — Traceability & recalls — https://www.fao.org/food-safety/food-control-systems/traceability---recalls/en