On 25 August, Belgium confirmed 306 salmonella cases from one egg farm, its largest outbreak on record: the mandatory EU producer code let regulators recall every known batch within days, but a second henhouse on the same site kept shipping for three more months before anyone tested it

One farm, two henhouses, five months apart

Belgium requires every egg sold at retail to carry a stamped producer code under EU marketing standards for eggs, currently set out in Commission Delegated Regulation (EU) 2023/2465, which replaced the older Regulation (EC) No 589/2008 in November 2023. The code's first digit states the farming method (2 for barn eggs, as at Laerco), the next two letters give the country (BE), and the final digits identify the specific registered producer, in this case 1073, with a further suffix distinguishing production units at the same site. Laerco's eggs carried four such codes: 2-BE-1073-01, -02, -03 and -04. When Salmonella Enteritidis turned up in a dust sample from one henhouse at the end of April, FASFC and Laerco recalled eggs bearing all four codes, with best-before dates running into early June, and closed the henhouse identified as the source. That is the traceability system working as designed: a single positive test, translated into a producer code, translated into a nationwide and then multi-country recall within weeks. What the code could not do was tell inspectors whether the other three production units on the same farm also carried the bacteria. New cases kept being reported through June and July. Only when investigators went back and tested a second henhouse did they find the same strain there too, five months after the first positive result. FASFC's response this time was not a fourth code added to a list: it shut down the whole site and ordered the flock culled.

The numbers behind 25 August

One number is how many people got sick. One is how many henhouses on the same site turned out to be contaminated. The third is how many countries had to act on a recall that started with a single dust sample.

The real subject: a code that identifies the farm, not the flock’s health status

Most coverage of the outbreak read the story as a recall that came too late, or a company that was slow to act. Read against how the EU's own egg-traceability system works, it is a narrower and more specific gap. The producer code stamped on every egg is built to answer one question: which registered site, and which production unit within it, did this egg come from. It answers that question well, well enough that Belgian authorities could name all four of Laerco's codes and pull them from shelves in Belgium and eight other countries within weeks of the first positive test. It was never built to answer a second question: is this specific unit, right now, carrying the bacteria. That answer only comes from testing, and testing at Laerco's site, by the accounts given to journalists, ran henhouse by henhouse rather than across the whole farm at once. The code that shipped with every carton from the second henhouse between May and August was accurate. It correctly said the eggs came from Laerco BV, site 1073, one of its production units. It said nothing about whether that unit's flock had picked up the same infection sitting two doors down from the one already confirmed positive. A traceability system can be complete, in the sense that every unit sold carries a code that resolves to a real, identifiable source, and still leave a live safety question the code was never designed to carry.

Why it matters for brands

Eggs rarely reach a retail shelf as eggs alone. They go into mayonnaise, sauces, baked goods, pasta and prepared meals sold under private label and national brands across the same countries Laerco's eggs reached. For any food brand or retailer sourcing egg or egg-derivative ingredients from EU suppliers, the practical lesson is not that producer codes fail. It is that a code passing a validity check, does this code resolve to a real, registered, currently licensed site, is a different question from whether that site is currently clean, and a supplier-monitoring program built only to verify the first cannot catch what this outbreak shows: a single registered farm can carry a known-contaminated unit and a still-clear one under the same producer number for months at a time. Brands that buy from multi-unit sites, a single farm with several henhouses, a single packer sourcing from several farms under one umbrella code, need a way to track alerts and recall notices by producer code in near real time, not just at supplier onboarding, and to ask suppliers how testing is scoped: farm-wide, or unit by unit. The gap that let this outbreak run five months past its first recall was not a missing filing or an unregistered producer. It was the assumption that one clean recall, built on one positive test, closed the question for the rest of a multi-unit site.

Two ways to read 25 August