Back to blog
Compliance

Lot Traceability Guide for FDA-Regulated Manufacturers

March 1, 2026· Updated October 2, 2026

Regulated manufacturers do not get to treat lot history as optional. Whether you make food, dietary supplements, or cosmetics, and whether you answer to the FDA, a customer’s quality agreement, or a third-party audit, the same three questions come up sooner or later: what went into this batch, where did it go, and who touched it? If you make supplements, our page on supplement manufacturing shows how these records look in Swift WMS.

Paper travelers and disconnected spreadsheets can get you through a calm audit. They tend to fail when a supplier calls about a bad lot and the clock starts. This guide explains what lot traceability means in practice, the records people commonly ask for, and how to build a habit that holds up when it counts.

One note before we start. This is a practical guide, not legal advice. Rules differ by product type, market, and customer, and they change. Confirm your specific requirements with your quality team or your regulator.

What lot traceability actually means

A lot is a quantity of material made or received under the same conditions, so it can be treated as one unit for quality purposes. A lot number is the name you give it. Lot traceability is the ability to follow that lot through your operation: from the supplier who sent it, through every batch that used it, to every customer who received product made from it.

That sounds simple until you count the handoffs. A single ingredient lot might be split across three pallets, staged for two work orders, blended into a WIP batch, filled into several finished lots, and shipped to a dozen destinations. Each handoff is a place where the link can break.

Good traceability means each of those handoffs is recorded against the same lot identity at the moment it happens. It does not mean someone rebuilds the chain from memory after the fact.

One-up, one-down: the minimum chain

You will often hear traceability described as “one step back, one step forward,” or one-up, one-down. The idea is that each business in a supply chain should know who it got a lot from and who it sent product to. If every link in the chain can do that, the whole chain can be traced.

For a manufacturer, one step back means knowing the supplier, the lot number they assigned, and when and where you received it. One step forward means knowing which customers received which finished lots, in what quantity, and when.

Inside your own four walls, the chain is longer than one step. Your quality team needs the internal links too: which ingredient lots went into which batch, and which batch became which finished lot. Without those, you can name your suppliers and your customers but still cannot connect a bad ingredient to a specific shipment.

Records regulators and customers commonly ask for

The exact list depends on your products and your customers, but the same kinds of records come up again and again in audits, customer questionnaires, and recall investigations. In general terms, expect to be asked for:

  • Receiving records: supplier, supplier lot number, your lot number if you assign one, quantity, date received, and where the material was stored.
  • Supplier documents: certificates of analysis and specifications for the lots you received.
  • Batch records: which ingredient lots, in what quantities, went into each batch, plus who made it and when.
  • Holds and releases: which lots were held, why, who released them, and when.
  • Shipping records: which finished lots went to which customer, in what quantity, on what date.
  • Change history: who changed a record, when, and what the old value was.

Foods on FDA's Food Traceability List carry extra record rules under FSMA 204. Our page on what FSMA 204 asks for explains them in plain words.

Notice that these are ordinary operating records. The goal is not a special traceability file that someone fills in for auditors. The goal is that the records your team creates every day already answer the questions. If you want help with the supplier side, our guide to managing certificates of analysis by lot covers how to keep each COA tied to the lot it covers.

Forward trace vs backward trace

A trace runs in one of two directions, and a real investigation usually needs both.

A forward trace starts from an input and asks where it went. A supplier tells you a lot of cocoa powder may be contaminated. You need every batch that used it, every finished lot those batches became, and every customer who received those finished lots. This is the trace that drives a recall.

A backward trace starts from an output and asks what went into it. A customer reports a problem with a finished lot. You need every ingredient and packaging lot in that batch, so you can check their COAs and see whether the same inputs went into other batches. A backward trace often turns into a forward trace once you find the suspect input.

Both directions depend on the same links. If receiving, staging, production, and shipping all record the lot, both traces are just two ways of reading the same chain.

Why paper and spreadsheets break under a recall clock

Paper and spreadsheets are not wrong. Many good plants started there. The trouble is how they behave under pressure, when you need a complete answer quickly and cannot afford to miss a shipment.

  • Records live in different places. Receiving logs are in one binder, batch sheets in another, and shipping in an email folder. A trace means walking between them.
  • Lot numbers get copied by hand. One transposed digit on a batch sheet breaks the chain, and nobody notices until the trace stops cold.
  • Partial pallets disappear. When a pallet is split or partly used, the remainder is easy to lose track of on paper.
  • Nothing stops a held lot. A note on a whiteboard does not prevent someone from using the lot on the next shift.
  • Each trace depends on one person. If the person who understands the spreadsheet is on vacation, the trace waits.

None of these failures show up in a quiet week. They show up during a recall or a mock recall, which is exactly why practice matters. Our article on moving beyond spreadsheets for inventory management goes deeper on where spreadsheets stop scaling.

How to build a traceability practice

Traceability is a habit first and a tool second. These steps work whether you use paper, spreadsheets, or software.

  1. Decide what a lot is in your plant. Write down how you name lots for received materials, WIP batches, and finished goods, and make the rule easy to follow.
  2. Capture the lot at receiving. Record the supplier lot, the expiration date, and where the material went. A lot that is not captured at the dock is very hard to recover later. Our warehouse receiving best practices cover the dock routine in detail.
  3. Label everything the floor touches. Each pallet or container should carry an ID that ties back to its lot, so nobody has to guess.
  4. Record consumption at the batch. When an ingredient goes into a batch, record which lot and how much, at the time it happens.
  5. Make holds real. Decide who can put a lot on hold and who can release it, and make sure a hold actually stops the lot from being used or shipped.
  6. Link finished lots to shipments. Every shipment should list the finished lots it contained.
  7. Practice. Run a mock recall on a schedule, score it honestly, and fix what it finds.

The last step is the one most teams skip. Our step-by-step guide to running a mock recall shows how to choose a lot, run the trace in both directions, and score the result.

Where software fits

Software does not replace the habit. It removes the steps where the habit tends to break: copying lot numbers by hand, losing partial pallets, and walking between binders to rebuild a chain.

Swift WMS records the lot on the license plate at receipt and keeps it attached through every move, consume, and ship. If the license plate idea is new to you, our explainer on what a license plate number is covers the basics. Because each plate holds one SKU and lot at one location, a trace follows plates instead of paperwork.

On the Core plan, Lot Trace follows a lot forward to the plates it went into and where they shipped, with a CSV export. Each work order has a batch record with forward and backward traceability, and Batch Genealogy shows the full chain from receiving to shipment as a PDF report. Recall Impact shows downstream lots, in-flight work, and shipped destinations, can hold every impacted lot in one step, and saves a recall audit record.

Held lots in Swift WMS cannot be shipped, and with lot holds turned on in your production settings they cannot be consumed either. COAs can be attached to the lot they cover. Audit Logs keep a change history with the old and new values. These records help your team answer the questions above. They do not decide what your requirements are; your quality team and regulator do. See the lot traceability and recall impact page for the full feature list.

One caution: software keeps records, it does not make a plant compliant. Swift WMS is not certified by the FDA or any standards body. Your food safety plan, procedures, and audits are still yours to run. Swift gives them the lot history to work from.

The practical takeaway

Lot traceability comes down to three questions: what went in, where it went, and who touched it. If your daily records already answer them, an audit or a recall becomes a search instead of a scramble.

  • Capture the lot at receiving and keep it on every container.
  • Record consumption and shipments against the lot when they happen, not later.
  • Make holds stop product, not just flag it.
  • Run a mock recall and fix what it shows.
  • Confirm your specific requirements with your quality team or regulator.
How Swift WMS does itLot traceability and recall impact