The CFIA publishes the procedure its inspectors follow, and for traceability, recalls and complaints it's specific. The inspector reads your recall procedure for its two named contacts, checks for a recall simulation in the last 12 months, and reviews any past recalls. They read at least a month of your complaint file. Then they go onto the floor and do it themselves: follow one ingredient through to the package, read one label, and trace one shipped product a step forward and its ingredients a step back. This checklist goes through each step and what to have ready.
It covers element 7 of the CFIA's preventive control inspection, "Traceability, control and complaints." The other elements cover the rest of your preventive controls and aren't in this article.
The short version
- Have the recall procedure ready, with both names the SFCR asks for.
- Have your last recall simulation, from the last 12 months, written up.
- Have at least a month of complaints, including the latest food safety complaint and what you did about it.
- Be able to show, on the spot, one ingredient's lot through to the finished package.
- Be able to trace one shipped product forward to the customer and back to its ingredient suppliers.
- Make sure whoever the inspector interviews knows the procedures as written.
- Practice it before they come. TaroStack keeps all of it in one place, so the practice and the visit look the same.
This is general information, not legal advice. Your CFIA inspector has the last word on what applies to you.
Traceability and recall: the documents
| What the inspector does | What to have ready |
|---|---|
| Reviews your written traceability and control (notification and recall) program | The recall procedure and your traceability records, current |
| Confirms the recall procedure names a person responsible for the procedure and a person responsible for conducting recalls | Both names, with backups (section 84(1)) |
| Confirms trace records show the common name and lot code, and one step forward and back | Who received each lot, with address and date; what went into it, with supplier names, addresses and dates |
| Confirms a recall simulation in the last 12 months, based on the recall procedure, with how it was done and its results | The latest mock recall write-up, and the one before it if you have it |
| Reviews any previous recalls | What was controlled, distributed and returned, how it was disposed of, that the CFIA was notified, and what you changed |
Two of those trip people up. The 12 months is 12 months, not a calendar year: a simulation in March 2026 and the next in May 2027 leaves a gap. And a real recall counts as one, if it's documented. The trace records are the ones in section 90.
Traceability and recall: on the floor
| What the inspector does | What it tests |
|---|---|
| Picks at least one ingredient or work in progress and confirms its identity is kept through to final packaging, including pre-mixes and rework | That a lot code follows the food through production |
| Picks at least one prepackaged product and checks its label for the common name, your business name and principal place of business, and a lot code | Section 92 |
| Picks at least one distributed product and traces it one step forward and its inputs one step back | That your records answer the question a recall asks |
| Interviews at least one person who verifies traceability and one who starts corrective actions | That the people know the procedure |
The on-site trace is the part you can't prepare on the day. Say the inspector at a bakery picks invoice 3302, dark rye
bread lot 20261110L2 to a café in Gatineau. The bakery has to show the batch record for that lot, the ingredient lots
it used (rye flour R4471, caraway C-118), the deliveries those came in on, and who else got bread from the same lot.
If that takes an afternoon of paper, the inspector will notice. Here's how to set the records
up.
Rework is worth a sentence in your procedure. If yesterday's broken loaves go into today's crumbs, the crumbs carry yesterday's lot as an ingredient, and the inspector may ask to see that.
Complaints: the documents and the floor
| What the inspector does | What to have ready |
|---|---|
| Confirms a written procedure for receiving, investigating and responding to complaints, and that it's followed | The complaints procedure |
| Reviews at least one month of the complaint file, including at least one food safety complaint since the last inspection | Every complaint, not only the serious ones |
| Confirms each complaint has its details, investigation results and actions, kept two years after the actions are done | A record per complaint |
| Checks, for at least one complaint, that the corrective action was carried out and fixed the root cause | Proof the fix happened: the recalibration, the retraining, the new check |
| Interviews at least one person who handles complaints | Someone who can describe the procedure as written |
The fourth row is the one to think about. "Retrained staff" in a complaint record invites the question "show me". Write down what changed and how you know it worked.
Practice it the week before
Do the floor part yourself, the way an inspector would:
- Pick an ingredient lot on the shelf and find the batches it went into and the packages that came out.
- Pick a finished package and read its label for the three things section 92 asks for.
- Pick an invoice from last month and trace it forward to the customer and back to the ingredient suppliers.
- Time each one. If any took more than a few minutes, find out why.
- Ask the two people the inspector is likely to interview to explain the recall and complaints procedures in their own words.
If you haven't run a recall simulation in the last 12 months, run one now. A drill you did this month is better than explaining why there isn't one.
Where this stops working
Most of this checklist is about whether the documents and the floor agree. A recall procedure that names someone who left in the spring, a trace that depends on one person's spreadsheet, a complaint record with no link to the lot: each one is a document that exists but doesn't match what happens. Paper systems drift that way because nothing connects them. The batch sheet doesn't know about the invoice, and the complaint log doesn't know about either.
How TaroStack does it
TaroStack keeps the records the inspector asks for in one place, connected by the lot, so what you show matches what happens.
Every delivery records the supplier's lot. Every batch records which ingredient lots went into it, first-expired-first-out by default, and every shipment records which lots went to which customer. So the on-site trace is one search: pick invoice 3302's lot, and TaroStack shows the ingredient lots and their deliveries, how much is still on your shelves and where, and every customer who received it.
The trace report carries the names and addresses the inspector's records check looks for.
Recall simulations are timed drills in TaroStack, saved with how long they took and what they found.
The two people your recall procedure names are kept in settings and printed on every drill and recall record, and TaroStack reminds you before 12 months pass without a drill. Past recalls keep their own record: what was held, who received it, and what came back.
Lot labels print with the item's name, your business name and address, and the lot code.
Complaints are recorded against the lot they're about, with what you checked, what you found and what you did.
| The inspector asks for | On paper | In TaroStack |
|---|---|---|
| The two recall contacts | A page that goes out of date | In settings, on every record |
| The last simulation | A write-up, if someone remembered | A timed drill, with a reminder |
| One step forward and back | Batch sheets and invoices | One trace from the lot |
| A label | The packaging | A lot label from the lot |
| A month of complaints | A log apart from the lots | Complaints on the lot |
Lots, recalls and traceability drills are on every TaroStack plan, from $9.99 a month. It's free for 14 days. If an inspection is coming and you'd like a hand setting up, ask, and we'll do it with you.
