edi faxinating solutions

 

When the Lettuce Goes Bad: What a Cyclospora Outbreak Teaches Us About Grocery Traceability

By Steve Hatajlo

Right now, as I write this, there’s a parasite named Cyclospora working its way through the U.S. produce supply. Thousands of people have gotten sick—by some counts the worst season on record. Initially the trail has led investigators to shredded iceberg lettuce from a single supplier in central Mexico that ended up in Taco Bell locations across five states. On July 17, 2026, that supplier recalled all of its iceberg lettuce sourced from that region, eventually pulling product shipped to 27 states.

Here in Canada, as I write this, the Canadian Food Inspection Agency says there hasn’t been a reported outbreak. Good news. But here’s the part that caught my eye: at one point a test on Taylor Farms lettuce came back positive, triggered a scramble, and then turned out to be a false positive. Think about that for a second. One data point—wrong—and the whole chain lurches. This is a story I’ve been telling for thirty-five years, but usually it’s about an invoice instead of a salad.

The underlying problem is the same one I keep coming back to: the timing and accuracy of information flow. When a head of lettuce can make someone sick, the question isn’t just “is the food safe?” It’s “how fast can everyone in the chain figure out which food, from which lot, went to which store?” And that’s a data problem.

Why Traceability Matters More Than Ever in the North American Grocery Market

Traceability matters in the grocery market because when contaminated food enters the supply chain, the speed and accuracy of your recall data determines how many people get sick, how much product you destroy, and how much of your brand reputation you keep. A grocer or supplier that can pinpoint an affected lot in hours contains the damage. One that’s still digging through emails, spreadsheets, and paper a week later recalls everything, eats the cost, and erodes the trust it spent decades building.

A recall is only as fast as your worst record

When a parasite like cyclospora shows up, investigators work backward—from sick people, to a restaurant or store, to a distributor, to a grower. Every handoff in that chain is a place where the trail can go cold. If one party in the middle kept their receiving records as a stack of PDFs in someone’s inbox, the whole investigation waits on that person to go digging.

I’ve watched businesses treat that middle layer—the receiving confirmations, the ship notices, the lot codes—as paperwork. It isn’t paperwork. In an outbreak, it’s the map.

Bad data is expensive—sometimes catastrophically

I’ve talked about the 1-10-100 rule: it costs about a dollar to prevent a bad data entry, ten dollars to fix it once it’s in your system, and a hundred dollars once it’s traveled far enough to do real damage. A recall is the $100 category with the volume turned all the way up.

And that false-positive lettuce test that you see in the headlines? That’s the flip side of the same coin. Bad data doesn’t just fail to catch problems—it manufactures them. A wrong result, a mismatched lot code, a unit-of-measure error on a shipping document, and suddenly you’re pulling product that was fine, or missing product that wasn’t. Accuracy at the source isn’t a nice-to-have. In food, it’s the safety net.

Your biggest customers are already demanding it

This is the part that lands closest to home for the suppliers I work with. Long before any government deadline, the major grocers set the pace. If you sell into a big banner, you already know they don’t ask for advance ship notices and accurate lot data—they require them, and they’ll charge you back when the data’s wrong. Traceability compliance isn’t something you do for the regulator. It’s something you do to keep shipping to your largest account.

Where FSI Fits In

At FSI, we don’t grow lettuce and we don’t run the labs. But since 1991 we’ve excelled at solving the exact thing that breaks during a recall: getting clean, accurate, standardized supply chain data to move between trading partners who don’t all speak the same digital language.

We’ve been partners with major grocery retailers for over a decade, helping set up direct-to-store delivery (DSD) and distribution center (DC) EDI workflows  across every region in Canada. We know the North American grocery market from the inside out including its EDI requirements, its chargeback rules, its quirks. We’ve found that the average supplier’s chain is a patchwork of technology: some partners are using fully digital integration, some are emailing PDFs, and a few are still faxing.

Here’s how we help you build the traceability trail before you need it:

  • EDI (or API) integration. We map the transactions that carry your traceability data—the 810 invoice, the 850 PO, the 856 advance ship notice—into and out of your systems, so lot codes, quantities, locations, and dates flow automatically instead of getting rekeyed by hand.
  • Custom supplier web portals. Not every partner has EDI, and that’s fine. We’ve built browser-based portals—like the ones we run for Metro and Sobeys—that let their vendors submit clean, validated transactions with a full audit trail. When an investigator needs a record, it’s right there.
  • Document conversion services. Send FSI your PDFs, faxes, Excel files, and email attachments. We transform them into clean, validated, standardized data with a 99.95% accuracy rate so the messy formats coming from your smaller trading partners don’t become the weak link in your traceability chain.
  • Validation at the source. We catch the unit-of-measure mismatches, the wrong distribution-center codes, the missing fields—at the start of the process, using machine learning with a human in the loop. That’s the “1” in 1-10-100. Catch it there, and it never becomes the error that muddies a recall.

We put the work up front so that when someone up the chain asks “where did this lot go?”—you have an answer, and you have it fast. We can get you up and running within weeks, not months without disrupting your current workflows.

The Bottom Line

Outbreaks are going to happen. Parasites don’t read press releases, and produce comes from all over the world. What you can control is whether your piece of the supply chain is the one that answers quickly and accurately or the one everybody’s waiting on.

The businesses that succeed in times like these are those with stability and clear data points backed by seamless integration between systems.

That happens to be exactly what we do.

If you’d like us to take a look at where your traceability data might be slow, manual, or siloed—and whether we can help tighten it up before you need it—we’d be glad to talk. Because “it’s been working fine so far” is not the same as “it’ll hold when the recall notice lands.”