Food recall planning software for mock

01Current scope

Start with the recall records you can maintain every week.

HACCPlan's launch recall value is planning and evidence: write the recall procedure, keep contact lists and lot records organized, run a mock recall, document gaps, and print the packet. It should not be marketed as a live customer notifier, regulator submission engine, press-release publisher, or full recall command center until those workflows exist.

What is available now:

• Recall procedure drafting. Build a written plan around roles, decision steps, customer notification responsibilities, regulator contact notes, effectiveness checks, and product disposition.
• Contact-list organization. Keep recall coordinator, alternates, customer, supplier, and service-provider contact information with the workspace.
• Lot traceability records. Use receiving, batch, and shipping records to support one-up / one-back tracing.
• Mock recall evidence. Pick a recent lot, trace it, document the time, note gaps, and save or print the result.
• Deviation and CAPA links. Connect recall-readiness gaps to corrective actions.
• Inspection binder output. Produce the procedure, recent records, mock recall result, and supporting documents for review.

Coming soon:

• Mock recall scheduler. Automatic annual or quarterly reminders, randomized trigger lots, and recurring evidence packets.
• Customer notification automation. Email/SMS/fax delivery, acknowledgements, and consignee status tracking.
• Regulator workflow support. FDA, CFIA, and FSIS contact routing, Reportable Food Registry pre-fill, and recall termination package assembly.
• AI press-release drafts. Useful, but must remain human-reviewed and should not be described as live until implemented.
• Live recall execution dashboard. Hold/release status, mass balance, recovered product, disposal, and effectiveness checks.
• FSMA 204 export coupling. Full KDE/CTE recall traces depend on the FSMA 204 module and sortable export work shipping first.

02The rule

What the recall plan has to cover.

FDA-regulated facilities that need a food safety plan generally need recall procedures under 21 CFR 117.139. Canadian SFCR operators need recall procedures and traceability records. Meat and poultry operators have FSIS-specific recall rules. The details differ, but the practical questions are stable:

1. 01

   Who decides and who acts?

   Name the recall coordinator, alternates, internal team, and outside support contacts.

2. 02

   Which lots are affected?

   Trace the implicated lot backward to inputs and forward to customers.

3. 03

   Who must be notified?

   Identify customers, suppliers, regulators, and service providers that need contact.

4. 04

   What happened to the product?

   Document hold, return, destruction, rework, correction, or other disposition.

5. 05

   How do you know the recall worked?

   Keep effectiveness-check evidence and a final corrective-action record.

03Launch fit

Where HACCPlan fits today.

HACCPlan fits small food businesses that need a recall plan and mock recall discipline but are not ready for an enterprise recall command center. It helps turn scattered invoices, supplier records, batch sheets, and shipping notes into a traceable packet.

It is not the right tool today if you need live regulator submission, automated customer notifications, legal-reviewed public warning distribution, real-time inventory holds, or mass-balance dashboards.

04Start

Run one mock recall before you need a real one.

1. 01

   Choose a recent lot

   Pick a real ingredient, batch, or finished lot from the last 30 to 90 days.

2. 02

   Trace backward

   Confirm supplier, supplier lot, receiving date, quantity, reference document, and related COA or certificate.

3. 03

   Trace forward

   Confirm finished batches, customers, shipments, dates, quantities, and carrier or invoice references.

4. 04

   Document the gaps

   Missing phone numbers, stale contacts, missing supplier lots, and incomplete customer records become CAPA tasks.

Start free

Draft your recall plan and run a mock trace

Use HACCPlan for recall procedure drafting, contact records, lot traceability, mock recall evidence, deviation/CAPA links, and inspection binder output. Notification automation and live recall execution workflows are coming soon.

Email required to save your workspace. No credit card.

Footnotes

1.21 CFR 117.139 - Recall plan - law.cornell.edu

2.21 CFR Part 7 - Recalls - law.cornell.edu

3.CFIA Recall Procedure Guide - inspection.canada.ca

4.FSIS Directive 8080.1 Rev. 8 - Recall procedure - fsis.usda.gov

Andrew Langevin·CFIA-licensed facility, Brantford ON· Published 2026-06-04· 7 min read· Wikidata Q139112497