European food law is detailed, enforceable, and — on the specific question of pregnancy — almost entirely silent. A restaurant can be fully compliant with every EU hygiene and information regulation and still serve a pregnant guest a dish that puts her at avoidable risk.
That gap is not a loophole. It is a design feature of legislation built around population-wide averages rather than vulnerable subgroups. Understanding exactly where the legal floor sits is the first step to knowing what a pregnancy-safe standard has to add on top of it.
What the law actually requires
Regulation (EC) 852/2004: hygiene and HACCP
The cornerstone of EU food hygiene law obliges every food business operator to put in place, implement and maintain permanent procedures based on HACCP principles. In practice this means identifying hazards, determining critical control points, setting critical limits, monitoring, taking corrective action, verifying, and documenting.
What it does not do is name pregnancy as a hazard category. The regulation is hazard-based and risk-based in the general sense — it asks whether a food is safe for consumers, not whether it is safe for a specific physiological state. A cook-chill process validated as safe for the general population satisfies the regulation regardless of who eats the result.
Regulation (EU) 1169/2011: food information to consumers
This is the regulation most front-of-house staff have actually been trained on, because it mandates allergen disclosure. Fourteen allergens must be declared, including for non-prepacked food served in restaurants, with each Member State free to determine the exact form of that communication — written menu, notice, or verbal on request with a signposted written record available.
Article 7 adds a general fairness duty: food information must not be misleading, and must not attribute to a food properties it does not possess. That article matters more than most operators realise — a restaurant advertising itself as “safe for pregnancy” without a substantiated basis is exposed under it.
But again, pregnancy is absent. Listeria risk from a soft cheese is not an allergen. Mercury content in a large predatory fish is not an allergen. Neither triggers a mandatory disclosure.
Regulation (EC) 2073/2005: microbiological criteria
This regulation is the closest EU law comes to acknowledging pregnancy. It sets microbiological criteria for foodstuffs, and for ready-to-eat foods able to support the growth of Listeria monocytogenes it establishes a limit of 100 CFU/g during shelf life, with a stricter absence-in-25g requirement for foods intended for infants and for special medical purposes.
Note what that means in practice: a ready-to-eat food can legally carry a detectable listeria load and still comply. For a healthy adult that limit is well-calibrated. For a pregnant woman, whose risk of invasive listeriosis is many times higher than the general population’s, the same number represents a materially different level of exposure.
Regulation (EU) 1379/2013 and mercury limits
Fishery products carry species and origin labelling obligations, and Regulation (EU) 2023/915 sets maximum mercury levels by species. Swordfish, shark and certain tuna carry higher permitted limits precisely because they naturally accumulate more — the limit is set at what is tolerable for the general population, and national authorities issue separate, non-binding advice telling pregnant women to avoid those species altogether.
That advice is public health guidance, not a service obligation. No EU regulation requires a restaurant to repeat it at the table.
The gap, stated plainly
Put the four pillars together and the picture is consistent. A restaurant operating lawfully in the EU may:
- serve a ready-to-eat food containing listeria within the 100 CFU/g limit,
- serve swordfish or shark to a pregnant guest with no mercury advisory,
- serve unpasteurised soft cheese with no pregnancy warning,
- serve a lightly cooked egg preparation with no indication of the cooking temperature reached,
- and disclose none of this unless asked a direct question — and in several Member States, only if that question touches one of the fourteen allergens.
Every one of those is legal. Several of them are, for a pregnant diner, the exact things she was told at her first antenatal appointment to avoid.
What a pregnancy-safe standard adds
A credible pregnancy-safe certification is not a parallel legal regime. It is a voluntary standard that takes the HACCP architecture the law already requires and extends it to a defined vulnerable group.
Tighter microbiological targets
Absence in 25g rather than 100 CFU/g for ready-to-eat items served on the pregnancy-safe menu, aligning those dishes with the stricter category the law reserves for infants and medical nutrition.
Species exclusion, not just labelling
High-mercury species removed from pregnancy-safe options entirely, rather than disclosed and left to the guest’s judgement at the moment of ordering.
Proactive disclosure
Menu marking and staff scripts that surface pregnancy-relevant information without the guest having to ask. This inverts the legal default — the law is reactive, a pregnancy-safe standard is declarative.
Process separation
Dedicated preparation sequencing and cross-contamination controls above the general HACCP baseline, because the tolerance for error is lower.
Documented verification
Third-party audit and periodic surface testing, which converts an internal claim into a defensible one — and, under Article 7 of Regulation 1169/2011, that substantiation matters legally as well as commercially.
The liability angle operators tend to miss
There is an asymmetry worth naming. Doing nothing about pregnancy exposes a restaurant to very little legal risk under EU food law. Claiming something about pregnancy without substantiation exposes it to considerably more.
A menu note reading “suitable during pregnancy” is a food information statement. If it cannot be evidenced — no defined criteria, no process controls, no records — it is a claim attributing to a food properties it does not possess. Certification is, among other things, the evidence file that makes such a claim defensible.
This is why the safest position is not silence, and not an informal reassurance from a well-meaning server. It is a documented standard applied consistently.
Where regulation is likely to move
The direction of travel across EU consumer law is toward more disclosure to identifiable vulnerable groups, not less. Allergen rules for non-prepacked food were themselves a relatively recent extension of obligations that previously applied only to packaged goods. Several national authorities have already issued restaurant-facing pregnancy guidance, and voluntary standards typically precede regulatory ones by several years.
Restaurants building pregnancy-safe protocols now are, in effect, implementing early what a later revision may formalise — with the commercial advantage of having done it first.
Practical next steps
Start by auditing your current menu against the four pillars above: which ready-to-eat items could support listeria growth, which fish species exceed pregnancy advisory thresholds, which dishes involve unpasteurised dairy or undercooked egg, and what your staff currently say when a guest mentions she is pregnant.
That audit almost always produces a shorter list of required changes than operators expect — most kitchens are closer to the standard than they assume, and the work is in formalising and documenting rather than rebuilding.
The SafeBloom certification course walks through that audit step by step, with the criteria, record templates and staff scripts needed to move from legal compliance to a substantiated pregnancy-safe claim. Guests can confirm any establishment’s status through our certification verification page, and browse certified venues across Europe in the SafeBloom certified restaurant directory.