Food traceability software for lot records, mock recall, and inspection prep.

01Current scope

Traceability that starts with the records you already need.

HACCPlan's launch traceability feature set is practical and narrow: keep supplier records, receiving records, batch records, shipping records, and mock recall evidence in one workspace. It does not currently ship full FSMA 204 seven-CTE capture, supplier KDE collection, one-click FDA/CFIA sortable exports, buyer network exports, or per-brand co-packer traceability views.

What is available now:

• Supplier records. Keep suppliers, contacts, onboarding files, certificates, COAs, and related documents together.
• Receiving records. Capture supplier lot code, internal lot code, quantity, date, temperature, reference document, and receiving notes.
• Batch linkage. Tie incoming lots to production or prep records so finished lots can trace back to inputs.
• Shipping records. Record customer, finished lot, quantity, carrier, invoice or BOL reference, shipment temperature, and release approval.
• Mock recall. Practice one-up / one-back tracing against real records and print the evidence.
• Inspection binder output. Save or print the current traceability records for an inspector, buyer, consultant, or internal review.

Coming soon:

• CSV/XLSX traceability exports. This is one of the easiest high-value launch additions and should be built before copy says "one-click export."
• FSMA 204 CTE/KDE mode. Seven event forms, required KDE prompts, TLC propagation, and missing-field checks.
• CFIA section 91 export. A Canadian one-up / one-back sortable export shaped for a 24-hour request.
• Supplier KDE portal. Structured upstream data collection, beyond the current supplier document portal.
• Buyer and per-brand views. Distributor CSV shapes and co-packer brand filtering.
• Immutable audit trail. Useful for inspections, but copy should not claim immutability until an audit-log implementation exists.

02Why it matters

A recall is a record-retrieval test.

Most small operators can explain where a product came from. The hard part is proving it quickly with records: which supplier lot arrived, which batch used it, which finished lot shipped, which customer received it, and what corrective action happened if something went wrong.

The current HACCPlan traceability workflow is built around that simple test. Pick a lot. Trace one step back to the supplier and one step forward to the customer. If the answer takes hours, the system is not ready. If the answer takes minutes and the supporting documents are attached, the operation is in better shape.

03Launch fit

Where HACCPlan fits today.

HACCPlan fits small food businesses that need a better record system but do not need a full enterprise supply-chain network: cottage-to-commercial operators, small manufacturers, restaurants, bakeries, farms with processing, importers, co-packers, and specialty producers.

It is not the right tool today if you need GS1 EPCIS event exchange, retailer network membership, real-time ERP synchronization, automated distributor exports, or an FDA-ready FSMA 204 spreadsheet this week.

04What not to claim

Keep traceability copy concrete.

Launch copy should say HACCPlan helps organize traceability records and run mock recalls. It should not say every FDA Critical Tracking Event is captured, KDEs are validated field-for-field, suppliers submit KDEs through a portal, a 24-hour sortable spreadsheet is one click away, or per-brand exports are live. Those claims should wait until the app has shipped and tested those paths.

The best immediate addition is CSV export for receiving, batch, shipping, and traceability summary records. That is much easier than full FSMA 204, and it gives inspectors, buyers, and consultants something useful right away.

05Start

Start with a mock recall.

1. 01

   Load suppliers and products

   Add supplier records, product records, and current documents.

2. 02

   Create recent receiving records

   Capture supplier lots, quantities, dates, reference documents, and temperatures.

3. 03

   Connect batches and shipments

   Link inputs to finished lots and finished lots to customers.

4. 04

   Run the trace

   Choose one lot and verify one-up / one-back evidence without reconstructing it in a spreadsheet.

Start free

Run a mock recall from real lot records

Use HACCPlan for supplier files, receiving records, batch links, shipping records, mock recall, and inspection binder output. FSMA 204 CTE/KDE workflows and sortable exports are coming soon.

Email required to save your workspace. No credit card.

Footnotes

1.FDA - FSMA Food Traceability Rule - fda.gov

2.CFIA - Traceability requirements - inspection.canada.ca

3.eCFR - 21 CFR Part 1 Subpart S - ecfr.gov

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