Lot Code Traceability vs. Batch Records: Why Most Food Manufacturers Have a Gap

Ask a QA director at most food manufacturing companies whether they have batch records, and the answer is yes. Ask whether they have lot code traceability that satisfies FSMA Rule 204, and the answer often gets complicated. These two things sound similar but serve fundamentally different purposes — and the gap between them is where most manufacturers discover their compliance exposure.

This distinction matters because FDA's Food Traceability Rule does not ask for your batch records. It asks for Critical Tracking Event records with specific Key Data Elements, linked by traceability lot codes, in an electronic format that can be produced within 24 hours. Batch records — even excellent, complete, GMP-compliant batch records — are usually not that.

What a Batch Record Is

A batch record (or master batch record executed copy) is a GMP document that captures the manufacturing instructions and their execution for a single production run. It is the primary quality record in pharmaceutical and food manufacturing, and most operations with a functioning quality system have them. A complete batch record typically includes:

• Formula or bill of materials: ingredient specifications, quantities, and target weights
• Weigh-in and dispense records: actual quantities used, with operator signature and date
• Mixing, cooking, or processing instructions and actual parameters (time, temperature, RPM)
• In-process inspection checkpoints and results (pH, Brix, moisture, weight checks)
• Hold and release records
• Packaging line setup, label reconciliation, and finished goods lot code assignment
• QA sign-off and deviation notes

Batch records serve internal quality purposes: they document that the product was made to specification, that quality checks were conducted at critical steps, and that any deviations were recorded and dispositioned. They are reviewed by QA on release and retained as the historical record of production.

The problem is that batch records are designed around the production event, not the supply chain event. They tell you what happened inside the four walls of your facility. They do not tell you where each ingredient lot came from before it arrived at your dock, or where each finished goods lot went after it shipped from your warehouse.

What Lot Code Traceability Is

Lot code traceability is the ability to follow a specific lot of product or ingredient through the supply chain — forward from its origin to its destination, and backward from any point to every prior handling event. This is the core requirement of FSMA Rule 204.

Under 21 CFR Part 1, Subpart S, lot-level traceability is defined through the traceability lot code (TLC) — a unique identifier assigned to a food at initial packing (or first land-based receiving for seafood). That TLC must be carried through every Critical Tracking Event (CTE) in the chain: receiving, transformation, packing, and shipping. At each CTE, a record must capture the TLC and the required Key Data Elements (KDEs) for that event type.

The result of doing this correctly is a complete, bidirectional chain of custody for every lot. Starting from any point — a finished goods lot code, an ingredient lot, a specific shipment — you can trace forward to every destination and backward to every origin. That is what FDA needs to conduct a trace-back investigation.

Where They Overlap — and Where They Don't

The overlap between batch records and lot code traceability exists inside your facility, during the transformation CTE. Your batch record for a production run should contain:

• The ingredient lot codes used (the input TLCs for the transformation CTE)
• The finished goods lot code produced (the output TLC)
• The quantity and description of each input and output
• The location and date/time of transformation

If your batch records capture all of this, they can serve as the transformation CTE record under FSMA Rule 204 — provided they are maintained electronically in a sortable, searchable format and can be exported to FDA on request.

But the batch record does not cover what happens before raw materials enter your facility or what happens after finished goods leave it. Those are separate CTEs with their own record requirements:

• Receiving CTE: When each ingredient lot arrives at your facility, a receiving record must capture the TLC, quantity, the entity it was received from, and the reference document (purchase order or BOL). This is not part of your batch record — it precedes production.
• Shipping CTE: When finished goods lots ship out, a shipping record must capture the TLC, quantity, and the entity receiving the shipment, with the reference BOL or shipping document. This happens after production and outside the batch record.

The gap between batch records and FSMA 204 compliance, in most operations, is in these upstream and downstream CTEs. The facility's own transformation record may be adequate, but the inbound receiving records and outbound shipping records often exist in separate systems (WMS, ERP, shipping manifest) with no systematic link to the lot codes in the batch records.

The Link Problem

The most common specific failure point is what we might call the link problem: the lot codes exist — they are on the batch record, they are on the packing label, they are on the COA from the supplier — but they are not linked into a navigable chain.

Consider a typical scenario at a mid-size food manufacturer:

• Incoming ingredient lots are logged into the WMS with a receiving date and PO number. The supplier's lot code may or may not be captured. The connection between the WMS receiving record and the specific production run that consumed that ingredient is not systematic.
• The batch record captures the internal lot code the plant assigned to the ingredient upon receipt (which may differ from the supplier's TLC), the quantity used, and the finished goods lot code produced.
• The finished goods lot code is printed on the case label and entered into the ERP as a shipment. The ERP records which customer received the shipment but may not capture which specific lot codes were included in a mixed shipment.

In this scenario, every individual record exists: receiving logs, batch records, shipping orders. But the chain is broken at two points. You cannot go from the finished goods lot backward to the specific supplier lot codes because the WMS receiving records and the batch records are not linked. You cannot go from the finished goods lot forward to the specific retailer receiving records because the ERP shipment records are not at the lot level.

When FDA issues a trace-back request for a specific lot of finished goods, you need to be able to answer: which ingredient lots went into that batch? Where did each of those ingredient lots come from? Which customers received shipments containing that finished goods lot? Your batch records answer the first question, but the other two require systems that talk to each other.

The Electronic Format Requirement

Even if your records are complete, FSMA Rule 204 has a separate requirement that trips up many manufacturers: records must be maintained in an electronic format that is sortable and searchable. You must be able to provide them to FDA within 24 hours in that format.

This means that paper batch records — even binders full of them, meticulously filed by lot code and date — do not satisfy the rule on their own. Neither do PDF scans of completed batch record forms stored in a folder structure. The records must be in a format where FDA can sort by lot code, date, product, or location and search for specific entries.

Manufacturers who have digitized their batch records in a QMS (Quality Management System) are closer, but still need to verify that the system can export the trace chain in the format FDA expects — not just a dump of batch record PDFs, but a structured trace record linking input TLCs, output TLCs, and all required KDEs.

How to Close the Gap

The practical path to closing the gap between batch records and FSMA 204 lot code traceability has four components:

1. Verify supplier TLC capture at receiving

Every covered ingredient that arrives at your facility needs its supplier's traceability lot code captured in your receiving record, not just an internal receiving number or PO line. This usually requires a change to your receiving process — either scanning a barcode on the supplier's label that encodes the TLC, or manually entering the TLC from the COA into your receiving system.

2. Link receiving records to batch records

The ingredient lot codes captured at receiving need to flow into the batch record — or more precisely, the batch record needs to reference the same lot codes that were captured in the receiving records. This is the transformation CTE: input TLCs from receiving records, output TLC on the finished goods label, all in a single linked record.

3. Capture lot codes in outbound shipping records

Your shipping records — BOL, packing list, EDI 856 ASN — need to capture the finished goods TLC for each lot shipped. If your 3PL or shipping team is picking from mixed-lot inventory, the lot code for each pallet or case needs to be recorded at the time of shipment, not reconstructed later.

4. Maintain records in a queryable system

Once the records are created and linked, they need to live in a system where they can be queried. Starting from any lot code, the system should be able to return the complete upstream chain (all ingredient lots that went into it, with their origins) and the complete downstream chain (all shipments that included it, with their destinations) within seconds.

This is the operational test: enter your most recent finished goods lot code. How long does it take to produce a complete electronic trace chain — input lots, sources, output lot, all destination shipments — in a format you could hand to FDA? If the answer is more than 30 minutes, you have a gap that needs closing before the next FDA inquiry arrives.

What This Means for QA Directors

The bottom line is that batch records and FSMA 204 lot code traceability are different systems with different purposes that need to be connected. Most QA directors already understand batch record requirements well — they have been part of food GMP practice for decades. The FSMA 204 layer is an addition: upstream and downstream CTE records that wrap around the production event the batch record documents.

The good news is that if your batch records are already capturing input lot codes and the output lot code, you are not starting from zero on the transformation CTE. The work is in adding structured receiving CTEs and shipping CTEs — and building the links between these three record types so the chain is navigable.

Foodtrce is designed to do exactly this: connect your existing ERP, WMS, and batch record data into a unified trace chain, filling the gaps between systems without replacing the systems you already depend on. If you are working through this gap assessment for your facility, we are happy to walk through your specific system landscape and identify where the links need to be built.