A bakery traceability system needs four records. You record what came in, with the supplier's lot, and which of those lots went into each batch. You give each bake a lot code, and you record which customers got which lots. Under the Safe Food for Canadians Regulations, the first and last are required for any bakery that ships to another province or holds an SFC licence. The middle two decide whether a supplier's recall costs you two days of sesame buns or everything you baked that month.
The short version
- Keep the supplier's lot on every delivery of flour, seeds, dairy, eggs and fillings.
- Write down which lots went into each batch, on the day.
- Code each bake by day and oven line, like
20261116L2, and put the code on the bag. - Treat a silo or bin as a mix of lots until it's emptied.
- Give dough, fillings and toppings made ahead their own lot, and carry it into the bake.
- Rework (yesterday's bread into today's crumbs) carries yesterday's lot.
- TaroStack records the batch's lots for you as you bake. More at the end.
Is your bakery covered?
Part 5 of the SFCR applies if you send food to another province, import or export it, or hold an SFC licence to make or package it. A bakery that sells only over its own counter in its own province may not be. The day it delivers a pallet of bread to a grocer across the provincial line, it is, along with a written recall procedure, a yearly recall simulation and a complaints procedure. The rules in plain words cover who's in.
A bakery's own retail counter keeps one step back (what the food is, and its suppliers) but doesn't record each shopper.
This is general information, not legal advice. Your CFIA inspector has the last word on what applies to you.
The four records, bakery version
| Record | In a bakery | What it answers |
|---|---|---|
| Receiving | Each delivery of flour, seeds, butter, eggs, fillings: supplier, address, date, their lot | Which deliveries a supplier's recall reaches |
| Batches | Which ingredient lots went into each mix, and the lot code of what came out | Which of your lots a supplier's lot reached |
| Lot codes | One code per bake, on the bag and the case | What a customer can find on the shelf |
| Shipping | Which lots went to which customer, how much, when | Who to call |
The SFCR asks for receiving and shipping by name, address and date. It doesn't ask for the batch link. Without it, though, a recall can't be narrowed, and the CFIA's inspector will follow one ingredient through to the package on the floor, so the link is what they test. Here's a template that holds all four.
Where bakeries lose the trail
Most bakery trace problems come from five places that other food makers don't have, or not as much.
The flour silo or bin is the first. When a new delivery goes into a silo that still has flour in it, the next mixes use both lots. My advice is to record both as inputs until the silo has been run empty, and run it empty now and then on purpose so the mix of lots has an end.
Dough and preferments made ahead are the second. A dough mixed on Monday and baked on Tuesday, or a frozen dough baked over a week, has its own ingredient lots. Give it its own lot when it's mixed, and record that lot as the ingredient of each bake. A sourdough starter, kept going for years, is easier: record the flour lots that feed it, at least.
Fillings and toppings are the third: custard, streusel, a seed mix in a topping bin. Each is a small batch with its own lots, and the seed bin is a silo in miniature.
Rework is the fourth. Yesterday's unsold loaves ground into crumbs, or broken cookies folded into a new batch, carry yesterday's lot. The CFIA's inspection procedure mentions pre-mixed and reworked ingredients by name.
The counter is the fifth. Loaves sold from the bakery's own shop are covered as retail sales: no record of each shopper, but the lot still has to be on what you made, and your counter sales still count when you add up where a lot went.
Lot codes that keep a recall small
The CFIA's advice is to decide what a lot is first, then code it. For most bakeries, a day and an oven line is narrow
enough to keep a recall small: 20261116L2 is the second line on November 16. If the same line bakes several products,
the code still works, because the product's name is on the label beside it. More on CFIA lot
codes.
A best-before date can stand in for the lot code if each day's bake has its own date. Two shifts with the same best-before date need a shift digit as well.
A sesame recall, worked through
A 14-person bakery in Ontario gets a call from its seed supplier: sesame seed lot SS-1107 may contain peanut. Allergens
were behind 57 of the 185 recall incidents in the CFIA's figures for 2025 to 2026.
With the four records, the bakery's answer goes like this:
- Receiving:
SS-1107came in once, on November 2, 4 bags of 10 kg. - The topping bin: refilled from
SS-1107on November 3, emptied and cleaned on November 7. SoSS-1107went on whatever was topped from November 3 to 7. - Batches: sesame burger buns on November 3, 4 and 6, and bagels on November 5 and 7. Five lots.
- Shelves: 210 bags of buns and 90 bags of bagels still at the bakery, held and set apart.
- Shipping: eight customers in Ontario and Quebec received those five lots.
The bakery calls eight customers about five lots, not every customer about every sesame product it made that month. Step 2 is the bakery-specific one. Without the bin record, the honest answer is "everything topped since November 3, until someone can prove otherwise."
The same steps, without a real recall, are the yearly simulation the SFCR asks for. Here's how to run one, and how to write it up.
Where this stops working
On paper, the batch record is a clipboard by the mixer. It's filled in between batches by someone with flour on their hands, and the lot numbers it needs are on bags that went in the bin last week. The topping bin and the silo have no paperwork at all. By the time a supplier calls, the sheet for November 3 may say "sesame" and nothing else, and the recall widens to everything.
The other drift is between the bakery's three systems: the receiving clipboard, the batch sheets and the invoicing program. Each is right on its own, and the trace is only as good as the matching between them.
How TaroStack does it
TaroStack keeps the four records as one, so the trace is there before the supplier calls.
When flour or seeds come in, you record the supplier's lot, or scan it off a GS1-128 case label. When you finish a batch, TaroStack takes the ingredients from the lots that expire first and writes down which ones it used, so the batch record fills itself in. You change it only when you used a different bag. A dough, a filling or a seed mix made as its own batch gets its own lot, and the bake that uses it records that lot like any other ingredient. Recipes can have sub-recipes for exactly this: dough, fillings, toppings.
Each bake gets its lot code, yours or the batch's own number, and a printable lot label. Each shipment records which lots went to which customer. Then any lot, the mill's or yours, opens a trace: every batch it reached, how much is still on your shelves and where, and every customer who received it, with dates and quantities.
The report carries the names and addresses the SFCR asks for, and it downloads as one CSV file for the CFIA.
The yearly simulation is a timed drill in TaroStack, saved with how long it took and what it found.
TaroStack reminds you before 12 months pass without one.
| Clipboard and invoices | TaroStack | |
|---|---|---|
| Which flour went into a mix | Written by the mixer, if there's time | Recorded with the batch |
| Dough and fillings made ahead | Usually not traced | Their own lot, carried into the bake |
| Who got a lot | Matched from invoices | Recorded when the order ships |
| The yearly simulation | Easy to forget | A timed drill, with a reminder |
Lots, recalls, sub-recipes and drills are on every TaroStack plan. Starter is $9.99 a month for one person; a bakery where three people record batches would be on Growth, at $39. It's free for 14 days. If you'd like a hand setting up your recipes and lots, ask, and we'll do it with you.
