Skip to content

SFCR Traceability Requirements, in Plain Words

What Canada's food traceability rules ask you to record, who they cover, how long to keep it, and the one file the CFIA can ask for within 24 hours.

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

Canada's traceability rule asks you to be able to follow any food you sell one step back, to who supplied it and its ingredients, and one step forward, to who you sold it to. Each step needs a name, an address, a date and a lot code. You keep those records for two years, and when the CFIA asks, you hand them over within 24 hours, as one plain-text file if you send them electronically. That's Part 5 of the Safe Food for Canadians Regulations, sections 90 to 92.

The short version

  • Give every lot of what you make a lot code, and put it on the label of consumer prepackaged food.
  • For every lot, record who supplied each ingredient (name, address, date received) and who you sold it to (name, address, date).
  • Keep it two years, somewhere it can be reached from Canada.
  • Be able to produce it within 24 hours as a single file a spreadsheet program can open.
  • TaroStack records all four as a side effect of receiving, making and shipping, and produces the file in one click.

Who the rule covers

More businesses than the licence does. Traceability applies to you if you:

  • send or convey food from one province to another, import it or export it;
  • hold an SFC licence to manufacture, process, treat, preserve, grade, store, package or label food (or to slaughter);
  • grow or harvest fresh fruit or vegetables that go to another province or abroad; or
  • sell food at retail (restaurants and similar places selling meals and snacks are left out).

A bakery that sells only in its own shop in its own province may not be covered. The day it ships one pallet of bread to a grocer across the provincial line, it is. Selling across provinces covers what else changes that day.

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

What you have to record

Section 90(1) lists four things. In plain words:

SFCR What to keep Example from a bakery
90(1)(a) The food's common name, its lot code, and the name and principal place of business of whoever made, stored, packaged or labelled it Dark rye bread, lot 20261116L2, made by the bakery at its Hamilton address
90(1)(b) The date you provided it, and the name and address of who you provided it to 16 Nov 2026, 120 loaves to a grocer in Gatineau, with its address
90(1)(c) Who provided the food to you, their address, and the date you received it For something you buy and resell: the supplier, their address, the delivery date
90(1)(d) The name of each ingredient (the regulation says "food commodity"), and its supplier's name and address and the date you received it Rye flour, from the mill at its address, delivered 9 Nov 2026

Retailers keep (a), (c) and (d): what the food is, and one step back. They don't track each shopper.

Notice what (d) doesn't say. It asks for the ingredient, its supplier and the delivery date, not the supplier's lot code or which delivery went into which lot of bread. You can meet the letter of it and still be unable to say which loaves a flour recall reaches. That link is a batch record that notes the ingredient lots (the mill's lot R4471, say), and it's what keeps a recall to five days of rye instead of a month of everything. Here's how to keep it.

The lot code and the label

Section 92 says the food has to carry, or come with, a label showing its common name, the name and principal place of business of the person it was made by or for, and a lot code. For consumer prepackaged food (the bag of buns on a shelf) the lot code is required on the label. For cases and other packaging, a lot code or another unique identifier like a purchase order number will do.

The CFIA's advice on choosing one is good and short: decide what a lot is first (a day, a shift, an oven line), then pick a code that names it, like 20261116L2 for the second line on 16 November. The narrower the lot, the narrower your recall. More on CFIA lot codes.

How long, and where

Two years after the day you provided the food to someone (retailers: two years after the day it was sold). The records have to be accessible in Canada. They can sit on a server elsewhere, as long as you can reach them from here.

The 24-hour request

Section 91 is the part that tests everything else. When the CFIA asks for your traceability records, you have 24 hours, or less if they think there's a health risk. If you send them electronically, they have to come as "a single file and in plain text that is capable of being imported into and manipulated by standard commercial software." A CSV file does that. Forty photos of batch sheets don't. Here's how to answer that request.

When an inspector visits, they'll test it in person: pick a product you've shipped and ask you to trace it one step forward and its ingredients one step back. That's in the CFIA's own inspection procedure.

A worked example

A 14-person bakery in Ontario gets a call from its flour mill: rye flour lot R4471 is being recalled for a possible foreign object. Here's what the bakery's records have to answer, and in what order.

  1. Which deliveries of flour were lot R4471? Two: 9 November (40 bags of 20 kg) and 13 November (20 bags).
  2. Which batches used them? Five days of dark rye and two of a multigrain loaf, seven lots in all.
  3. How much of each lot is still here? 310 loaves across the bakery and its retail counter.
  4. Who received the rest? Eleven customers: nine grocers in Ontario, two in Quebec, with dates and quantities.

The answers to 1 and 4 are what section 90 asks you to keep. The link between them, steps 2 and 3, is what makes the answer specific. Without it, the bakery recalls every rye product it shipped in November.

Where this stops working

Most small food makers start with a spreadsheet: one tab for deliveries, one for batches, one for orders. It works while one person keeps it, and every lot code is typed the same way twice. It stops working on the day the flour mill calls, because the answer to step 2 means reading down the batch tab for a supplier lot somebody may have typed as R-4471, and step 4 means matching those batches against invoices in another program. The CFIA's 24 hours is plenty of time to search. It isn't much time to reconcile three files that never agreed.

How TaroStack does it

TaroStack keeps the trace as you work, so there's nothing to reconcile when someone asks.

When a delivery comes in, you record the supplier's lot (or scan it off a GS1-128 case label) and TaroStack keeps the date and supplier. When you record a batch, it notes which ingredient lots went into it, first-expired-first-out by default, and gives the batch its own lot code and a printable lot label. When an order ships, it records which lots went to which customer. That's 90(1)(a) to (d), filled in by doing the work you already do.

Then any lot, yours or a supplier's, opens a trace: every delivery of it, every batch it reached, how much is still on your shelves and where, and every customer who received it, with dates and quantities.

The trace report carries the names and addresses section 90 asks for, yours, your customers' and your suppliers', and every delivery of a lot with its own date.

It downloads as one CSV file, one lot or several, which is the single plain-text file section 91 describes.

Lot labels carry the common name, your business name and address, and the lot code.

Nothing is deleted, so the two years look after themselves. And when you want to know whether you could answer the CFIA in time, run a timed drill: TaroStack records how long the trace took and what it found.

Spreadsheet TaroStack
Which ingredient lots went into a batch Typed in by hand, if at all Recorded with the batch
One step forward from a lot Matched against invoices Recorded when the order ships
The CFIA's 24-hour request Several files, reconciled One CSV file
Two years of records Whatever survived Kept

Lots, recalls and traceability drills are on every TaroStack plan, from $9.99 a month. It's free for 14 days, and you can bring your suppliers, customers and items from spreadsheets. If you'd like a hand setting up, ask, and we'll do it with you.

TaroStack keeps the records the rule asks for. Meeting the rule is still your business's job, and your inspector's call.

Questions people also ask

What is traceability in food safety?

Being able to say where a food came from and where it went, one step each way, quickly. The CFIA's own definition is "the ability to track the movement of a food product, one step forward and one step back in the supply chain."

Do restaurants have to follow the SFCR traceability rules?

No. Restaurants and similar businesses that sell food as a meal or snack are excluded from the traceability requirements. A restaurant that also makes jars of sauce to sell in grocery stores is a different story for the sauce.

Is a best-before date a lot code?

It can be, if it marks the day the food was made and a day is your lot. The CFIA's lot code guidance gives that as an example. If you make two lots a day, you need something more.

How is this different from the US traceability rule?

The US has its own rule for foods on FDA's Food Traceability List, with different records and a sortable spreadsheet. FDA has proposed moving its compliance date to July 20, 2028, and Congress directed it not to enforce the rule before then. If you export to the US, our one up, one back article covers the American side.

Does the CFIA provide a traceability template?

The CFIA has an interactive tool that tells you which rules apply, but no fill-in record. Our SFCR traceability template lays out the columns.

Sources

  1. Safe Food for Canadians Regulations, SOR/2018-108, Part 5 Traceability (s.90 to 92) · read November 16, 2026
  2. CFIA: Traceability for food · read November 16, 2026
  3. CFIA: What to consider when selecting a lot code · read November 16, 2026
  4. CFIA operational procedure: Food preventive control and traceability inspection, System Verification (Element 7) · 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.