Skip to content

SFCR Traceability Template: One Up, One Down, in One File

A free SFCR traceability template with a row for every lot received, used and shipped, a trace tab, and one CSV file for the CFIA's request.

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 · 9 min read

Whether you call it a traceability matrix, a one up, one down log or a record template, what the Safe Food for Canadians Regulations ask for is the same: a record of every time a lot of food moves. You need one when it's received from a supplier and one when it's provided to a customer, each with the food's name, its lot code, the date, and the name and address of the business on the other side. That's section 90(1). This template keeps it all on one tab, so it saves as the single plain-text file section 91 asks for.

Download the SFCR traceability template. It's an Excel file that opens in Google Sheets, LibreOffice and Numbers, with no macros and no sign-up.

The short version

  • One row for every movement of a lot: Received, Used (in one of your batches) or Shipped.
  • Type each supplier and customer once on the Businesses tab, address included. Every row fills it in.
  • Used rows aren't in the regulation, but they're the ones that let you narrow a recall.
  • The Trace tab takes any lot code, yours or a supplier's, and marks every row it reaches.
  • When the CFIA asks, save the Records tab as CSV. That's the whole answer, in one file.
  • When the Used rows start falling behind, TaroStack writes them for you. More at the end.

What each column is for

Column What goes in it Why
Date The day it was received, used or provided 90(1)(b), (c) and (d)
Record Received, Used or Shipped Sorts and filters the tab
Food (common name) The name on the label or invoice 90(1)(a) and (d)
Lot code The supplier's lot on Received rows, the ingredient's lot on Used rows, yours on Shipped rows 90(1)(a)
Quantity and Unit How much Not required, but you can't check a recall without it
From or to The supplier on Received rows, the customer on Shipped rows 90(1)(b), (c) and (d)
Their address Filled in from the Businesses tab 90(1)(b), (c) and (d)
Made into lot On Used rows, the lot of yours it went into The link between one step back and one step forward
Made or labelled by, and its address On Shipped rows, your business for your own food 90(1)(a)
Document The invoice, packing slip or batch sheet Where to look when a row is questioned
On the trace? Marked by the Trace tab

Your own address is your "principal place of business", in the regulation's words: the address you'd give the CFIA. If you resell something another business made or labelled, name that business in the Made or labelled by column, as section 90(1)(a) asks.

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

Why it's one tab

Section 91 gives you 24 hours to hand your traceability records to the CFIA when they ask. If you send them electronically, they must be "a single file and in plain text that is capable of being imported into and manipulated by standard commercial software." A CSV file is plain text, and every spreadsheet program opens it.

A workbook with a tab for receiving, another for production and a third for shipping can't be saved as one CSV. Excel, Google Sheets and LibreOffice all save only the tab you're on. You'd send three files, or spend part of your 24 hours pasting them together. With everything on one tab, the save is the answer. Here's the rest of that request.

That's also why addresses are typed once on Businesses and filled in on each row: the CSV carries them as text.

A week in a bakery

The example in the file is a 14-person bakery in Ontario that ships to grocers and a café in Ontario and Quebec. In the week of November 9, 2026, it got rye flour lot R4471 twice from its mill: 40 bags of 20 kg on Monday and 20 more on Friday. It made three lots with it and shipped them five times.

Date Record Food Lot code Quantity From or to Made into lot
Nov 9 Received Rye flour R4471 40 bags Flour mill
Nov 10 Used Rye flour R4471 6 bags 20261110L2
Nov 10 Shipped Dark rye bread 20261110L2 120 loaves Grocer A, Ottawa
Nov 10 Shipped Dark rye bread 20261110L2 60 loaves Café B, Gatineau
Nov 11 Used Rye flour R4471 6 bags 20261111L2
Nov 12 Used Wheat flour W-2290 8 bags 20261112L1
Nov 13 Received Rye flour R4471 20 bags Flour mill
Nov 13 Used Rye flour R4471 4 bags 20261113L3

That's eight of the fifteen rows in the file. Now say the mill calls about R4471. Type it on the Trace tab and it answers:

  • 2 deliveries received, 60 bags in all
  • 3 batches made with it, using 16 bags: two lots of dark rye and one of multigrain
  • 44 bags that should still be on the shelf, so go and count them
  • 5 shipments on the trace, 420 loaves, to three customers in two provinces

The white sandwich loaf shipped on Nov 12 isn't marked, because it was made from wheat flour lot W-2290. That's the work the Used rows do. Without them, the bakery would have to call every customer who got bread that week.

The trace works the other way too. Type 20261110L2 and it marks the flour and caraway lots that went into that batch, and the deliveries they came in on. That's the "one step back" an inspector asks you to show.

How to fill it in

  1. Fill in Businesses first, your own included, with full addresses. A row whose name isn't there says "add to Businesses".
  2. Add a Received row for every delivery, with the lot code printed on the package. If there isn't one, write the delivery date and the supplier's invoice number as the code, and put the same code on the bags.
  3. Add a Used row for every ingredient lot in every batch, on the day you make it. This is the row people skip, and it's the one that matters.
  4. Add a Shipped row for every lot that goes to each customer, and put the lot code on the invoice as well.
  5. Copy lot codes instead of retyping them. R4471 and R-4471 are two different lots to a spreadsheet. Before the first row, settle how you'll code your own lots: the CFIA's advice is short.

Where this stops working

The template is complete on the day you fill it in. It stops working on the days nobody does. Received and Shipped rows have paperwork behind them: the invoice comes with the delivery, and the invoice goes out with the order. Used rows have nothing behind them except someone remembering to type which flour went into which batch. In a busy week, that row gets filled in on Friday from memory, or not at all.

The other problem is the shelf. The Trace tab says 44 bags should be there, but nothing in the spreadsheet knows whether a bag split and was thrown out, or went to the other site. And when two people keep the file, there are soon two files that disagree. None of it shows until the mill calls, and then the 24 hours start.

How TaroStack does it

TaroStack writes these rows as you receive, make and ship, so the trace is there before anyone asks.

When a delivery comes in, you record the supplier's lot as you receive it, or scan it off a GS1-128 case label, and TaroStack keeps the supplier and the date. When you record a batch, TaroStack notes which ingredient lots went into it, first-expired-first-out by default, so the Used rows write themselves. The batch gets its own lot code and a printable lot label. When an order ships, TaroStack records which lots went to which customer.

Then any lot, yours or a supplier's, opens a trace. You see every delivery of it, every batch it went into, how much is still on your shelves and where, and every customer who received it, with dates and quantities. The shelf figure is TaroStack's own stock count, which moves with every delivery, batch, shipment and write-off, so the 44 bags are a number you can check, not a subtraction.

The trace report carries the names and addresses section 90 asks for: yours, your customers' and your suppliers'.

It downloads as one CSV file, for one lot or several, so the CFIA's request is one download.

And to find out whether you'd make the 24 hours, run a timed drill. TaroStack records how long the trace took and what it found.

This template TaroStack
Which ingredient lots went into a batch A Used row, typed by hand Recorded with the batch
Who received a lot Shipped rows, typed from invoices Recorded when the order ships
What's still on the shelf Received minus used Counted stock, by place
The CFIA's request Save the Records tab as CSV One CSV file from the trace

Lots, recalls and traceability 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, this one included. If you'd like a hand setting up, ask, and we'll do it with you.

Questions people also ask

What is a traceability matrix?

A traceability matrix is a table that links what came in to what went out: which supplier lots went into which of your lots, and which customers got them. In this template that's the Used rows. The SFCR doesn't use the word. It lists the records, and the matrix is one way to keep them.

Does the SFCR require a specific template?

No. Section 90 says what to record, and section 91 says how fast to hand it over and, if you send it electronically, in what form: one plain-text file. Any layout that does both works, including paper records you don't send electronically.

Do I have to record my supplier's lot code?

The regulation asks for the ingredient's name, the supplier's name and address, and the date you received it, not the supplier's lot. But without the lot, a supplier's recall reaches every batch you made since the delivery. Tracking ingredients by lot shows how little extra it takes.

What do retailers have to keep?

Retailers keep sections 90(1)(a), (c) and (d): what the food is, and one step back. In this template that's the Received rows and the Businesses tab. They don't record each shopper, and restaurants are left out of these requirements altogether.

How long do I keep traceability records in Canada?

Two years after the day you provided the food (for retailers, two years after the day it was sold), somewhere they can be reached from Canada. The SFCR's traceability requirements cover the rest.

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 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.