Your food business is growing.
Instead of making 30 jars of salsa for Saturday’s farmers market, you’re now making 500 jars at a time. Some go to Grocery Store A, some to Grocery Store B, and others go to online customers.
Then a customer calls and says, “There’s something wrong with the jar I bought.”
One of your first questions should be: “What is the lot number?”
That little string of numbers or letters can identify which production batch the product came from. From there, a good traceability system can help determine when the product was manufactured, which ingredients and ingredient lots were used, who supplied those ingredients, which production records apply, which other finished products came from the same batch, and which customers received them.
That’s why lot codes become increasingly important as a small food business grows.
What Is a Food Lot Code?
A lot code—also commonly called a lot number, batch number, or production code—is an identifier used to connect a particular quantity of food with its production and traceability records.
For example:
LOT 260927A
might identify a particular batch manufactured on September 27, 2026.
Another manufacturer might use:
L269-03
or:
CHOC-260927-02
There isn’t one universal lot-code format used by every food manufacturer. The important characteristic is that the code allows you to determine which specific lot of food a package belongs to.
What Is a Lot?
A lot is generally a defined quantity of product that you treat as belonging together for production and traceability purposes.
For a very small manufacturer, one production batch might equal one lot. If you make 400 jars of salsa in one production run, all 400 jars might receive LOT 260927A. The next production run could receive LOT 260927B.
Other manufacturers may define lots differently depending on their manufacturing process.
The important thing is to establish a consistent rule for when one lot ends and another begins.
Does FDA Require Every Food Product to Have a Lot Code?
There isn’t one universal FDA rule requiring every conventional packaged food to carry the same type of consumer-visible lot code simply because it’s a food product. Specific regulations can impose coding, recordkeeping, or identification requirements on particular foods and operations.
FDA’s Food Traceability Rule also establishes additional traceability requirements for certain foods on the Food Traceability List, subject to applicable exemptions. Those requirements include a specifically defined Traceability Lot Code, or TLC, at certain points in the supply chain.
It’s therefore too simplistic to ask, “Does FDA require lot codes?” and expect one answer covering every food manufacturer.
From a practical food-manufacturing standpoint, however, lot coding is extremely useful even when a particular regulation doesn’t require your ordinary internal lot number to appear on the consumer package. Once food leaves your direct control, lot identification becomes one of your most useful tools for traceability, complaints, investigations, withdrawals, recalls, and quality control.
Why Are Food Lot Codes Important?
Consider two manufacturers.
The first manufactures 10,000 chocolate bars during September but doesn’t use meaningful production lot codes. A customer reports a possible problem. The company knows which product is involved, but it can’t readily determine which production day, batch, cocoa lot, milk-powder lot, packaging lot, or customer shipments are associated with that particular bar.
The investigation could potentially involve all 10,000 bars.
Now consider a manufacturer whose customer reports:
LOT 260915B
The manufacturer’s records show:
| Record | Information |
| Production Date | September 15 |
| Production Run | B |
| Quantity | 475 bars |
| Ingredient Lots | Identified |
| Packaging Lot | Identified |
| Customers Receiving Lot | Identified |
Now the investigation can begin with those 475 bars rather than automatically treating every bar produced during September as potentially involved.
That’s the power of lot-level traceability.
Smaller Lots Can Reduce Recall Scope
There is an important tradeoff when defining lots.
Suppose you manufacture 10,000 jars per month. You could theoretically define the entire month’s production as one lot. That’s simple, but if something goes wrong, the potentially affected quantity could be 10,000 jars.
Instead, suppose each day’s production receives a separate lot number and a typical daily lot contains 500 jars. A problem associated with one production day might initially involve 500 jars rather than the entire month’s production.
FDA makes a similar point in its Food Traceability Rule materials: smaller traceability lots may result in less food being affected when a recall is necessary.
But extremely small lots also create more codes, records, inventory complexity, warehouse tracking, and shipping complexity.
The objective is to define lots narrowly enough to provide useful traceability without creating unnecessary administrative burden.
Lot Code vs. UPC: What’s the Difference?
This is an important distinction for a growing food company.
A UPC or GTIN identifies the product. A lot code identifies a particular production lot of that product.
Suppose you sell a 12-ounce Green Chile Salsa. Every jar of that particular retail item generally carries the same UPC. Jars manufactured on different days, however, might have:
LOT 260925A
LOT 260926A
LOT 260927A
The UPC answers, “What product is this?”
The lot code answers, “Which production lot did this particular package come from?”
They serve different purposes.
Lot Code vs. SKU
A SKU is generally an internal product identifier.
For example:
SAL-GC-HOT-12
might mean:
Salsa – Green Chile – Hot – 12 oz
Thousands of jars could carry or be associated with that same SKU, while individual production lots receive different lot codes.
For example:
SKU: SAL-GC-HOT-12
Lot: 260927A
The SKU identifies the product. The lot identifies the production group.
Lot Code vs. Best-By Date
These are also different.
A lot code is primarily about production identity and traceability. A Best If Used By date generally relates to product quality and shelf life.
For example, a package might show:
BEST IF USED BY 09/27/2027
LOT 260927A
Manufacturers sometimes incorporate date information into a lot code, but conceptually the two serve different purposes.
Lot Code vs. Expiration Date
An expiration date is also different from a lot number.
Where an expiration date is used, it identifies a shelf-life endpoint under the manufacturer’s system or an applicable regulatory requirement. The lot number identifies the production lot.
A package can therefore have all three:
| Identifier | Purpose |
| UPC/GTIN | Identifies the product |
| Lot Code | Identifies the production lot |
| Best-By/Expiration Date | Communicates shelf-life information |
What Information Should a Lot Code Contain?
There is no universal format that every small food manufacturer needs to use.
A lot code could encode information such as production date, shift, production line, batch number, facility, product, or sequence number.
But don’t make the code more complicated than necessary.
A lot code doesn’t need to contain every piece of traceability information directly. It needs to reliably connect the package to records containing the information you need.
For example:
LOT A48372
might appear meaningless to a consumer. Your production system, however, could tell you that A48372 means September 27, 2026; Facility 1; Line 2; Batch 4; Green Chile Salsa; Production Record 48372.
That’s perfectly workable. The intelligence can reside in your records rather than being obvious from the printed code.
A Simple Lot Code System for a Small Manufacturer
A small food company doesn’t necessarily need an elaborate coding scheme.
A straightforward format might be:
YYMMDD-BB
For example:
260927-01
could mean September 27, 2026, first batch of the day.
The second batch would be 260927-02 and the third 260927-03.
This approach is easy for employees to understand and easy to connect to production records.
Example: Bakery Lot Codes
Suppose your bakery produces three batches of cookies on September 27, 2026:
| Production | Lot Code |
| Chocolate Chip Batch 1 | 260927-01 |
| Chocolate Chip Batch 2 | 260927-02 |
| Oatmeal Batch 1 | 260927-03 |
The production records associated with those lots can then identify the recipe, ingredient quantities, ingredient lot numbers, employees, production time, finished quantity, inspections, packaging, and customers.
The printed code itself can remain simple.
Should the Product Code Be Included in the Lot Number?
You can include product identity, but you don’t necessarily need to.
For example:
CC-260927-01
could mean Chocolate Chip Cookies – September 27, 2026 – Batch 1.
That’s convenient for humans. But suppose you eventually manufacture 200 different products. Encoding product identity into every lot-code format can become cumbersome.
If your software already associates Lot 483729 with Chocolate Chip Cookies – 8 oz, the product doesn’t necessarily need to be encoded directly into the lot number.
For very small companies, human-readable codes can be convenient. As the company grows, database-generated identifiers can be more scalable.
Should I Use a Julian Date?
Some manufacturers use Julian-style production dates in lot codes. Instead of representing September 27 as 0927, the code might use the sequential day of the year.
This can create shorter codes and is common in manufacturing environments.
But don’t choose a coding method simply because another company uses it. Ask whether the code is unique, whether employees can use it reliably, whether you can trace it back to production records, and whether you can explain the system during an audit or investigation.
A simple system employees use consistently is better than a clever system nobody understands.
Don’t Accidentally Reuse Lot Numbers
Lot numbers should uniquely identify the intended production lot within your traceability system.
Suppose you use 0927 for production on September 27. What happens next year? If you use 0927 again, you now have two different production lots with the same printed identifier.
Your database might distinguish them by year, but someone looking only at the package cannot.
Including enough information to prevent ambiguity is generally better:
260927-01
and the following year:
270927-01
What Should My Lot Records Contain?
The printed code is only the beginning. A useful lot code connects to a production record.
For a small food manufacturer, that record might contain:
- product and lot number
- production date and production times
- recipe or formula version
- quantity produced
- ingredient lots used
- packaging lots used where relevant
- employees or operators
- equipment or production line
- quality and food-safety checks
- hold/release status
- finished quantity, yield, and waste
- disposition and customer shipments
Not every company needs every field.
The objective is straightforward: given a finished-product lot code, can you reconstruct what happened?
Ingredient Lot Numbers Are Just as Important
Suppose you manufacture chocolate.
Finished chocolate:
LOT CH-260927-01
The batch contains:
Cocoa Liquor — Supplier Lot CL98241
Sugar — Supplier Lot S61392
Cocoa Butter — Supplier Lot CB44172
Now imagine your cocoa-butter supplier calls and says it is recalling Lot CB44172.
Your traceability system should allow you to search CB44172 and determine which finished-product lots used it.
You might discover:
CH-260927-01
CH-260927-02
CH-260928-01
Now you know which finished lots require investigation.
This is trace-forward capability.
Trace-Back and Trace-Forward
A good lot system needs to work in both directions.
For trace-back, start with a finished product lot and determine which ingredients went into it, which supplier lots those ingredients came from, and which suppliers provided them.
Finished Lot → Ingredient Lots → Suppliers
For trace-forward, start with an ingredient lot and determine which production batches used it, which finished-product lots resulted, and which customers received those finished lots.
Supplier Lot → Production Batches → Finished Lots → Customers
Both directions matter.
Customer Shipment Records Complete the Chain
Suppose you know Lot 260927-01 has a problem. That’s useful, but now you need to know where it went.
Your shipment records should connect finished-product lots to customers.
For example:
| Finished Lot | Destination | Quantity |
| 260927-01 | Grocery Store A | 150 units |
| 260927-01 | Grocery Store B | 100 units |
| 260927-01 | Distributor C | 75 units |
| 260927-01 | Online warehouse | 50 units |
| 260927-01 | Farmers-market inventory | 25 units |
Now you can identify where the potentially affected product was distributed.
Without shipment-level lot tracking, you may know what you manufactured but not where it went.
Why Lot Codes Matter During Recalls
FDA recall notices commonly identify affected products using combinations of information such as product name, package size, UPC, lot codes, sell-by or use-by dates, packaging images, and distribution information.
That allows retailers and consumers to distinguish affected products from unaffected products.
Imagine that a company sells the same salsa nationwide but only LOT 260927-01 is affected. A useful lot code can help the company, retailers, regulators, and consumers identify that particular production rather than automatically treating every jar of that salsa as potentially affected.
Lot Codes Can Reduce Business Risk
Lot coding isn’t simply a compliance exercise.
Suppose you manufacture 100,000 packages of a product each month and a quality or safety problem affects one production run containing 4,000 packages.
If your traceability system can reliably isolate those 4,000 packages, your investigation, withdrawal, or recall may be substantially narrower than if you can’t determine which products are affected.
Without adequate records, a much larger amount of inventory may need to be treated as potentially involved.
Traceability therefore has direct operational and financial value.
Lot Codes Help With Quality Problems Too
Not every lot investigation involves food safety.
Suppose customers report that your Chocolate Chip Cookies are unusually hard, and all of the complaints involve LOT 260921-02.
You review the batch record and discover that Oven 2 was running hotter than normal. Or perhaps an ingredient supplier lot had different moisture characteristics.
Lot codes can reveal patterns involving texture, color, flavor, weight, packaging, breakage, oxidation, separation, and shelf-life problems.
Traceability supports quality control as well as food safety.
Lot Codes Help With Customer Complaints
When a customer reports a problem, train employees to ask for the lot number printed on the package.
Also collect useful information such as the product, package size, UPC when helpful, Best-By date, purchase location, purchase date, photographs, and a description of the problem.
The lot number can immediately narrow the investigation and allow employees to review production records for the exact lot involved.
Where Should the Lot Code Be Printed?
A consumer-visible lot code should be placed somewhere it can be found and read.
Common locations include the package back or bottom, top or seal area, bottle shoulder, jar lid, label, or pouch seal.
The ideal location depends on the package and coding equipment.
One practical consideration is whether consumers will still have access to the code after opening the package. If you expect consumers to provide the lot number during a complaint, don’t routinely place the only usable code on a piece of packaging that’s immediately destroyed or discarded during opening.
Make Sure the Code Is Legible
A lot code isn’t useful if nobody can read it.
Common problems include faint ink, smeared printing, poor contrast, printing across seams, ink rubbing off, poor adhesion to the packaging material, tiny characters, distorted printing, and date-code printer misalignment.
Periodically verify coding during production.
A simple packaging check might ask:
- Is the lot code present?
- Is it the correct lot?
- Is it legible?
- Is the applicable date correct?
A quick inspection can prevent thousands of packages from being produced with unusable codes.
Don’t Rely Only on a Best-By Date as Your Lot Code
Some small manufacturers effectively use:
BEST BY 09/27/27
as their only production identifier.
That may provide adequate differentiation in a very simple operation where every production lot has a unique date. But what happens if you manufacture three batches on the same day using different ingredient lots?
All three could receive the same Best-By date.
You can no longer distinguish them from the package alone.
A separate lot identifier can provide much more precise traceability.
How Small Should a Lot Be?
There isn’t one perfect answer.
A manufacturer could define a lot as one batch, one production run, one shift, one day, production between sanitation events, production associated with particular ingredient lots, or another meaningful production grouping.
A useful question is:
What event would cause me to want to isolate this product from everything produced before or after it?
For a small batch manufacturer, one production batch is often a natural starting point. For continuous manufacturing, a time period or other defined production interval may make more sense.
When Should You Start a New Lot?
Potential reasons for starting a new lot can include a new production batch or day, a major sanitation break, formula change, ingredient-lot change, allergen changeover, production-line change, or significant process interruption.
The appropriate rules depend on your operation.
Write them down. Employees shouldn’t have to decide spontaneously whether a particular event requires a new lot.
Should an Ingredient Lot Change Create a New Finished Lot?
This is an important design decision.
Suppose halfway through production you finish Sugar Lot S100 and begin using Sugar Lot S101.
One approach is to keep one finished lot and record that it contains both S100 and S101.
Another approach is to close the first finished lot when the ingredient lot changes and begin a new finished lot.
The second approach provides more precise traceability but also creates more finished lots and additional inventory complexity.
The appropriate balance depends on risk, manufacturing process, product value, batch structure, customer requirements, and traceability objectives.
The important point is to establish a defined policy and apply it consistently.
What Is FDA’s Traceability Lot Code?
FDA’s Food Traceability Rule uses a specifically defined term: Traceability Lot Code, or TLC.
A TLC is a descriptor, often alphanumeric, used to uniquely identify a traceability lot within the records of the firm that assigned the code.
The Food Traceability Rule applies to persons who manufacture, process, pack, or hold foods on FDA’s Food Traceability List, subject to applicable exemptions. It establishes additional traceability recordkeeping requirements beyond ordinary internal lot-coding practices.
This means an ordinary internal lot number and an FDA Traceability Lot Code are related concepts, but you shouldn’t automatically assume that every number your inventory or ERP system calls a “lot number” satisfies all requirements of the Food Traceability Rule.
Current Status of the FDA Food Traceability Rule
The Food Traceability Rule remains in place, but its implementation schedule has changed.
The original compliance date was January 20, 2026. FDA later proposed extending that date by 30 months to July 20, 2028. Congress subsequently directed FDA not to enforce the Food Traceability Rule before July 20, 2028, and FDA has stated that it intends to comply with that directive.
FDA has also been engaging with industry during 2026 regarding implementation challenges and possible additional flexibilities involving lot-level tracking.
For a manufacturer potentially subject to the rule, this additional time shouldn’t be interpreted as a reason to ignore traceability. It provides additional time to determine whether the rule applies, understand the required Critical Tracking Events and Key Data Elements, evaluate existing systems, and prepare for implementation.
Because the rule and its implementation guidance continue to develop, manufacturers should check current FDA information rather than relying solely on an older article, training course, or compliance calendar.
When Is an FDA Traceability Lot Code Assigned?
Under the Food Traceability Rule, a TLC is assigned at particular Critical Tracking Events.
These include:
- initial packing of a raw agricultural commodity other than food obtained from a fishing vessel
- first land-based receiving of food obtained from a fishing vessel
- transformation
There are additional provisions for certain situations in which an FTL food is received from an exempt person without a TLC.
Once assigned, the TLC generally remains associated with the traceability lot as it moves through the supply chain. A firm shouldn’t simply create a new regulatory TLC during ordinary activities such as shipping. Transformation is one of the events at which a new TLC can be assigned.
Does the FDA Traceability Lot Code Have to Be Printed on the Food Package?
Not necessarily.
FDA states that the Food Traceability Rule doesn’t require the TLC itself to appear on the food label or package.
The required information can be communicated to the next recipient through methods such as a bill of lading, advance shipment notice, electronic record, email, or QR code, provided the information is transmitted in a way that allows the recipient to maintain the records required by the rule.
Therefore:
FDA Traceability Lot Code ≠ automatically a consumer-visible lot number printed on the package.
A manufacturer may nevertheless choose to print a useful lot identifier on the package because it can be extremely valuable for complaints, investigations, withdrawals, and recalls.
Internal Lot Codes vs. FDA Traceability Lot Codes
A business can maintain both.
For example, a distributor might assign its own internal inventory lot identifier while also preserving the FDA-required TLC associated with an FTL food.
FDA specifically recognizes that companies may maintain internal lot numbers. When the Food Traceability Rule applies, however, an internal lot number doesn’t replace the regulatory TLC merely because the company’s software calls both fields “lot number.”
Systems should therefore be designed to distinguish the two where necessary.
Do I Need to Worry About the Food Traceability Rule?
Start by determining whether you manufacture, process, pack, or hold a food on FDA’s Food Traceability List.
The FTL identifies foods subject to the additional traceability recordkeeping requirements. It also covers certain foods containing an FTL-listed food as an ingredient when that listed ingredient remains in the same form in which it appears on the list.
If you handle FTL foods, determine whether an exemption applies and which Critical Tracking Events you perform. You should also understand which Key Data Elements apply, whether and when you must assign or preserve a TLC, what information must be shared with trading partners, and what your traceability plan must contain.
Don’t assume that ordinary batch records automatically satisfy all of these additional requirements.
What Should a Small Manufacturer’s Traceability System Do?
At a basic level, think about traceability in three directions.
First:
Supplier → Ingredient Lot
Who supplied this particular ingredient lot?
Second:
Ingredient Lot → Finished Product Lot
Which production batches and finished products used it?
Third:
Finished Product Lot → Customer
Where did the finished product go?
Together, that creates the fundamental traceability chain:
Supplier → Ingredient Lot → Production Batch → Finished Lot → Shipment → Customer
Spreadsheet Lot Tracking
A very small manufacturer can begin with spreadsheets.
An ingredient receiving log might look like:
| Ingredient | Supplier | Supplier Lot | Received | Quantity |
| Cocoa Butter | Supplier A | CB44172 | 9/20/26 | 500 lb |
The production record might then contain:
| Finished Product | Finished Lot | Ingredient Lot | Quantity Used |
| Dark Chocolate | DC260927-01 | CB44172 | 80 lb |
And the shipment record:
| Finished Lot | Customer | Quantity | Ship Date |
| DC260927-01 | Grocery A | 120 bars | 9/29/26 |
You can now trace:
CB44172 → DC260927-01 → Grocery A
That’s basic lot traceability.
When Spreadsheets Become Difficult
Spreadsheets can work when your operation is small.
Complexity increases quickly, however, when you have hundreds of ingredients, many suppliers, multiple warehouses, partial ingredient lots, many finished-product lots, rework, co-packers, multiple customers, transfers, returns, shelf-life extensions, and production holds.
Eventually, answering a seemingly simple question such as:
“Which customers received products containing Supplier Lot CB44172?”
can require searching many disconnected spreadsheets.
That’s when dedicated inventory and traceability software becomes much more valuable.
Lot Codes and Inventory
Lot tracking works best when inventory itself is lot-specific.
Instead of knowing only:
Cocoa Butter: 1,200 lb
your inventory system ideally knows:
| Ingredient Lot | Quantity |
| CB44172 | 350 lb |
| CB44811 | 500 lb |
| CB45092 | 350 lb |
Production can then record exactly which inventory lot was consumed.
Lot-specific inventory also supports FIFO and FEFO inventory practices.
Lot Codes and Shelf Life
Lot tracking can connect directly to shelf-life management.
For each ingredient lot, you might maintain the received date, manufacture date, Best-By date, and expiration date.
For each finished lot, you might maintain manufacture date, release date, Best-By date, and expiration date.
This allows inventory systems to identify which lots should be used or shipped first and which lots are approaching expiration.
Lot Codes and Holds
Suppose a laboratory test is pending for one finished lot.
You don’t necessarily want to stop shipping every product in the warehouse. Instead, you can place LOT 260927-01 on HOLD.
A properly configured inventory system can prevent that particular lot from being allocated or shipped until an authorized person releases it.
This is another reason lot-specific inventory becomes valuable as a manufacturer grows.
Lot Codes and Recalls
A useful recall system should allow you to start with either a supplier lot or a finished-product lot and quickly identify the affected chain.
For example:
Supplier Lot CB44172
↓
Finished Lots:
DC260927-01
DC260927-02
DC260928-01
↓
Customers:
Distributor A
Grocery B
Grocery C
↓
Quantities:
Known and reconcilable
That’s far better than:
“We know we used that ingredient sometime last month.”
Run a Mock Recall
Don’t wait for a real problem to discover that your lot records don’t work.
Periodically select a finished-product lot and ask whether you can identify every ingredient lot used.
Then select an ingredient lot and determine whether you can identify every finished lot containing it.
Next, determine whether you can identify every customer who received those finished lots.
Finally, reconcile the quantities.
For example:
| Lot Disposition | Quantity |
| Produced | 1,000 |
| Shipped | 700 |
| Still in inventory | 200 |
| Samples | 50 |
| Damaged | 30 |
| Consumed/other documented disposition | 20 |
| Total accounted for | 1,000 |
The closer you can get to accounting for the complete lot, the more useful your traceability system becomes.
Food Lot Code Checklist
Lot Definition
- ☐ What constitutes a lot?
- ☐ One batch?
- ☐ One production day?
- ☐ One shift?
- ☐ Another defined production interval?
Lot Number
- ☐ Is each lot uniquely identifiable?
- ☐ Could codes accidentally be reused?
- ☐ Can employees read and enter them accurately?
- ☐ Does each code reliably connect to production records?
Production
- ☐ Finished lot recorded?
- ☐ Production date recorded?
- ☐ Formula version recorded?
- ☐ Ingredient lots recorded?
- ☐ Packaging lots recorded where appropriate?
- ☐ Quantity produced recorded?
- ☐ Quality and food-safety checks linked to the lot?
Packaging
- ☐ Lot code applied?
- ☐ Correct lot code?
- ☐ Code legible?
- ☐ Code durable?
- ☐ Code location consistent?
Inventory
- ☐ Finished inventory tracked by lot?
- ☐ Ingredient inventory tracked by lot?
- ☐ Expiration and Best-By dates linked to lots?
- ☐ Holds applied at lot level?
Distribution
- ☐ Customer shipments record finished lots?
- ☐ Quantity shipped by lot recorded?
- ☐ Returns maintain lot identity?
Traceability
- ☐ Finished product → ingredient lots?
- ☐ Ingredient lot → finished products?
- ☐ Finished lot → customers?
- ☐ Mock recall tested?
- ☐ Quantities reconciled?
Regulatory
- ☐ Is the food on FDA’s Food Traceability List?
- ☐ Does an exemption apply?
- ☐ Which Critical Tracking Events apply?
- ☐ Are applicable TLCs assigned or preserved?
- ☐ Are required Key Data Elements maintained?
- ☐ Is a traceability plan required?
- ☐ Has current FDA implementation guidance been reviewed?
Example of a Simple Lot-Code Policy
A small manufacturer could adopt a policy such as:
Each production batch will receive a unique lot number in YYMMDD-BB format, where YY represents the year, MM represents the month, DD represents the production date, and BB represents the sequential batch number for that production day.
For example:
260927-01
means:
September 27, 2026 — Batch 1
The production record associated with that lot can contain the product, formula version, ingredient lots, packaging lots, quantity, operators, quality checks, production times, and finished-product disposition.
Shipment records then identify which customers received inventory from that lot.
That’s a simple system, but it’s dramatically better than having no lot-level traceability.
Frequently Asked Questions About Food Lot Codes
What is a lot number on food?
A lot number identifies a particular production lot or batch of food and connects the package or inventory to manufacturing and traceability records.
Is a lot number the same as a batch number?
The terms are often used similarly in food manufacturing, although individual companies can define “batch” and “lot” somewhat differently.
Does FDA require lot numbers on all packaged foods?
There isn’t one universal FDA consumer-package lot-code requirement applying identically to every conventional packaged food. Particular products and operations can have specific requirements, and foods subject to FDA’s Food Traceability Rule have additional traceability requirements, including TLC requirements at specified Critical Tracking Events.
Does a food lot code have to contain the manufacturing date?
Not necessarily. A manufacturer can use an alphanumeric code that connects to records containing the production date and other relevant information.
Can I use the production date as my lot number?
Yes, a lot-code system can be based on the production date, but the code should distinguish all lots you need to distinguish. If multiple batches are produced on the same day, add a batch, run, or sequence identifier when appropriate.
Can the Best-By date be the lot code?
A company’s coding system can use date information for traceability, but a Best-By date alone might not distinguish multiple production batches sharing the same date. A dedicated lot identifier often provides more precise traceability.
Is the lot number the same as the UPC?
No. The UPC or GTIN identifies the product. The lot number identifies a particular production lot of that product.
Is the lot number the same as an SKU?
No. A SKU identifies a product within an inventory system. A lot code identifies a particular production group of that product.
Should I print the lot number on the package?
For many manufacturers, printing a lot identifier on the package is extremely useful because consumers, retailers, employees, and investigators can use it to identify particular production during complaints, investigations, withdrawals, or recalls. Specific legal requirements depend on the product and applicable regulations.
Does FDA’s Traceability Lot Code have to appear on the package?
No. FDA states that the Food Traceability Rule doesn’t require the TLC to appear on the food label or package. Required traceability information can be transmitted through other appropriate records.
What is an FDA Traceability Lot Code?
Under FDA’s Food Traceability Rule, a TLC is a descriptor, often alphanumeric, used to uniquely identify a traceability lot within the records of the firm that assigned the code.
When is a Traceability Lot Code assigned?
Under the Food Traceability Rule, TLCs are assigned when a covered firm initially packs certain raw agricultural commodities, performs first land-based receiving of food obtained from a fishing vessel, or transforms a covered food. Special provisions apply in certain situations involving food received from exempt entities.
Is the FDA Food Traceability Rule currently being enforced?
As of September 2026, FDA states that Congress directed the agency not to enforce the Food Traceability Rule before July 20, 2028, and FDA intends to comply with that directive. The rule itself remains in place, and FDA continues to work with industry on implementation and possible flexibilities.
Should every production batch have a different lot number?
For many small batch manufacturers, assigning a unique lot to each production batch is a simple and effective approach. The appropriate lot definition depends on the manufacturing process, risk, customer requirements, and traceability objectives.
How long should lot records be kept?
There isn’t one universal retention period covering every lot-related record in every food operation. Record-retention requirements depend on the applicable regulations, customer requirements, certification standards, and the type of record. The Food Traceability Rule, for example, generally requires records covered by that rule to be retained for two years unless otherwise specified.
The Bottom Line
A lot code might look like:
260927-01
printed in tiny characters on the back of a package.
But behind those characters should be an entire traceability chain.
In one direction:
Finished Product → Production Batch → Ingredient Lots → Suppliers
And in the other:
Finished Lot → Inventory → Shipment → Customer
That’s what makes the code valuable.
For a very small manufacturer, the system can begin simply:
- One production batch = one lot.
- Record every ingredient lot used.
- Put a usable finished-product lot identifier on the package.
- Record which customers receive each finished lot.
- Test the system with a mock recall.
As the company grows, those same principles can expand into computerized inventory, purchasing, production, lot traceability, shelf-life management, quality control, holds, shipping, and recall management.
The goal isn’t to create complicated lot numbers.
The goal is to be able to answer three questions quickly when something goes wrong:
What happened? What was affected? Where did the affected product go?
A good lot code is the key that unlocks those records.
References / Sources
U.S. Food and Drug Administration — Traceability Lot Code
FDA explanation of Traceability Lot Codes, TLC sources, assignment events, lot definition, internal coding flexibility, and methods for communicating TLC information.
U.S. Food and Drug Administration — FSMA Final Rule on Requirements for Additional Traceability Records for Certain Foods
FDA’s current overview of the Food Traceability Rule, Critical Tracking Events, Key Data Elements, Traceability Lot Codes, traceability plans, and current implementation status.
U.S. Food and Drug Administration — Frequently Asked Questions: FSMA Food Traceability Rule
Detailed FDA answers concerning TLC assignment, internal lot codes, TLC source information, packaging, records, and supply-chain communication.
U.S. Food and Drug Administration — Food Traceability List
FDA’s current list of foods subject to additional traceability recordkeeping requirements, subject to applicable exemptions.
Electronic Code of Federal Regulations — 21 CFR Part 1, Subpart S
Federal regulatory text establishing additional traceability records for certain foods.
U.S. Food and Drug Administration — Food Recalls: What You Need to Know
FDA information illustrating how product names, package sizes, UPCs, lot codes, dates, photographs, and distribution information are used to identify recalled products.
U.S. Food and Drug Administration — FDA 101: Product Recalls
Additional FDA information concerning recall identification and communication.
Disclaimer: This article provides general information about food lot coding and traceability and isn’t legal or regulatory advice. Lot-code, traceability, recordkeeping, recall, and labeling requirements vary depending on the food, process, facility, customer, and regulations that apply. FDA’s Food Traceability Rule establishes additional requirements for covered foods on the Food Traceability List, subject to applicable exemptions, and its implementation status continues to develop. Food manufacturers should review current federal, state, local, customer, and certification requirements applicable to their operation.
