Five failure modes that kill a food label at review — and the regulations behind each one

Most teams I talk to don’t lose labels to one catastrophic mistake. They lose them to the same five or six quiet, boring failure modes that show up every single review cycle — the kind of issues a regulatory lead catches on the fourth pass and a copacker catches after the plates are cut.

The pattern is usually the same. Design finishes the artwork on a Thursday. The file goes to regulatory. Two weeks later it comes back with eleven comments. Three rounds of edits happen. Half of those comments are the same three or four issues that come up on every SKU, and nobody has the time to build a real checklist because the next launch is already pressing. So the same failures compound, SKU after SKU.

Here are the five I see most often in North American F&B and CPG work, with the actual rules they trip over. If you’re running a label program at a mid-market manufacturer, none of this will be new — but it might be useful to have them all in one place.

1. Nutrition Facts panel formatting — the boring details that get flagged

Most of the pain lives in 21 CFR §101.9. The 2016 format rewrite has been fully in force for years, but I still see SKUs printed in the pre-2020 style that have never been re-reviewed — usually because they’re slow movers and nobody wanted to touch them.

What gets flagged, in rough order of frequency:

• Rounding. Calories round to the nearest 5 below 50 and the nearest 10 at 50 and above. Sodium and potassium round to the nearest 5 mg below 140, then to the nearest 10. Get the rounding wrong on two lines and the panel is non-compliant even if every other number is right.
• Added sugars. Required as a sub-line under Total Sugars, with both grams and %DV. The number of labels I’ve seen with Total Sugars but no Added Sugars line is higher than you’d think.
• Dual-column panels for products with a reasonable possibility of being consumed in a single eating occasion above the RACC (e.g., a 20 oz bottle).
• Vitamin D and potassium with actual amounts plus %DV — not just %DV. Vitamin A and C are no longer required.
• Serving size in household AND metric units (“2 tbsp (30 g)”), not one or the other.
• Type size and leading. Minimum 8-point for most of the panel, 6-point for footnotes, specific leading requirements on the larger figures. Designers shrink the panel to fit the layout and the whole thing falls out of compliance.

Individually these are small. Stacked on one SKU, they’re a whole revision cycle.

2. Allergen declarations — the “Contains” statement

FALCPA governs the majors. The FASTER Act added sesame as the ninth major allergen effective January 1, 2023. If your label was written before that and you haven’t re-reviewed it, you have exposure.

Two failure modes I see constantly:

The “Contains” statement is in the wrong place, or missing entirely. It must appear immediately after or adjacent to the ingredient statement, in a type size no smaller than the ingredient list. I’ve seen “Contains: milk, soy, wheat” lines tucked below the UPC on the back panel, three inches from the ingredient statement. That’s a fail. Allergens listed inside the ingredient statement don’t exempt you from the separate “Contains” line.

Tree nuts and fish/shellfish are declared generically. FDA requires the specific species: “Contains: Almonds, Walnuts” — not “Contains: Tree Nuts.” Same for fish (“Cod, Salmon”) and crustacean shellfish (“Shrimp, Crab”). Teams writing the “Contains” statement from memory almost always default to the category.

And sesame — worth a separate mention because it’s the newest. If you’re producing a product with tahini, sesame oil, or a spice blend that contains sesame, it’s now a required allergen callout. A lot of 2022-era labels are still in circulation that predate this.

3. Ingredient statement order and sub-ingredient disclosure

21 CFR §101.4. Ingredients in descending order by weight as added to the formulation — not as they appear in the finished product after water loss, not alphabetically, not grouped.

The silent failure is compound ingredients. A spice blend, a chocolate coating, a pre-made bread crumb, a flavor system. Sub-ingredients inside a compound must be disclosed in parentheses when they contain:

• A major allergen (e.g., “Natural Flavor (contains milk)”)
• A certified color (FD&C Red 40, Yellow 5, Yellow 6, Blue 1, Blue 2, Green 3 — these require by-name disclosure)
• Certain additives that must be individually declared by regulation

I see “natural flavors” and “spices” treated as black boxes on labels whose compound suppliers have clearly confirmed allergens are present. That’s a direct non-compliance, and it’s the kind of thing that shows up in warning letters — not in the first review.

The fix is upstream: get complete sub-ingredient statements from your suppliers in writing, and audit them when a formulation or a supplier changes. “Same as last time” is how nested allergens get missed.

4. Claims that silently trigger additional rules

21 CFR §101.13 and the nutrient content claim subparts. Every one of these words carries a definition:

• “Low sodium” — ≤140 mg per RACC.
• “Low fat” — ≤3 g per RACC.
• “Good source of” — 10–19% DV per RACC.
• “High” / “Excellent source of” — ≥20% DV per RACC.
• “Light” — has three different definitions depending on whether you’re talking about calories, fat, or sodium.
• “Healthy” — FDA finalized a new definition in late 2024 that raised the bar substantially (food-group requirements plus tighter limits on added sugars, saturated fat, and sodium). Labels written to the pre-2024 “healthy” rule are quietly non-compliant now, with a compliance date clock running.
• “Natural” — no formal FDA definition, but an active policy and an enforcement posture. Use it with eyes open.

The structural failure: claims are usually written by marketing or brand, and regulatory often doesn’t see the claim copy until it’s already on the front of the box. By the time the label hits review, the claim is a design element nobody wants to pull. Build claim review into the front-of-pack brief, not the back-end compliance pass.

5. Canadian SKUs — bilingual requirements and CFIA differences

If you’re a US brand expanding north, this is the failure mode. A US-compliant label cannot be dropped into Canada with a language sticker.

Canada’s Food and Drug Regulations and the Safe Food for Canadians Regulations govern most of this. A non-exhaustive list of what has to change:

• All mandatory information bilingual. English and French, with equal prominence. The Nutrition Facts Table is bilingual on the same panel (“Nutrition Facts / Valeur nutritive”). Ingredient statements require both languages. The allergen statement is “Contains / Contient.”
• Canadian NFt format is not the FDA panel. Different required nutrients in some categories, different rounding rules, different %DV reference values (Health Canada’s DVs aren’t identical to FDA’s), different formatting specifications.
• Net quantity declarations are metric-first, with specific type size minimums based on the principal display surface area.
• Common names follow CFIA conventions — the US common name isn’t always the Canadian one. “Enriched flour” vs. “farine enrichie” is the easy case; “half and half” vs. “crème 10%” is the one that trips teams up.

If you sell into both markets, you’re running two label programs, not one, and the cost of treating them as one — re-printed packaging, CFIA findings, delisted SKUs — is real.

Closing

None of these five are exotic. They’re the ordinary, repeating grind of a food label program. What makes them expensive is that the review loop is slow: a two-week external review, five comments back, a design revision, another two weeks. A SKU launch that should take a month takes a quarter, and the same failure modes show up on the next SKU because nobody had the bandwidth to turn the lessons into a checklist.

At Complion we spend all day staring at these exact failure modes across FDA and CFIA — if you’re seeing something weird show up repeatedly in your own reviews, I’m happy to compare notes. I’m reachable.

— Hoa