When the CFIA asks for your traceability records, section 91 of the Safe Food for Canadians Regulations gives you 24 hours from the moment you get the request. It can be less if the CFIA thinks there's a risk to health, or more if the records aren't needed for a recall. If you send them electronically, they have to be "a single file and in plain text that is capable of being imported into and manipulated by standard commercial software." In practice, that's one CSV file.
The short version
- The clock starts when you receive the request, not on the next business day.
- They can ask for any part of your traceability records, usually one product or lot.
- Answer with one step back (who supplied it, with addresses and dates) and one step forward (who you provided it to).
- Send one CSV file. Not photos, not three spreadsheets, and nothing password-protected.
- If you can't make the deadline, call before it runs out, not after.
- The time to find out whether you can do it in 24 hours is a drill, not the real request. TaroStack times one for you.
What the regulation says
Section 91(1) says anyone who receives a request from the Minister for a document referred to in section 90, "or any part of such a document", must provide it:
- within 24 hours after receiving the request, or within a shorter period the Minister sets if they believe it's needed to identify or respond to a risk to human health, or a longer one if they believe the document isn't needed for a recall; and
- if provided electronically, "in a single file and in plain text that is capable of being imported into and manipulated by standard commercial software."
Section 91(2) defines plain text as "data that is not encrypted and whose semantic content is available." In other words, the CFIA has to be able to open the file and read the data in it as data.
The regulation names the Minister; the request itself comes from the CFIA. Section 90 is the list of what you keep: the food, its lot code, who made it, who you provided it to and who provided it to you, with names, addresses and dates. Here's that list in plain words.
This is general information, not legal advice. Your CFIA inspector has the last word on what applies to you.
What counts as one plain-text file
| What you send | Does it fit section 91(1)(b)? |
|---|---|
| One CSV file | Yes. It's plain text, and every spreadsheet program opens it. |
| One plain text file with a column layout | Yes, though a CSV is easier to sort. |
| An Excel workbook with one tab per record type | Not plainly. It's several tables, and an .xlsx file isn't plain text. |
| Three separate spreadsheets | No. That's three files. |
| Photos or a scanned PDF of batch sheets | No. The words are a picture, not data. |
| A password-protected file | No. Plain text is data that isn't encrypted. |
The workbook row is my reading, not a CFIA ruling. The rule doesn't apply to paper: if you hand over paper records, the single-file requirement is about electronic ones. But paper can be slow to gather and slow for the CFIA to use, so I'd still send a CSV when you can.
How to answer it in 24 hours
- Write down exactly what was asked, and when the request arrived. Note the product, lot codes, date range and who asked. The deadline is that time plus 24 hours, or whatever shorter time they gave you.
- Trace one step back. List every delivery of the ingredients that went into the lots in question: the supplier's name and address, the date received, and the supplier's lot if you have it.
- Trace one step forward. List every customer who received those lots: name, address, the date, and how much of each lot.
- Put it in one table, one row per movement, with the same columns all the way down. If a lot was made from an ingredient lot, say so on the row.
- Save it as CSV and open the CSV to check it. A spreadsheet can drop a lot code's leading zeros, or turn a code that looks like a date into one.
- Send it to the person who asked, and keep a copy of exactly what you sent and when.
If something is missing, send what you have on time and say plainly what's missing and when you'll have it. In my view that's better than a complete answer a day late.
What the file looks like
Here are the first rows and columns of a bakery's answer about rye flour lot R4471, from the example in our SFCR
traceability template, whose Records tab saves as this file:
Date,Record,Food,Lot code,Quantity,Unit,From or to,Their address,Made into lot
2026-11-09,Received,Rye flour,R4471,40,bag (20 kg),Flour mill,"[street], [city], ON [postal code]",
2026-11-10,Used,Rye flour,R4471,6,bag (20 kg),,,20261110L2
2026-11-10,Shipped,Dark rye bread,20261110L2,120,loaf,Grocer A,"[street], Ottawa, ON [postal code]",
2026-11-10,Shipped,Dark rye bread,20261110L2,60,loaf,Café B,"[street], Gatineau, QC [postal code]",
One table, one row per movement, addresses in the rows. Anyone at the CFIA can sort it by date, filter it to one customer, or match it against another business's file.
Where this stops working
The 24 hours sound generous until you count what goes into them. The request arrives on a Friday afternoon, or the person who keeps the records is on holiday. The deliveries are in the invoice program, the batches are on clipboards, and the customers are in a spreadsheet one person updates. Every step above is an afternoon of matching codes that were typed three different ways.
The other risk is not knowing. A business that has never done it doesn't know whether it takes two hours or two days, and finds out with the CFIA waiting. That's what a timed mock recall is for.
How TaroStack does it
In TaroStack, the answer to a records request is a trace you've already been keeping.
Deliveries are recorded with the supplier's lot, scanned from a GS1-128 case label or typed in. Batches record which ingredient lots went into them, first-expired-first-out by default. Shipments record which lots went to which customer. So when the CFIA names a lot, yours or a supplier's, the trace opens straight from it. You see every delivery of it, every batch it went into, what's 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 the lot with its own date.
It downloads as one CSV file, for one lot or several, so the answer to section 91 is one download.
Nothing is deleted, so the two years section 90 asks you to keep records for take care of themselves. To find out how long a real request would take you, run a traceability drill: TaroStack times it from start to finish and keeps the record.
| Records in three places | TaroStack | |
|---|---|---|
| One step back | Invoices and batch sheets, matched by hand | Recorded at receiving and on each batch |
| One step forward | Invoices, matched to batches | Recorded when the order ships |
| One plain-text file | Pasted together under the deadline | One CSV download |
| Knowing how long it takes | Found out on the day | A timed drill, on record |
Lots, recalls and timed drills are on every TaroStack plan, from $9.99 a month. It's free for 14 days, and you can import your suppliers, customers and items from spreadsheets. If you'd like a hand setting up, ask, and we'll do it with you.
