Skip to content

CanadaGAP Mock Recall: What the Auditor Checks

What the CanadaGAP audit checks for traceability and the yearly mock recall, how that lines up with the SFCR, and a grower's mock recall worked through.

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

In the CanadaGAP audit, version 11.0 for 2026, the mock recall is part of question T4. It's worth 6 points: a mock recall performed once a year, on the current season's product. Another 4 points go to an up-to-date recall program, with every supplier and customer and their contact details, and a recall team. The checklist says the mock recall "must test the effectiveness of the operation's entire traceability system", which question S1 checks separately: can product be traced one step up and one step down? Below is what each question looks for, how it lines up with the SFCR, and a grower's mock recall worked through.

The short version

  • T4 is 10 points: 4 for the recall program, 6 for a yearly mock recall on this season's product.
  • S1 is 10 points: one step up and one step down, through your records.
  • The mock recall has to test the whole traceability system, not one record.
  • If your produce leaves the province or the country, the SFCR asks for much the same, every 12 months.
  • Run the mock recall at the same point each season, and both are met.
  • TaroStack times and saves each traceability drill. More at the end.

This is general information, not legal advice. Your CanadaGAP auditor and your CFIA inspector have the last word on what applies to you.

What the auditor checks

Question Points What the checklist looks for
S1, traceability 10 Product traced one step up and one step down through your records; incoming and outgoing product recorded
T4, recall program 4 A list of every product supplier and customer with contact information; a recall team; the program written down
T4, mock recall 6 Once a year, on the current season's product, testing the whole traceability system, documented
T1, deviations and complaints 2 Records of major deviations and complaints

For S1, the auditor checks that the same information carries through from one set of your records to the next, and that incoming and outgoing product is recorded. If another operation labels your product, the auditor looks for that operation's written confirmation that it labels product as soon as it arrives.

For T4, the checklist points to two appendices of CanadaGAP's manual: a recall program (Appendix S) and an example of how to conduct a mock recall (Appendix R).

How it lines up with the SFCR

The Safe Food for Canadians Regulations count anyone who grows or harvests fresh fruits or vegetables as an operator (section 45). If your produce is sent to another province or exported, the recall and traceability sections apply to you as well as to licence holders:

CanadaGAP, version 11.0 SFCR
Tracing S1: one step up, one step down Section 90: who supplied it and who you provided it to, with names, addresses and dates
Recall program T4: suppliers, customers, contacts, a recall team Section 84(1): a written procedure naming a person responsible for it and a person responsible for recalls
Mock recall T4: once a year, current season's product Section 84(2): at least once every 12 months, with a written record kept two years

The two clocks differ. CanadaGAP counts seasons; the SFCR counts 12 months. A grower that ran last year's mock recall in August and this year's in October passes the CanadaGAP question and has gone 14 months under the SFCR. Pick a week in the season and keep to it. The CFIA's version, with a template, has the fields a written record needs.

A grower, worked through

A carrot grower in Ontario washes and packs its own crop, and ships to Quebec and New Brunswick. On October 20 the food safety lead picks a lot from this season at random: Pack ID C-F14-0912, carrots from field 14, packed September 12. The clock starts at 9:05.

One step up:

  1. The packing record shows 640 cases of 10 kg, from 18 bins harvested from field 14 on September 11 and 12.
  2. The field records show what was applied to field 14 this season, and when.
  3. The water test for the wash line covers September.
  4. The bag supplier's lot for the cases is on the packing record.

One step down:

Customer Province Cases Shipped
A produce distributor Quebec 300 September 13
A grocery warehouse Ontario 220 September 15
A farm market New Brunswick 80 September 18
Still in cold storage 40 Counted October 20
Total 640

Every case is accounted for. The clock stops at 10:50: 1 hour 45 minutes.

What it found: the New Brunswick invoice didn't carry the Pack ID, so the office matched it by date and case count. The corrective action is the Pack ID on every invoice, from now on. The record is signed by the food safety lead and the owner, and filed with the recall program.

Where this stops working

On a farm, the records that make up the trace are kept in different places by different people: the field book in the truck, the bin tags in the packing shed, the invoices in the office. Each is complete on its own. The mock recall is the one day a year they're joined up, and the join is where it breaks: a bin tag that didn't make it to the packing record, an invoice without the Pack ID.

How TaroStack does it

TaroStack joins the records as they're made, so the mock recall is a lookup.

Each harvest goes into stock as its own lot, such as field 14 on September 12. Each packing run is a batch that records which harvest lots and which bag lot it used, and gives the packed product its own lot code for the Pack ID. Each shipment records which lots went to which customer. Any lot opens a trace both ways, and a traceability drill starts the clock, opens that trace, and saves the start, the finish, how long it took and your notes.

The drill record carries the two people your recall procedure names, and TaroStack reminds you before 12 months pass without one. The trace report carries the names and addresses the SFCR asks for and downloads as one CSV file.

Lots and traceability drills are on every TaroStack plan, from $9.99 a month for one person; a farm where three people record packing would be on Growth, at $39. It's free for 14 days. If you'd like a hand setting up before the season's mock recall, ask, and we'll do it with you.

Questions people also ask

How often does CanadaGAP require a mock recall?

Once a year, on the current season's product. The SFCR asks for one at least every 12 months if your produce leaves the province or the country.

How many points is the CanadaGAP mock recall worth?

In version 11.0, 6 of the 10 points for question T4. The other 4 are for an up-to-date recall program.

Does a mock recall have to trace forward and back?

The checklist says it must test the whole traceability system, and question S1 checks one step up and one step down. So trace both: back to the field and its inputs, forward to every customer. Checking that each customer acted is the same check in a real recall.

Is a failed mock recall an automatic fail in the audit?

It isn't on version 11.0's list of automatic fails. It costs the points, and the problems it found go in the record with what you'll change.

Sources

  1. CanadaGAP Audit Checklist, version 11.0 (2026): sections S and T · read November 16, 2026
  2. Safe Food for Canadians Regulations, SOR/2018-108, s.45 and 46 (who Part 4 covers) · read November 16, 2026
  3. Safe Food for Canadians Regulations, SOR/2018-108, s.84 Recall procedure · read November 16, 2026
  4. Safe Food for Canadians Regulations, SOR/2018-108, Part 5 Traceability · 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.