Codex CCFL49: What Came Out of Five Days in Ottawa
Labelling, advertising and marketing are a considerable part of my practice. Allergen statements, bilingual claims, country-of-origin language, and joint-presentation rules for multipacks are some of the rules that decide whether a product can sit on a shelf in Canada, or whether the company selling it is exposed to enforcement, recall liability, or a Competition Bureau referral.
What the food sector’s stakeholders sometimes do not see is that many of those rules arrived in Canada through the Codex Alimentarius Commission years before they appeared in the Food and Drug Regulations or the Safe Food for Canadians Regulations. Codex sets international labelling standards through its Committee on Food Labelling. Canada hosts that committee, has done so for decades, and chairs its sessions. The 49th Session of CCFL met in Ottawa from May 11 to 15, 2026.
I didn’t attend CCFL49, so what follows is based on the formal report, REP26/FL, published May 26, and follow-up conversations with colleagues rather than meeting-room impressions. But this is intended to serve as a primer on what came out of CCFL49 and what it means for Canadian food companies over the next twelve months.
How Codex shows up in Canadian rules and why it matters
Codex is not foreign to Canadian food law. In 2026, it is closer to a foundation of it. The SFCA gives the regulatory system a mechanism to incorporate external standards: section 52 lets the regulations incorporate "any document, regardless of its source ... as it is amended from time to time," and the SFCR's preventive-control framework - the HACCP-based core of the modern safety regime - is itself drawn from Codex's General Principles of Food Hygiene.
Labelling, however, is the piece that does not automatically absorb Codex-based ideas. A Codex labelling standard, the kind CCFL produces, generally runs through Health Canada and CFIA consultations, the Canada Gazette, and the amendment process. That can take years, but it lands in a system built on Codex foundations, which is why Canadian regulators treat what CCFL decides as a benchmark, not a foreign import, when the next round of FDR or SFCR labelling amendments is designed. It also serves as a benchmark for Canada's export markets: a company selling into the EU, the U.K., Brazil, or Japan has a commercial interest in what is advanced at CCFL before any domestic amendment follows.
What’s changed?
The CCFL49 items sat at different stages of Codex’s eight-step adoption process. Stage matters: an item at Step 7 is close to adoption, while one at Step 4 is early enough that the substance is still negotiable. You can read more about the Codex process here: Reading a Codex Proposal: From Draft to Adopted Standard.
The big news from CCFL49 was that three items were forwarded to the Codex Alimentarius Commission for adoption in Geneva this July: precautionary allergen labelling at Step 8, and the multipack and emergency-labelling texts at Step 5/8. After that, one proposal was declined outright, one was deflected to a sister committee, and two were kept for further work.
Precautionary allergen labelling (PAL)
In Canada, “may contain” statements are not mandated by the Food and Drug Regulations. The priority allergen, gluten and added-sulphite rules sit in B.01.010.1 and the sections that follow; precautionary statements are voluntary, governed by Health Canada’s February 2012 Position on the Use of Food Allergen Precautionary Statements on Prepackaged Foods, which asks companies to use them only for a real cross-contact risk. No rule sets a trigger or action-level threshold. But the statement is not unregulated: once a cross-contamination “may contain” declaration is used, FDR B.01.010.4 governs how it appears (placement immediately after the ingredient list or “Contains” statement, bilingual where that statement is bilingual, and prescribed formatting and type height) and section 5(1) of the Food and Drugs Act bars any version that is false or misleading. In practice, a precautionary statement can invite CFIA scrutiny of whether the manufacturing practices and cross-contamination controls justify it. CFIA truly intends for PAL to be used as a last resort.
The proposed annex to the General Standard for the Labelling of Pre-packaged Foods (CXS 1-1985) on precautionary allergen labelling came in at Step 7. This is the international rule for “may contain” statements - the language manufacturers use to flag possible cross-contact with priority allergens.
This was the most consequential outcome of the session. The annex now goes to CAC49 (6-10 July, Geneva) for consideration for final adoption as a Codex standard. It had been held at Step 7 since CCFL48 and made good headway after two FAO/WHO expert consultations in 2025, one on risk-assessment guidance and one on gluten (Rome, November 2025), building on the earlier Risk Assessment of Food Allergens series (Parts 2 and 3, 2022-2023).
So what does this mean? Well, the guidelines anchor on reference doses for priority allergens: for the first time at Codex level, a 4 mg gluten reference dose for cereals containing gluten, separate from wheat-allergy thresholds. The reference dose is a risk-assessment input manufacturers use to calculate food-specific action levels, not a consumer-facing label threshold. The 20 ppm gluten-free policy threshold - Health Canada’s interpretation of FDR s. B.24.018 - is unchanged.
The text CCFL49 agreed (REP26/FL, Appendix III) sets the discipline as a sequence, not a number. Controls come first: PAL is restricted to risk that cannot be prevented or controlled under the Code of Practice on Allergen Management for Food Business Operators (CXC 80-2020) (s. 4.1). The decision to use PAL rests on a risk assessment, qualitative first and quantitative where needed (s. 4.2). A “may contain” statement is warranted only where residual presence exceeds the food-specific action level - the reference dose divided by the amount consumed - not as a default disclaimer (s. 4.3). And where PAL is used for cereals containing gluten, “gluten-free” cannot also appear (s. 4.3.2).
In terms of what this means for the Canadian marketplace, Health Canada has no published timeline for a binding “may contain” rule, and the 2012 Position remains the operative guidance until that changes. But the Codex framework is a forward read on the structure any eventual Canadian rule will rest on, and Canadian practice is already pointed the same way. Food Allergy Canada’s published guidance for food manufacturers - developed through a 2020 collaboration with Université Laval’s Food Risk Analysis and Regulatory Excellence Platform (PARERA) and Maple Leaf Foods, funded by Agriculture and Agri-Food Canada’s AgriAssurance Program - already takes a risk-based approach to PAL: controls first, “may contain” reserved for residual, risk-assessed presence. Even ahead of formal adoption, that guidance is up for review: Food Allergy Canada has indicated to industry stakeholders that it is reviewing its guidance in light of the CCFL49 outcome. Allergen-sensitive sectors - dairy, plant-based, bakery, confectionery, nuts - should be aligning their “may contain” SOPs to a risk-based framework now; the work is the same whether or not Canada moves quickly.
It’s worth noting, however, that on May 5 the Senate gave first reading to Bill S-247, An Act to establish a national framework on food allergy (Senator Andrew Cardozo); it is now at second reading. The bill would require the Minister of Health to table, within eighteen months, a framework covering six areas, one of which is “access to accurate ingredient information.” It does not amend the FDR, change the priority allergen list, or prescribe “may contain” practice - it is a framework instrument, and any operational effect runs through what the framework recommends and what Health Canada then acts on. The reason to flag it is its timing in relation to CCFL49 and this PAL development: food allergy is back on the federal agenda just as Codex moves on the international “may contain” rule, and the next Health Canada team to draft an allergen-labelling amendment will read the two together.
Multipack and joint-presentation labelling
The rule for variety packs, bundles, and outer cartons holding multiple labelled units reached Step 4. Going in, the 1985 standard was silent on the practical questions: whether allergen statements repeat on the outer pack, how to handle mixed shelf lives, whether nutrition has to appear on each unit or only the carton. CCFL49 forwarded the amendments at Step 5/8, and the text is now public in REP26/FL, Appendix IV. The core rule (s. 8.1.3.1): the outer pack carries the container's mandatory labelling unless that information is already legible and discernible on at least one of each type of inner unit.
This isn’t really news for Canada, as CFIA's position is effectively the same: where more than one unit is sold together, the required information goes on the outer consumer package, unless each inner unit is fully labelled and visible at the time of purchase. So, for Canadian multipacks we view this new Codex text as confirmation of Canadian market practices.
Country of harvest for spice labelling
Country of harvest was a quiet item on an ambitious agenda but one I find interesting. It runs head-on into food fraud, supply-chain traceability, geographical indications, and the old customs-law question of where a product is really "from." Any one of those sub-items could be its own post on this blog, and we will give this one the room it deserves another day. For now, the short version:
The committee looked at whether to add "country of harvest" to spice labels alongside the mandatory country of origin. Country of origin and country of harvest are not the same thing, and this difference is a problem in the spice trade specifically. Country of origin is a trade-law idea: it tracks where a product had its "last substantial transformation." Country of harvest asks a plainer question: where was this actually grown? For some foods they may converge, but for spices, which are barely transformed at all, harvest and origin can sit continents apart; the spice grown in one country can be processed in a second and packaged in a third. The origin claim ends up telling you little-to-nothing about where the crop left the ground. That gap is where some of the most fraud-prone foods in the world get mislabelled. Saffron and oregano are the textbook cases.
CCFL49 did not make country of harvest mandatory, or optional, across the board. But it did agree to nine guiding principles and handed them to the Codex Committee on Spices and Culinary Herbs (CCSCH) to use in commodity standards development. I would flag a classic country of origin labelling jurisdictional principle here: Codex origin labelling is for health, safety, and fair trade, while selling a product on its origin like "Kashmiri saffron" or "Tellicherry pepper" is left to voluntary claims and, in some parts of the world, to the geographical-indications system. In other words, Codex stayed in its lane. Saffron received special wine-adjacent treatment: you cannot grow saffron in one place and have it "originate" in another, so for that standard origin and harvest are the same thing, with region and year of harvest now optional. Weird but fun to see concepts of terroir and vintage quietly applied to a spice.
For Canadian importers, distributors, and private-label programs, all of these issues now sit with CCSCH, so there is no regulatory immediacy to this. But supply-chain transparency is changing and spice fraud is well documented. If you can already answer "where was this spice grown," you are ahead of both the fraud risk and whatever CCSCH eventually puts into place.
Food labelling provisions in emergencies
When the meeting opened, Codex had an early-stage draft (Step 4) of guidelines on emergency labelling derogations: temporary, authorized departures from normal labelling rules during events like a pandemic or supply shock. COVID-19 and subsequent supply chain disruptions saw countries improvise these flexibilities with no common approach. The Codex work is intended to set a shared standard for granting them without sacrificing allergen disclosure or consumer protection, and CCFL49 advanced the text on an accelerated track (Step 5/8). The point for industry: only a competent authority (in Canada it’s CFIA or Health Canada) can grant a derogation; a manufacturer cannot relax its own label and call it an emergency.
The sharpest commentary came from the International Baby Food Action Network (IBFAN), which argued that emergencies are politically defined and manipulable and that flexible labelling complicates traceability and recall integrity. It pressed for stronger safeguards and for foods for infants and young children to be excluded from emergency flexibilities altogether. The intervention did not change the outcome, but it is on the record and will anchor opposition to national implementations. I include IBFAN’s work here because it’s a salient point and it helps provide non-participants a window into the work that goes into creating alignment at CCFL. More practically, for Canadian manufacturers that used CFIA's COVID-era flexibilities, the framework is a forward read on two things: the shape of future emergency derogations, and the disclosures Canada will hold non-negotiable even in a crisis.
Future work
The committee kept two items on its future-work inventory. The first is alcoholic-beverage labelling, which in Canada is governed by a mosaic of regulatory and legislative tools: the FDR for nutrition and allergens, the SFCR for compositional and standard-of-identity rules, and the Excise Act, 2001 and provincial liquor regimes for the rest. CCFL49 reached no consensus to start and declined to form a working group; the topic will stay on the inventory and is open to a narrower proposal later. For Canadian food and beverage companies, the Codex anchor will not arrive quickly, but the fact that it is staying on the list is relevant.
The second is a “small packages” definition with exemptions from mandatory nutrition labelling, relevant to any product too small for a full nutrition facts table or bilingual statement under Canadian rules. It drew general support but ran out of time; Panama and the International Chewing Gum Association are championing efforts on this topic and will revise the project document for CCFL50.
Ultra-processed foods
A proposal to start work on ultra-processed-foods (UPF) labelling had been circulating before the meeting. CCFL49 declined it this time around, as no project document had been submitted. This makes sense: there is no scientific consensus on the definition of UPF, nor its relevance to a labelling mandate as opposed to nutrition or policy. UPF was removed from the new-work inventory. The procedural reasons for declining UPF (the formal project document and lack of consensus) can be addressed before CCFL50 by any country willing to do the work and expend political capital on this specific issue. Whether any country sees that as a priority is not yet obvious.
This is a quiet-but-relevant discussion in Canada. In the United States, UPF is drawing both litigation and regulatory attention: an early personal-injury suit was dismissed in 2025, and the GRAS self-affirmation pathway is under FDA review. Elsewhere we’re seeing more analysis on the efficacy of FOP labelling programs on populations. In the Canadian context, Health Canada’s front-of-pack nutrition symbol became mandatory on January 1, 2026 under the 2022 FDR amendments. The FOP symbol is not a UPF designation, but the two travel parallel paths arising from adjacent nutrition-policy concerns. So, as the UPF discussion matures in individual markets and becomes more aligned in important markets (with respect to definitions and nutritional impacts, e.g.), we can expect Canadian policymakers to look to Codex and for Codex to push this analysis forward. All to say, our view is that this international refusal does not shut any domestic or international doors with respect to UPF.
What this means in the next twelve months
The Codex calendar moves slowly, and the value of tracking it is forward visibility, not immediate compliance. Part of my job is to track new ideas and amorphous proposals for Canadian food companies and then counsel them on Canadian exposure. From CCFL49, three things follow:
If you use "may contain" statements, build your PAL SOP now - align your precautionary-labelling procedures to a risk-based framework, controls first. The 4 mg gluten reference dose is an internal input for action-level decisions, not a consumer-facing threshold. Health Canada will set its own implementation timeline, but the framework is clear and we have excellent Canadian tools and resources like those built out by Food Allergy Canada.
The multipack rules aren’t much of a change for Canadians, matching existing CFIA guidance. If your private-label, club-pack, and seasonal programs follow the outer-pack rule today, there isn’t much to do. If you're unsure, reach out.
For those connecting the concept of UPFs to front of pack labelling, do not read the UPF deferral as opening the door to future FOP relief. These are related concerns, but separate rules and separate timelines - you’d do well to watch both.
Glenford Jameson is the principal of GSJ&Co., a Canadian food law and regulatory affairs practice. This post is for informational purposes only and does not constitute legal advice.