Skip to main content
SKYGN
Guides

Traceability

Lot traceability software for food manufacturers: what it must do

Published · 5 min read

The short answer

Lot traceability software records which lots of each ingredient went into which lots of finished product, and which customers received them. The test of a system is simple: given one lot number, can you list every source lot and every customer shipment it touched, in minutes, without stitching spreadsheets together?

What lot traceability actually means

A lot (or batch) is a quantity of product made or received under the same conditions, identified by a lot number. Lot traceability is the ability to follow that lot through your business: from the supplier that shipped it, through every production run that consumed it, to every customer order that shipped it out the door.

Food safety people describe this as "one step back, one step forward": you should know who you bought from and who you sold to. A manufacturer has to add the middle step too, because the lot you ship is rarely the lot you received. Flour lot F-1182 becomes part of three batches of crackers, each with its own finished-goods lot, each shipped to different distributors. That internal transformation is where spreadsheets break down.

The three events a system must capture

Every trace is built from three kinds of transactions. If any one of them is recorded without a lot number, the chain has a gap.

  1. Receiving: the item, the supplier, the supplier's lot (or the lot you assign), the quantity, the date, and ideally the expiry date.
  2. Production: which input lots were issued to which work order or batch, in what quantities, and which output lot that batch produced. This parent-child link is called lot genealogy.
  3. Shipping: which finished-goods lots left on which shipment, to which customer, in what quantity, on what date, with which tracking number.

Adjustments, transfers between warehouses, and returns matter too, but those three are the spine. A trace is just a walk across them: backward from a finished lot to its sources, or forward from an ingredient lot to its customers.

Forward and backward traces

A backward trace starts from a finished-goods lot and answers "what went into this?" You use it for root cause: a customer complaint about a batch of salsa leads you back to the specific lot of peppers and the supplier who sold it.

A forward trace starts from any lot, often an ingredient a supplier has recalled, and answers "where did this go?" You use it to scope a recall: which finished lots contain the affected ingredient, which of those have shipped, and to whom. A good system follows the chain through multiple levels, because the affected ingredient may sit inside a sub-assembly (a spice blend or a sauce base) that was itself an input to the finished product.

The practical benchmark: a trace should take minutes and produce a list you can act on (customers, quantities, dates), not a pile of documents someone has to reconcile over a weekend.

Why spreadsheets and basic inventory apps fall short

Most growing brands start with lot numbers written on batch sheets and a spreadsheet of what shipped. That works until it is tested. The common failure points are predictable:

  • Lots are recorded at receiving but not at production, so the link between ingredient and finished lot lives on paper.
  • Production consumes "some of" several lots, and nobody records the split.
  • Shipments are recorded by SKU, not by lot, so a forward trace stops at the warehouse door.
  • The data lives in three places (a 3PL portal, a production log, and an accounting system) that never tie out.

Basic inventory apps often track lots on receipt and sale but treat production as a simple stock movement, which loses genealogy. When you evaluate software, ask specifically how it records lot consumption inside a work order.

What to look for in lot traceability software

  • Lots are part of the inventory ledger, not a separate log. Every receipt, issue, transfer, and shipment line should carry a lot, so the trace reads the same data your on-hand quantities come from.
  • Genealogy is captured automatically when production is completed, including multiple input lots per component.
  • Multi-level traces that follow ingredients through sub-assemblies to the finished product.
  • Expiry dates on lots, with first-expiry-first-out (FEFO) picking so the oldest product ships first.
  • Lot status controls (released, quarantined, rejected) that actually stop a held lot from being picked and shipped.
  • Exports. Regulators, auditors, and customers will want the result as a spreadsheet.
  • Mobile scanning at receiving and picking, because lot numbers typed by hand are the most common source of broken traces.

How Skygn handles lot traceability

Skygn is a food and beverage ERP, so lot tracking sits in the core inventory model rather than in an add-on. Concretely, as it ships today:

  • Purchase receipts create or reference lots, with expiry dates, against the supplier on the purchase order. Receiving can be done by scanning on a phone.
  • When a work order is completed, Skygn creates the finished-goods lot and records a genealogy link from every input lot that was issued to it, with quantities. If two lots of the same ingredient were used, both are recorded.
  • Shipments record the lot on each line, and pick lists are allocated first-expiry-first-out from lots whose status allows shipping, so quarantined or rejected lots are skipped.
  • The recall screen takes a lot (ingredient or finished good) and lists every posted customer shipment it reached, including shipments of finished goods built from it, with customer, quantity, date, order, and tracking number. The same screen shows the backward trace to source lots and suppliers, and the result exports to CSV.

Because the trace reads the same transactions that drive on-hand inventory and the general ledger, there is no separate traceability database to keep in sync. You can read more about how we think about this in lot traceability is the backbone, not a feature, or see the full module list on the features page.

What software cannot do for you

Software makes a trace fast; it cannot make it right. The data is only as good as the habits on the floor. Three things are worth getting in place no matter what system you use:

  • A lot-numbering convention for your own production lots that people can read on a label.
  • A rule that nothing is issued to production or shipped without a lot scan.
  • A regular mock recall, so you find gaps in a drill rather than in a real event.

If you sell foods on the FDA's Food Traceability List, you also have specific recordkeeping obligations under FSMA section 204. Our guide to FSMA 204 and recall readiness covers what the rule asks for and where an ERP helps.

Getting started

If you are on spreadsheets today, start by putting lots on receipts and shipments, then add production genealogy. Skygn is one plan at a flat per-user price with every module included; see pricing for details, or start a free trial and run a trace against your own items.

Frequently asked questions

What is the difference between lot tracking and lot traceability?
Lot tracking means recording lot numbers on stock so you know what lots you hold. Lot traceability adds the links between events, especially which input lots were consumed into which output lots, so you can follow a lot backward to its sources and forward to customers.
Do I need lot traceability if I use a co-packer?
Yes. You remain responsible for knowing which ingredient lots went into your product and where it shipped. Ask your co-packer for lot-level production records and record their finished lots on receipt so your own forward trace to customers is complete.
How fast should a trace be?
Fast enough to act on the same day. Many food safety programs aim to complete a trace within a few hours, and FDA's Food Traceability Rule asks covered firms to provide records within 24 hours of a request. A system that keeps lots in the transaction ledger can return a trace in minutes.

See it on your own items, lots, and recipes

Skygn is the ERP for food & beverage and CPG brands. One plan with every module, and a 14-day free trial.