Skip to content

CFIA Lot Code Requirements, Explained With Examples

When a food label in Canada needs a lot code, what it can look like, and how big and in which language it goes on the package, from the SFCR and the CFIA.

By Koa Sterling. Product specialist at TaroStack and small business owner. Yes, I am a real human, and I actually sit in front of a computer and write these articles. Reviewed November 16, 2026 · 8 min read

Under the Safe Food for Canadians Regulations, food you provide to another business has to carry, or come with, a label showing its common name, the name and principal place of business of whoever made it (or had it made), and a lot code or other unique identifier. For consumer prepackaged food, the bag of buns on a store shelf, it has to be a lot code. That's section 92. The format is yours to choose. The CFIA's advice is to decide what a lot is first, then pick a code that names it.

The short version

  • Consumer prepackaged food needs a lot code on the label. Cases and bulk food need a lot code or another identifier that lets the food be traced.
  • A lot is food made "under the same conditions": a day, a shift, a line. You decide how narrow it is.
  • The narrower the lot, the smaller your recall. A day and an oven line, like 20261116L2, is a good start.
  • A best-before date can be your lot code if each day's production gets its own date.
  • Make it legible. The CFIA's best practice is characters at least 1.6 mm high. A code with words in it has to be in English and French.
  • A lot code only helps if your records link it to the ingredient lots that went in and the customers it went to. TaroStack keeps that link. More at the end.

What the regulation says

Section 92(1) says anyone covered by Part 5 of the SFCR must make sure food they provide to another person has a label with the information in section 90(1)(a): the food's common name, "a lot code or other unique identifier that enables the food to be traced", and the name and principal place of business of the person by or for whom it was manufactured, prepared, produced, stored, packaged or labelled. The label can be applied, attached, or sent with the food.

Section 92(2) narrows it for consumer prepackaged food that isn't packaged at retail. There, the identifier has to be a lot code.

Food What identifies it Where
Consumer prepackaged food (the package a shopper buys) A lot code On the label
Cases, totes, bulk sold to another business A lot code or another unique identifier On the label, attached, or with the food
Food at the time it's exported Not required by section 92
Food other than consumer prepackaged, at the time of a retail sale Not required by section 92

There are a few narrower exceptions at retail: one-bite confections sold one at a time, and fresh fruit or vegetables in a band or wrapper under 13 mm wide (section 213). If you're not sure Part 5 covers you at all, start here.

This is general information, not legal advice. Your CFIA inspector has the last word on what applies to you.

Decide what a lot is first

The CFIA describes a lot code as one that identifies food made "under the same conditions", and it leaves the definition of a lot to you. The trade-off is plain: a broad lot means a broad recall. The CFIA's own example is strawberries. Define the lot as a growing region and a problem recalls the whole region's fruit. Define it as a harvest date and the recall stops at the days involved.

For a bakery the choice usually looks like this:

Your lot is The code could be What a problem on Nov 16 recalls
A week 2026W47 Seven days of everything
A day 20261116 One day, every line
A day and a shift 20261116s2 Half a day
A day and a line 20261116L2 One oven line, one day
A day, a shift and a line 20261116s2l2 One line, half a day

The last three follow the CFIA's examples, which use year, month and day, then s and the shift, then l and the line. A day and an oven line is where I'd start for a small bakery. It's narrow enough to keep a recall small and simple enough that nobody gets it wrong at 5 a.m.

The CFIA's test for your code is two questions. Does it identify one lot made under the same conditions? And, for a more targeted recall, could it leave out food that wasn't involved? You should also be able to explain what each part of the code means when an inspector asks.

Can a best-before date be the lot code?

Yes, according to the CFIA, if it shows which day the food was made, so each day's production has its own best-before date. If you make two lots a day with the same best-before date, it isn't enough on its own. Add a shift or line after it.

One thing changes when a best-before date does double duty. It has to follow the label rules for a best-before date as well, so it goes on the package itself. "Accompanies the food" stops being an option for most prepackaged food.

A Julian date code (26320 for the 320th day of 2026) is also a common way to code a day, and nothing in the SFCR rules it out. The same test applies: you have to be able to explain it, and it has to separate lots that need separating. How Julian date codes work.

On the package: size, place and language

  • The SFCR asks that label information be clearly and prominently shown and readily discernible, but sets no size for a lot code. The CFIA's best practice is characters at least 1.6 mm (1/16 inch) high.
  • The CFIA gives colored text on a similar background, and embossed codes on cardboard or plastic with no contrast, as examples that may not be legible enough.
  • The code can go on the top, bottom or side of the package, by inkjet, sticker or stamp.
  • If the code contains a word, or starts with one, it has to be in English and French on consumer prepackaged food (with the usual exceptions for labels allowed in one language). A code of numbers and letters like 20261116L2 has nothing to translate. Adding "Lot #" isn't required, but it helps people find the code.

If you buy food that already has a lot code and sell it on unchanged, the CFIA says you generally don't need to make a new one. Record the supplier's code when it comes in, because that's the code a recall will use.

Where this stops working

The code on the bag is the easy half. It's only useful if your records can answer two questions about it: which ingredient lots went into 20261116L2, and which customers got it. On paper, the first answer is a batch sheet where someone wrote "rye, 4471" or nothing at all. The second is a stack of invoices that may or may not list the lot.

A date stamp also goes wrong in ordinary ways. Somebody forgets to roll the date gun forward after midnight. Line 2's codes go on line 1's bags. The code on the case and the code on the invoice don't match. None of it shows until the day you need the code to mean something.

How TaroStack does it

TaroStack makes the lot code the thing every record hangs on.

When you finish a batch, type your own code into the lot box, in the format you've defined, or leave it and the batch's own number becomes its lot code. The batch already knows which ingredient lots it used. TaroStack takes them first-expired-first-out and writes them down, so the first question is answered before anyone asks it. When the order ships, the lot goes with it, so the second is too.

Lot labels print from the lot: the item's name, the lot code, its dates, and a GS1-128 barcode carrying the GTIN, use-by and lot when the item has a GTIN, which some distributors ask for on cases.

Each label also carries your business name and address, the other part of section 92.

When a supplier's case comes in with a GS1-128 label, scanning it fills in their lot and date, so the supplier's code is recorded exactly as printed. And any code, yours or theirs, opens a trace: every batch it reached, what's still on your shelves, and every customer who got it.

A date gun and paper TaroStack
Your lot code Stamped on the bag Typed or set from the batch, printed on the label
The ingredient lots in it Whatever made it onto the batch sheet Recorded with the batch
Who got it Invoices, if they list lots Recorded when the order ships
A supplier's code Copied by hand Scanned from the case label

Lots, lot labels and recalls are on every TaroStack plan, from $9.99 a month. It's free for 14 days. If you'd like a hand setting up your lot codes, ask, and we'll do it with you.

Questions people also ask

Does every package need a lot code in Canada?

Every consumer prepackaged food that isn't packaged at retail does, if Part 5 of the SFCR covers your business. Cases and bulk food going to another business need a lot code or another identifier that lets them be traced.

Do lot codes have to be bilingual?

Only if the code contains words. A code made only of numbers and letters like 20261116L2 reads the same in both languages.

How big does a lot code have to be?

The SFCR sets no size. The CFIA's best practice is characters at least 1.6 mm (1/16 inch) high, legible against the package.

Is a lot code the same as a batch number?

Often, and it can be. A batch number counts batches; a lot code identifies a lot on the label. If one batch is one lot, one number can do both. Batch number vs lot number goes through the difference.

Who decides my lot code format?

You do. Nothing in the SFCR prescribes a format, and the CFIA's guidance asks that you can explain your code and that it identifies food made under the same conditions.

Sources

  1. Safe Food for Canadians Regulations, SOR/2018-108, Part 5 Traceability (s.90 to 92) · read November 16, 2026
  2. CFIA: What to consider when selecting a lot code (modified 2024-11-25) · read November 16, 2026
  3. CFIA: Traceability for food · read November 16, 2026

We use AI to help with the research for these articles. Every one is read, checked against its sources and edited by Koa before it's published. Spot a mistake? Tell us and we'll fix it and say so. How we write these.

Let’s get your stack in order.

Get TaroStack

Sign up now for your free 14 day trial. No credit card required.