Under the Safe Food for Canadians Regulations, every licence holder needs a written recall procedure that would let them recall a food effectively, and it has to name two people: one responsible for the procedure and one responsible for running recalls. That's section 84(1). The CFIA's guide breaks a recall into twelve steps, and the template below follows them, so a small business can fill it in over an afternoon.
The short version
- Write it down. The rule asks for a document, and an inspector will ask to see it.
- Name the two people the regulation asks for, with a backup and an after-hours number for each.
- Follow the CFIA's twelve steps in order: team, notify the CFIA, find the food, hold it, distribution list, notice, effectiveness, returns, disposal, corrective action, review.
- Test it at least once every 12 months with a recall simulation, and keep the record for two years.
- TaroStack keeps the procedure, the two names and the trace in one place, so the document and the recall it describes never drift apart.
What the regulation actually says
Section 84 is short enough to read whole, and worth it. An operator must:
- Prepare, keep and maintain "a document that sets out a recall procedure that enables the effective recall of a food", with "the name of a contact person who is responsible for the procedure and the name of a contact person who is responsible for conducting recalls." That's 84(1).
- Run a recall simulation based on that procedure at least once every 12 months, and keep a record of how it went for two years. That's 84(2), and it has its own article.
- Tell the CFIA immediately if a food should be recalled because it's a risk to health. That's 84(3).
- In a real recall for a health risk, carry out the procedure immediately and document the recall, "including any information that substantiates its effectiveness", kept for two years. That's 84(4).
Who it applies to: anyone holding an SFC licence, the growers and harvesters of fresh fruit and vegetables who need a preventive control plan, and importers (section 85 adds them). If you're not sure you need a licence, start there. The recall procedure isn't part of the $100,000 small-business exemption. That exemption only spares the preventive control plan, so a small bakery that ships to another province still needs this document.
This is general information, not legal advice. Your CFIA inspector has the last word on what applies to you.
The CFIA's inspection procedure tells inspectors to check that both names are there and that your latest simulation is on file, then to trace one shipped product forward and its ingredients back, on the spot. So the procedure has to describe what your people really do. Here's the rest of that visit.
The template
This one is laid out for a 14-person bakery in Ontario that sells bread and buns to grocers and cafés in Ontario and Quebec. Change the names and cross out what doesn't apply. A five-person business will see the same name in several boxes, and that's fine. What matters is that nobody has to ask who does what.
1. The two people the regulation names
| Role (s.84(1)) | Name and position | Phone | After hours | Backup |
|---|---|---|---|---|
| Responsible for this procedure | ___ , owner | ___ | ___ | ___ |
| Responsible for conducting recalls | ___ , production manager | ___ | ___ | ___ |
The first person keeps the document current: new products, new customers, new phone numbers. The second runs a recall when one happens. They can be the same person in a very small business, but give each role a backup, because recalls have a way of starting on the one week somebody is away.
2. The recall team
The CFIA's guide suggests these jobs. Put a name beside each one that applies:
| Job | Who |
|---|---|
| Investigating complaints and food safety incidents | |
| Quality and technical advice | |
| Deciding to recall | |
| Talking to the CFIA | |
| Customer calls and the notice of recall | |
| Holding and counting product still here | |
| Media and consumers (if a public warning goes out) | |
| Legal advice (outside) |
3. When we consider a recall
Write down what starts the process for your business: a supplier telling you an ingredient lot is affected, a complaint that suggests illness, a foreign object or an undeclared allergen, a bad test result. In the CFIA's figures for 2025 to 2026, 57 of the 185 recall incidents were about allergens.
4. Telling the CFIA
If we decide a food should be recalled because it's a risk to health, the person conducting recalls calls the CFIA's Area Recall Coordinator immediately. For Ontario that's 416-665-5049; the other regions' numbers are on the CFIA's contact page. Have ready: what the problem is, the product, brand, size and lot codes, where it went and when, any complaints or illnesses, the quantity made and shipped, the labels, and our after-hours contact. This article walks through the call.
5. Finding every affected lot
Every case and bag carries a lot code (ours is the day and the oven line, like 20261116L2; here's how the CFIA
suggests choosing one). Batch records list the supplier lot of every flour, seed
and dairy ingredient. Every invoice lists the lots shipped. From one lot code or one supplier lot, we can produce: the
finished lots affected, how many were made, how many are still here and where, and every customer who received them
with quantities and dates.
6. Holding what's still here
Locate it, count it by location, tag it "RECALLED, DO NOT SHIP" and move it apart from everything else. Record the counts. They're the first number in the effectiveness check later.
7. The distribution list
One list per food and lot code, with each customer's name, address, contact person, phone, email, what kind of customer they are (distributor, grocer, café, or a hospital, care home or daycare, which the CFIA asks you to flag), and the quantity of each lot they received. Send it to the CFIA as soon as it's ready.
A useful check from the CFIA's guide: add what customers received to what's still on your shelves. If the total is less than what you made, somebody is missing from the list.
8. The notice of recall
Every customer on the list gets a phone call and a written notice the same day. The CFIA publishes a notice of recall template and asks to review your draft before it goes out. Ask each customer to confirm they got it and what they did with the product.
9. Checking that it worked
For each customer, record the date and how you contacted them, who you spoke to, what they did (returned, destroyed, told their own customers), and how much of each lot they had. That record is the "information that substantiates its effectiveness" that section 84(4) asks for. More on recall effectiveness checks.
10. Returns, disposal and what we change
Keep returned product apart and counted. Decide with the CFIA what happens to it (destroy, relabel, return to the supplier) and record it. Find the cause and write down what changed. After every recall and every simulation, the person responsible for the procedure updates this document and dates the revision.
Where this stops working
The document is the easy part. Steps 5, 7 and 9 are where a paper procedure meets the real business, and they're where it breaks. The trace lives in three places: batch sheets on a clipboard, an invoice program, a spreadsheet of customers that somebody updates when they remember. At 4 p.m. on a Friday, with the CFIA on the phone, you're reconciling those by hand, and the "every customer who received it" in step 7 is only as good as the last time the spreadsheet was touched.
The other thing that drifts is the names. The production manager in section 1 left in the spring; the after-hours number is his old cell. An inspector who calls it will notice.
How TaroStack does it
TaroStack is where the procedure and the recall live together, so the document describes what the software really does, and the trace is already there when you need it.
The two people section 84(1) asks for are named in TaroStack's settings, with their backups, and they're printed on every recall report and simulation record. When someone leaves, you change the name once.
Every batch you record keeps the supplier lots that went into it, so step 5 is one search: start from a lot of your bread or a supplier's lot of flour, and TaroStack shows every batch it reached, how much is still on your shelves and where, and every customer who received it, with dates and quantities.
The recall report carries what the CFIA's distribution list asks for, customers' names, addresses, contacts and quantities by lot, and the whole trace downloads as one CSV file you can send the CFIA as it is.
Starting a recall in TaroStack gives it a number and holds every affected lot still in stock, so nobody ships it by mistake.
As your team calls customers, each contact is recorded on the recall: when, how, who answered, and what they had left. That's step 9's effectiveness record, written as you go instead of reconstructed afterwards.
And the simulation the regulation asks for every 12 months is a timed drill in TaroStack, recorded with its result.
TaroStack reminds you before the 12 months are up.
| By hand | In TaroStack | |
|---|---|---|
| Finding every affected lot | Batch sheets, invoices and a spreadsheet, reconciled under pressure | One search from any lot, yours or a supplier's |
| The distribution list | Typed up from invoices | On the recall report, with addresses and quantities by lot |
| Proof it worked | Notes from the phone calls, gathered later | Each contact recorded on the recall as it happens |
| The two named people | A page that goes out of date | Kept in settings and printed on every report |
| The yearly simulation | Easy to forget | A timed drill, with a reminder before 12 months pass |
Lots, recalls and drills are on every TaroStack plan, from $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, and you can bring your customer and supplier lists as spreadsheets. If you'd like a hand setting it up, ask, and we'll do it with you.
TaroStack keeps the records the procedure depends on. Writing the procedure, and deciding to recall, stay with you.
