Food traceability plan: template and a practical example

If they ask you tomorrow to reconstruct a lot: can you say which IBCs it left in, which customer, and which units are still out?

That is the traceability plan. Not the PDF for the audit. The procedure that decides whether an alert withdraws three lots or a whole month of production.

It fits in a few pages if you cut it clean. Here is the structure, section by section, and a plant example with returnable containers. The full frame — Reg. 178/2002, HACCP, RD 1055/2022 and Envalora — is in the food traceability and Envalora declaration guide.

What it is, in the plant

How you identify, record and can reconstruct the path: what comes in, what happens inside, what leaves and where it goes. It is a HACCP prerequisite. In Spain the reference is the AESAN traceability guide.

The law does not impose a format. It imposes an outcome: immediate supplier and immediate customer of any lot, without delay. If you audit to BRC, the full exercise in under 4 hours.

Template: the 8 sections

One by one. No need to invent another structure.

1. Purpose and scope

Which products, lines and sites it covers. Include — and almost everyone leaves this out — the returnable containers and handling units: pallets, crates, IBCs, bins. They are part of the chain. And since RD 1055/2022 they also go into the annual declaration.

2. Responsibilities

Who maintains the plan, who records on each shift, who leads a recall. Name, role, deputy.

3. Identification and lot coding

Your lot rule: how the code is built (line + Julian date + shift), where it is marked, on which support (label, GS1-128, QR on the returnable container). If two units could have had different histories, they must be distinguishable.

4. Upstream traceability (suppliers)

At each goods-in: supplier, delivery note, product, supplier lot, quantity, date, condition on arrival. Link the approved-supplier list.

5. Internal traceability (process)

How you link what comes in to what goes out: production sheets, mixes, splits. Where it is written: line sheet, ERP, whatever you use. This is the link that breaks most often when the record is on paper.

6. Downstream traceability (customers)

At each dispatch: customer, order, lots, quantity, date, carrier and on which handling units — number of pallets, IBCs with their identity. Without that last data point you do not recover the container. You also cannot prove rotations.

7. Mock recall and verification

At least annual; quarterly if you audit to BRC/IFS. Pick a lot at random and reconstruct the chain both ways. Target time, results, deviations.

8. Withdrawal procedure (recall)

Who decides, who is notified (authorities, customers), how stock is held, where it is recorded. Art. 19 of Reg. 178/2002: if the product is not safe, withdrawal is immediate.

Annexes: traceability matrix (inbound ↔ lots ↔ customers), approved suppliers, goods-in and dispatch templates, inventory of returnable containers with identity.

Example: a sauce plant with returnable IBCs

A plant fills sauce into 1,000 L IBCs. They go to three industrial customers and come back for wash and refill.

Lot: S-[line][date][shift] → S-2-250714-M. Each IBC has its own identity (QR): IBC-0347.

In: tomato concentrate, supplier, lot TC-8812, date. Inside: the line sheet links TC-8812 → S-2-250714-M. Out: the lot leaves in IBC-0347, IBC-0512 and IBC-0533 to customer A, 15/07.

Mock-recall day. The supplier flags a problem on TC-8812. The matrix, in minutes: 1 lot, 3 IBCs, 1 customer. Call, hold, withdraw that. Without the handling-unit record the conversation is “check every IBC we have sent you this month”.

The same record shows IBC-0533 has sat at customer A for 47 days, no movement. At year-end, how many real rotations each IBC did. That is exactly what the reusable-packaging declaration under RD 1055/2022 asks for: stock, rotations, replacements, service life.

One record. Three holes: the recall, the IBC that does not come back, and the declaration.

From paper to the plant

The plan does not fail in the drafting. It fails in the doing: the shift that does not write, the dispatch without the IBC, the spreadsheet that is no longer the plant. Paper → digital, one checkpoint then the next.

• QR on every returnable container. The operator scans with the phone already in their hand. Who, where, when. Not another app: the phone.
• In and out on site (BLE). You want to know when it entered and when it left. That, first. What happens inside, if it is not validated, wait.
• One searchable history. Goods-in, dispatch, custody. Ready for the mock recall, the audit or the declaration. Base, validate, then build on top.

That is how we set up traceability in food plants: the plan no longer depends on each shift remembering.

See your savings

If at section 6 you thought “we do not record which units each lot leaves on”, there are two holes. One in compliance. One in cash. In returnable circuits it is common to lose 5–10% of containers a year. In plants on renting, until you take the unit off the contract you keep paying — even if it is lost. Residual on a container of this type is around €1,900. If payback does not fit in 2–3 years, they do not buy. Plant examples, not a generic ROI.

See your savings → Real rotation and which data you are missing for the recall and the declaration. A first estimate, in 2 minutes, with the Vitum Agent.