5 EU Labelling Mistakes That Cost FMCG Brands Thousands
EU food labelling law is deceptively specific. Regulation (EU) No 1169/2011 — the Food Information to Consumers (FIC) regulation — runs to 45 articles, 15 annexes, and a growing body of Commission notices and member-state guidance. Most FMCG brands understand the broad strokes: list ingredients, declare allergens, print a nutrition table. But the details trip up even experienced regulatory teams, and the cost of getting them wrong is measured in product recalls, retailer delistings, and fines that start at five figures.
We see the same five mistakes come up again and again. Here they are, along with what the regulation actually requires and how to fix each one before your label goes to print.
1. Allergen Emphasis Failures
What the law says
Article 21 of Regulation 1169/2011 requires that substances or products listed in Annex II — the 14 mandatory allergens — must be emphasised in the ingredients list through a typesetting that clearly distinguishes them from the rest of the list. The regulation mentions bold, but practice also accepts CAPITALS or a contrasting colour, provided the emphasis is consistent and unambiguous.
The 14 allergens are: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, tree nuts, celery, mustard, sesame, sulphur dioxide and sulphites (above 10 mg/kg), lupin, and molluscs.
Where brands fail
The most common mistake is missing derived allergens buried in compound ingredients. Take casein: it is a milk protein, so it must be emphasised as a milk allergen. Yet we regularly see labels where casein appears in plain text inside a sub-ingredient list, with no bold, no capitals, and no reference back to milk. The same happens with whey, lactose, lecithin (soy), and wheat starch.
Another frequent error is inconsistent emphasis. A label might bold "MILK" in the main ingredients list but fail to bold "milk powder" in a compound ingredient further down. Article 21 does not allow selective emphasis — every occurrence of every allergen must be distinguished.
The fix
- Maintain a master allergen dictionary that maps every derivative back to its parent allergen (casein to milk, lecithin to soy, semolina to wheat, and so on).
- Run an automated scan against the ingredients text before artwork approval. If your PIM or label management system does not support this, build a simple validation rule.
- Use a single, consistent emphasis method across the entire label — bold uppercase is the safest choice.
2. Nutrition Declaration Rounding Errors
What the law says
Article 30 requires a mandatory nutrition declaration covering energy, fat, saturates, carbohydrate, sugars, protein, and salt. Annex XV specifies the expression and rounding rules: energy must be declared in both kilojoules (kJ) and kilocalories (kcal), and each nutrient has defined significant-figure rules.
Energy values must be rounded to whole numbers. Fat, carbohydrate, sugars, protein, and salt must be rounded to one decimal place (0.1 g) when the value is below 10 g per 100 g, and to whole numbers above that. The order of kJ and kcal matters too — kJ must come first.
Where brands fail
The most frequent rounding error is declaring energy in kcal only, omitting kJ. This is non-compliant in all EU member states. A close second is rounding fat or sugar to whole numbers when the value falls below 10 g — for example, declaring "Fat: 3 g" instead of "Fat: 3.2 g".
Brands also stumble when adapting labels from non-EU markets. A US Nutrition Facts panel uses different rounding rules, different reference amounts, and a completely different format. Copy-pasting values without recalculating for EU rules is a guaranteed compliance gap.
The fix
- Build a nutrition declaration template that enforces Annex XV rounding automatically — spreadsheet validation or a purpose-built tool.
- Always declare kJ first, then kcal in parentheses, on the same line.
- When adapting from non-EU labels, recalculate from the raw analytical data rather than transcribing rounded values.
3. Net Quantity Mistakes
What the law says
Article 23 requires net quantity to be expressed in litres, centilitres, or millilitres for liquids and in kilograms or grams for other products. Crucially, the net quantity must appear in the same field of vision as the product name — meaning the consumer must be able to see both without turning the pack.
Directive 76/211/EEC (the "e-mark" directive) and its amending legislation also prescribe minimum font sizes based on the net quantity value: 6 mm for products over 1,000 g or ml, 4 mm for products between 200 g and 1,000 g, 3 mm for products between 50 g and 200 g, and 2 mm for products up to 50 g.
Where brands fail
The field-of-vision rule is the one that catches people out. On a narrow jar or a tube, the brand name sits on the front panel but the net quantity gets pushed to a side panel during artwork layout. That is non-compliant. Similarly, brands sometimes print the net quantity at a font size that looks fine aesthetically but falls below the legal minimum for the pack size.
Another error is declaring net quantity in the wrong unit — for example, using grams for a pourable sauce instead of millilitres, or failing to switch from "ml" to "cl" when that is the norm in the target market.
The fix
- Add a mandatory field-of-vision check to your artwork review process. The product name and net quantity must be on the same panel.
- Create a font-size lookup table tied to pack size and enforce it at the design stage, not during final proofing.
- Confirm the correct unit of measurement for each product category and target market early in the brief.
4. Country of Origin Declarations
What the law says
Article 26 of the FIC regulation requires country of origin or place of provenance to be declared when its omission might mislead the consumer. This becomes mandatory for several product categories including fresh meat, honey, olive oil, and fruits and vegetables.
Where origin is declared voluntarily or mandatorily, Implementing Regulation (EU) 2018/775 adds the primary ingredient rule: if the primary ingredient does not originate from the declared country of origin, the label must either state the origin of the primary ingredient or indicate that it does not come from the declared origin. For example, if a pasta is labelled "Made in Italy" but the durum wheat comes from Canada, the label must say so.
Where brands fail
Many brands treat "Made in [country]" as a simple production statement without considering the primary ingredient disclosure. A chocolate bar "Made in Belgium" with cocoa from Ivory Coast is non-compliant if it does not declare the cocoa origin or add a qualifier like "made from cocoa beans that do not originate from Belgium."
Brands also confuse "origin" with "provenance" and misapply the rules — especially in cross-border private-label arrangements where the brand owner, the manufacturer, and the ingredient sources are in three different countries.
The fix
- Map the origin of every primary ingredient against your finished-product origin claim.
- If there is a mismatch, add the required disclosure in close proximity to the origin claim, using the same font size.
- Review origin claims every time you change a supplier — a new sourcing arrangement can instantly make an existing label non-compliant.
5. Translation Gaps
What the law says
Article 15 requires that mandatory food information be provided in a language easily understood by consumers in the member state where the product is marketed. Most member states have legislated this to mean the official language(s) of that country.
This gets complicated fast in multilingual markets. Belgium alone requires labelling in French, Dutch, and German — all three — depending on the region of sale. If you distribute nationally in Belgium, all three languages must appear on pack. Finland requires Finnish and Swedish. Luxembourg requires at least one of French, German, or Luxembourgish, though practice overwhelmingly favours French.
Where brands fail
The Belgium example is the most common pitfall. Brands enter the Belgian market with a French-only label, not realising that Flemish enforcement authorities in the north will pull the product for lacking Dutch. Even when all three languages are present, errors creep in through inconsistent translations — a storage instruction that says "keep refrigerated" in French but "store in a cool place" in Dutch is a compliance risk because the actual instruction differs.
Another gap: translating the product name but not the mandatory allergen information, usage instructions, or warning statements. Every piece of mandatory information under the FIC regulation must appear in every required language.
The fix
- Build a market-language matrix that maps every target country to its required languages.
- Use qualified regulatory translators, not general translators, for mandatory label text.
- Run a side-by-side comparison of each language version to confirm that every mandatory element is present and consistent.
The Cost of Getting It Wrong
A product recall in the EU typically costs an FMCG brand between EUR 50,000 and EUR 150,000 in direct costs — logistics, destruction, replacement stock, and retailer penalties. That figure does not include the indirect costs: lost shelf space, damaged retailer relationships, consumer complaints, and the regulatory scrutiny that follows a recall.
Allergen labelling errors are particularly costly because they are treated as food safety issues, not just labelling non-conformities. They trigger RASFF notifications, mandatory public recalls, and in some member states, criminal liability for the responsible person.
The cheapest recall is the one that never happens. Every one of these five mistakes is preventable with the right validation processes built into your product data workflow.
Prevention Starts with Product Data
All five of these labelling mistakes share a root cause: product data that is incomplete, inconsistent, or not validated against regulatory rules before it reaches the artwork stage. By the time the label is printed, the cost of correction has multiplied tenfold.
The solution is to validate compliance at the data layer — where ingredients are structured, allergens are mapped, nutrition values are calculated, and translations are managed — before any of that data flows into design software. That is exactly what a product information management approach should deliver, and it is the principle behind how Artyql handles compliance for FMCG brands across Europe.