The Lot Code Was on the Case. You Threw the Case Away.

Traceability programs break in two specific places, and neither one shows up in a recall plan. The first is the moment somebody opens a master case. The second is the moment an ingredient passes through a repacker. A mock recall that clears finished goods in an afternoon will still stall for days at those two seams, because the lot code the trace depends on stopped existing before the ingredient reached the line.

The lot code lives on the case, not on the product

For most produce, most dry ingredients, and most packaging, the lot identity exists in exactly one place: printed or labeled on the master case.

The units inside carry a UPC and sometimes a best-by date. A UPC identifies a product, not a lot. A best-by date narrows things to a few days of packing on a good day and to a month on a bad one. Neither one gets a recall down to the shipment that matters.

Sometimes the code was never there at all. In the 2026 Salmonella Javiana outbreak tied to fresh jalapeños, which reached 431 illnesses across 32 states with 57 hospitalizations as of FDA's August 21 update, Coast Citrus Distributors recalled bulk cases and told FDA in the enforcement record: "No lot code information. Recall is for all product with a pack date of 07/01/2026 through 07/31/2026."

That recall covered 53,760 cases. A month of pack dates, because a month was the smallest unit anybody could define.

That is the upstream version of the problem. The downstream version is the one you control, and it is worse, because the code existed and then got destroyed.

Seam one: the case gets opened

The chain breaks the first time a master case is opened and the product moves into a different container.

Receiving does its job. Supplier, PO, quantity, receipt date, and the lot code copied off the case label. That record is clean.

Then the case goes to the line and gets opened. Product moves into a tote, a lug, a hopper, a staging rack, a walk-in bin. The new container carries nothing.

The case gets flattened and goes in the baler at the end of shift. From that point forward, your storage record is a record of an unlabeled container.

Partial cases are the sharpest version. Half the case runs Tuesday, the rest sits in the cooler until Thursday, and by Thursday the cardboard is gone.

Commingling makes it worse. Two cases from two different receipts go into one tote, and every unit that leaves that tote now points at two lots. Forward trace doubles on the first step.

The batch record still has a box for ingredient lot, and somebody still writes something in it. What nobody asks is where that number came from and whether it can still be checked against anything.

This seam closes on the floor. One rule covers it: the case label does not get destroyed until its code is written onto whatever the product moves into.

A lot ticket zip-tied to the tote handle. A grease pencil on the lid. The panel cut off the case and taped to the container. Pick whatever survives a wash-down and make it the only accepted method. Partial cases get tagged before the case is broken down, and no container holds two lots unless the tag names both.

Seam two: the identity changes hands at the repacker

At repacking the lot code may survive, but the traceability lot code source changes to the repacking location, and the record that ties the two together stays in the repacker's building.

FSMA 204 defines a traceability lot code as "a descriptor, often alphanumeric, used to uniquely identify a traceability lot within the records of the firm that assigned the traceability lot code." The definition names the firm on purpose. The code means something inside that firm's records and nowhere else.

FDA's own Q&A is specific about what happens next. A new traceability lot code will usually need to be assigned to repacked product. It can be retained instead when the food stays inside the same traceability lot, what FDA calls repacking "like into like," but even then the traceability lot code source changes to reflect the place where the repacking occurred. Either way the repacker keeps the key data elements under 21 CFR 1.1350 for the listed food going in and the food coming out.

Those KDEs are the join between the code on your receipt and the code their supplier used. They live in their building, not yours.

The 2026 jalapeño recalls show both halves of the problem inside one outbreak. Coast Citrus, the distributor FDA's traceback pointed at, initiated its recall on July 22 with no lot code and a month-wide pack-date range.

Two weeks later, on August 5, repackers pulling jalapeños recalled under numbering of their own. Sirna & Sons Produce listed lot numbers 60947409 and 60991812 on product "repackaged into 1 lb. plastic bags," citing Salmonella Javiana by name. Dairyland Produce listed seven codes beginning with X27 on bags repacked from bulk.

Those codes resolve inside Sirna's and Dairyland's records and nowhere else. A buyer holding Dairyland lot X2744163 cannot answer "is this from the grower FDA named" out of their own files. Somebody at Dairyland has to pull a receiving record first, and if that trail runs back to a bulk distributor whose own recall carried no lot code, the chain ends there no matter how fast anyone moves.

One-up one-down isn't a gap in the rule. It's the design. It works when every firm in the chain holds its own records and answers fast, and it stops working the moment your one link up is a repacker and the question is two links up. That is the same mechanism behind the supplier-of-supplier recall cascade, arriving through a different door.

So ask before you need the answer. For every repacker, distributor, and broker in your supplier records: if I give you your lot code, how long does it take you to give me your supplier's lot code and the name behind it?

Write what they say in the supplier file next to the GFSI certificate. A day is workable. A week means your backward trace ends at their dock, and you want to know that now rather than during a recall.

At the finished-goods end, the identity becomes a date

Once an ingredient is inside a finished product, the identifier that reaches the customer is usually a date range, not a lot.

WFM Purchasing recalled ten prepared items made with the recalled jalapeños: guacamoles, salsas, pico de gallo, a trio dip. The FDA enforcement records identify each product by a PLU code under the bar code and a best-before window. Eight of the ten read 8/7/2026 through 8/12/2026. The other two read 8/9 through 8/14. Each record lists the same quantity, 12,995 units total.

FSIS issued a public health alert covering meat and poultry products made with the recalled peppers. Food Safety News reported the alert on August 8, 2026, covering 18 products whose "use by dates up to and including Aug. 15" were the identifier consumers were given.

Neither identifier points back at a pepper case. When the identity of the finished good is a date window, the recall is a date window, and everything made inside it goes whether or not it ever touched the implicated lot. The difference between recalling one day of production and recalling two weeks is the difference between a lot code that survived the case and one that didn't.

Why a mock recall doesn't find either seam

Mock recalls start from a finished-goods lot and work backward through the records that exist. Both seams are places where the record never existed.

The usual drill runs like this. Pick a finished lot. Pull the batch sheet. Read the ingredient lot off the batch sheet. Pull the matching receiving record.

Three hours, everybody signs, the file goes in the audit folder. Nothing in that sequence tests whether the number on the batch sheet is the number that was on the case, or whether anyone could still prove it. A number in the box passes the mock, because the mock is checking for completeness and not for whether the identifier resolves to anything upstream.

A facility can hit the 24-hour clock and still hand FDA a backward trace that dead-ends at a repacker's loading dock. Getting fast at the supplier recall stress test does not close either seam, because both of them sit upstream of the records you are moving quickly through.

If your mock recall has never started at a case on the receiving dock and run forward, the part that breaks has never been tested.

The drill to run this week

Pick one incoming ingredient and follow it forward, physically, from the receiving dock to a finished-goods lot. One ingredient, one afternoon.

1. Pick something on the Food Traceability List that you received in the last 30 days. Fresh peppers, leafy greens, fresh-cut produce, melons, fresh herbs, a soft cheese, a nut butter, shell eggs.

2. Photograph a case label at receiving. Write down every identifier printed on it: lot code, pack date, UPC, best-by, the grower or packer code, the PO number. That list is the maximum identity this ingredient will ever have.

3. Find where the case gets opened. Watch it happen, or ask the person who does it. Note what the product goes into and what identifier travels with it. If the answer is nothing, that's seam one and you just watched it happen.

4. Ask when the case gets broken down. If the cardboard goes in the baler at the end of shift, your lot code has a shelf life measured in hours.

5. Pull the batch record that consumed it. Compare the number in the ingredient-lot box to the number on the case label. If they don't match, or the box holds a receiving line number instead, the batch record can't take you upstream.

6. Call the supplier of that ingredient and ask the one question: if I give you your lot code, how fast can you give me your supplier's lot code and the name behind it?

Step six decides the outcome. A same-day answer means the chain holds through the handoff. Anything longer means your backward trace stops at their dock, and the peppers or the seasoning behind them stay anonymous until FDA names them.

Run steps two through five on a second ingredient next month. Two afternoons gives you an honest map of where your traceability actually ends.

The 2028 date doesn't close either seam

Two separate things pushed FSMA 204 to 2028, and it helps to keep them straight. Congress directed FDA not to enforce the Food Traceability Rule before July 20, 2028. FDA separately proposed extending the compliance date by 30 months to that same date.

Neither instrument changed a requirement, which is the part worth planning around. Neither seam is going to close on its own between now and then. Both are habits, and habits change on the floor, not on a purchase order.

That part is on you. The case is the only thing carrying the identity, and the case gets opened and thrown away in the ordinary course of running a line. Somebody has to write the number down before the cardboard goes in the baler.

What a system can do is make the number go somewhere it survives. Beacon creates the lot at receiving and holds the case lot code on that record, keeps the parent link when the lot is split into the containers that go to the line, and carries the genealogy through production, so a finished lot resolves back to the case in both directions. It won't invent a code that was never printed on the case.

Run the drill first. If it comes back clean on both ingredients, you don't need anything. If it stalls at either seam, book a call and I'll walk your receiving flow with you.