Selling to the US? Why SFCR Traceability Isn't Enough for FSMA 204

Selling to the US? Why SFCR Traceability Isn't Enough for FSMA 204

Canadian food businesses selling into the US cannot assume that meeting SFCR traceability requirements also satisfies FSMA 204. For covered foods and activities, the US rule adds specific event records, data-sharing duties and traceability lot code requirements. This NutraSoft overview explains the gaps and gives owners, QA managers and operations teams a practical preparation plan. (inspection.canada.ca)

What does FSMA 204 require from Canadian food manufacturers?

FSMA 204 refers to the US FDA’s Food Traceability Rule under Section 204 of the Food Safety Modernization Act, finalized in November 2022. It requires additional records for businesses that manufacture, process, pack or hold covered foods intended for the US market. Canadian operations can be subject to these requirements before the food crosses the border. (fda.gov)

The rule centres on Critical Tracking Events, or CTEs, and the Key Data Elements, or KDEs, associated with each event. Think of CTEs as activities such as receiving, transformation and shipping. KDEs are the required details that explain what happened to each traceability lot. (fda.gov)

Start with the Food Traceability List

Not every food exported to the US falls under this rule. Coverage depends on the Food Traceability List, the activities performed and any applicable exemptions. Listed categories include nut butters, fresh-cut fruits and vegetables, and certain cheeses and seafood products. (fda.gov)

Multi-ingredient products also need attention. A product containing a listed ingredient may be covered when that ingredient remains in the form described on the list. Do not make the decision from the finished product’s name alone; check ingredients, processing conditions and exemptions against FDA guidance. (fda.gov)

Build a coverage register for your US-bound products. Include the reason each product is covered or excluded, the supporting guidance and who reviewed the decision. Revisit it when recipes, suppliers or processing methods change.

SFCR provides a foundation, not an automatic match

The Safe Food for Canadians Regulations require applicable businesses to trace food back to the immediate supplier and forward to the immediate customer. They also include food identification, document retention and record-access requirements. That foundation is valuable, but it does not automatically supply every event-specific field required by the US food traceability rule. (inspection.canada.ca)

These are practical differences, not a claim that Canadian rules lack lot codes or rapid record access. Both systems require accessible information; FSMA 204 adds a particular structure for covered supply chains. Compare the required fields, not just whether your business can complete a recall exercise. (inspection.canada.ca)

For teams reviewing food traceability in Canada, the useful question is specific: can existing records provide every required US data element, linked to the correct lot? A supplier invoice and customer shipment record may be a starting point. Test whether the connections between them are complete.

Where everyday lot tracking needs closer attention

A traceability lot code, or TLC, identifies a traceability lot within the records of the business that assigned it. FDA specifies when codes are assigned, including initial packing of certain commodities, first land-based receiving of seafood and transformation. Simply shipping a covered food is not a reason to replace its TLC. (fda.gov)

A distributor may use an internal warehouse code, but that does not replace the original TLC that must move forward. Keep the relationship between those identifiers clear. Otherwise, your team could retrieve an internal number without the supplier’s required identifier. (fda.gov)

Use a sample order to examine three handoffs:

• Receiving: Check whether supplier documents contain the applicable receiving KDEs, including the TLC and source information.

• Transformation: Where applicable, check whether input lots connect to the output lot and its required transformation records.

• Shipping: Confirm that the required shipping KDEs reach the next recipient and remain linked to the shipment. (fda.gov)

Do this with an actual workflow, not an empty template. Include partial pallets, split shipments and a product made from multiple ingredient lots. The goal is to find missing connections before a customer or regulator needs the records.

Why is the 2028 FSMA 204 timeline closer than it seems?

July 20, 2028 is the key preparation horizon, but customer deadlines and implementation work can arrive sooner. FDA proposed moving the original January 20, 2026 compliance date to July 20, 2028. Congress subsequently directed FDA not to enforce the rule before that date, and FDA says it will follow that direction. (fda.gov)

That distinction matters: FDA’s current overview describes a proposed compliance-date extension alongside a statutory enforcement delay. The extension proposal does not change the rule’s substantive requirements. Treat the extra time as preparation time, not as evidence that the required records have disappeared. (fda.gov)

Some major US retailers and distributors already set FSMA 204-related supplier requirements through purchasing programmes and supplier terms. These can create earlier commercial deadlines than 2028. Check each customer’s current contract, onboarding instructions and data specifications rather than assuming the federal timeline controls every delivery. (wegmans.com)

Allow time for systems, partners and staff

Plan the work in stages: agree on required fields, update systems, test customer data exchanges and train employees. Include receiving, production, QA and shipping staff rather than assigning the whole project to one manager. Each team should understand which information it captures and what to do when something is missing.

Schedule a pilot before expanding across all products. Give suppliers time to correct incomplete records and employees time to practise exception handling. A working process on a busy shift is a better milestone than a completed software installation.

A five-step FSMA 204 preparation checklist

Use this checklist to turn the requirements into assigned work. Give every step an owner, a target date and a clear completion test. Keep coverage decisions separate from software decisions so the system follows your actual obligations.

• [ ] Confirm scope: Review US-bound foods, ingredients, activities and exemptions using official FDA resources.

• [ ] Map events and fields: List applicable CTEs and identify every KDE your team must retain or share.

• [ ] Check trading partners: Confirm supplier data availability, customer formats and contractual deadlines.

• [ ] Update procedures and train staff: Document lot-code handling, record locations, responsibilities and missing-data escalation.

• [ ] Run a timed retrieval test: Assemble the required records and test a sortable spreadsheet export for a representative lot.

Base the exercise on the requirements that apply to your business, including its written traceability plan. FDA provides resources explaining event records, plans and requested spreadsheet submissions. Use those resources to assess the result, not just whether your team found an invoice. (fda.gov)

How NutraSoft helps organise lot records

NutraSoft connects supplier lots, production batches and customer shipments within its traceability workflow. Its platform records core lot information at receiving, transformation and shipping, with traceability exports available in PDF or Excel. These capabilities can support record organisation, but they should be assessed against your specific KDE requirements. (nutrasoft.ca) 

When evaluating lot traceability software, bring your own sample ingredients, products and shipment documents. Ask the team to demonstrate supplier-to-finished-product connections, missing-field handling and the export you would actually submit. Review the output with QA rather than assuming that an Excel file automatically meets every requirement.

The practical takeaway: build on your SFCR foundation, then verify the additional FSMA 204 requirements field by field. Start with one representative product and a timed record-retrieval exercise. Software helps keep records organised, but your business remains responsible for compliance; consult official FDA guidance when confirming your obligations. (fda.gov)

Ready to bridge the gap between SFCR and FSMA 204? 

While your Canadian traceability foundation is a critical starting point, meeting US export requirements demands complete visibility across every Critical Tracking Event and Key Data Element. Don't wait for an unexpected FDA request or a strict buyer audit to discover missing connections between your ingredient lots and finished goods. By testing your actual production, transformation, and shipping workflows within a modern food ERP, you can eliminate compliance guesswork and protect your US market access before commercial deadlines arrive. NutraSoft connects your supplier-to-customer lot records into seamless, audit-ready exports, giving your QA and operations teams total confidence in your data integrity.

In conclusion, preparing for FSMA 204 isn't just about passing an inspection, it is about building a resilient, transparent supply chain that gives your US buyers complete peace of mind. Taking a proactive, field-by-field approach today ensures your Canadian food business remains competitive, compliant, and ready to scale across the border without interruption. Start your free NutraSoft trial or schedule a personalized walkthrough with your own product data to see how easily you can bridge the compliance gap.