Food Safety

Food Labeling: What the Regulations Require

By Claudia · · 7 min read

Food Labeling: What the Regulations Require

Food Labeling: What the Regulations Require

Food labeling is far more than the wrapper around a product. It's the first line of communication between a company and its consumers, and also one of the points of greatest legal exposure for any quality manager. A misplaced detail, an undeclared allergen or an ambiguous expiration date can lead to a food safety alert, a product recall and reputational damage that's hard to undo. In this article we go over what current regulations require, the most common mistakes, and how to build labeling into an efficient quality system.

What information is mandatory on food labels in Spain

In Spain, food labeling requirements are set out mainly by Regulation (EU) 1169/2011, which applies directly across the whole country. This regulation lists the mandatory particulars that must appear on the label of any food product intended for the end consumer or for mass catering.

The mandatory particulars are as follows:

  • Name of the food: legal name or, failing that, a descriptive name for the product.
  • List of ingredients: in descending order of weight, with allergens highlighted typographically.
  • Quantity of certain ingredients or categories: when they appear in the name or the image.
  • Net quantity: in units of volume or mass, as appropriate.
  • Date of minimum durability or expiration date: preceded by the correct wording for the type of product.
  • Storage and/or usage conditions: when necessary to guarantee safety.
  • Name or business name and address of the responsible operator.
  • Country of origin or place of provenance: when omitting it could mislead the consumer.
  • Instructions for use: when it would be difficult to make proper use of the food without them.
  • Alcoholic strength: for beverages with more than 1.2% alcohol by volume.
  • Nutrition declaration: mandatory since December 2016.

Beyond the EU framework, the Spanish Agency for Food Safety and Nutrition (AESAN) (AESAN, n.d.) publishes interpretation guides and answers queries that help operators apply these requirements to specific cases, especially when the packaging format or the type of product raises questions.

Regulation (EU) 1169/2011 and allergen labeling, explained without the jargon

Allergen labeling is, without a doubt, the area that causes quality departments the most headaches. Regulation (EU) 1169/2011 requires 14 substances or products known to cause allergies or intolerances to be declared whenever they're used in making a food and are present in the final product, even in modified form.

Those 14 allergens are: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, tree nuts, celery, mustard, sesame seeds, sulphur dioxide and sulphites, lupin and molluscs.

The regulation requires these ingredients to appear in the ingredient list in a typeface that clearly sets them apart from the rest — bold, capitals, italics or a different color. It isn't a matter of style: it's a legal requirement, and failing to meet it can have serious consequences for consumer health.

One point that often causes confusion is so-called precautionary allergen labeling, or cross-contamination statements. Phrases like "may contain traces of…" aren't required under Regulation (EU) 1169/2011, but they are governed by industry best practice and risk management. If your company uses them, they must be backed by a documented risk analysis, and they can't be used as a substitute for good preventive management. For more on this, see our article on managing allergens without the risk and our allergen glossary.

The most common labeling mistakes — and why they end in a product recall

Labeling mistakes are one of the most frequent causes of food alerts in Europe. The RASFF system (Rapid Alert System for Food and Feed) logs numerous notifications every year related to misleading information, undeclared allergens or incorrect data. These are the failures that show up most often in audits and in real alerts:

  • Undeclared or poorly highlighted allergens: the most critical one. It can trigger serious reactions in sensitive consumers and forces an immediate withdrawal of the batch from the market.
  • Incorrect expiration or best-before date: confusing the two, or a typo in the batch code, are seemingly minor mistakes with disproportionate consequences.
  • Incorrect name of the food: using a name that doesn't match the product's legal category can be considered misleading information.
  • Nutrition declaration with calculation errors: values that don't match the product's real formulation, especially common when an ingredient changes without the label being updated.
  • Labels left outdated after a formulation change: one of the most common mistakes, and one of the easiest to avoid with an effective document-management system.
  • Missing or illegible net quantity or batch information.

As set out in Regulation (EC) No 178/2002 (Regulation [EC] 178/2002, 2002), food business operators are responsible for ensuring that the food they place on the market meets the food-law requirements applicable to their activities. That includes the accuracy and truthfulness of the information on the label.

The key to avoiding these mistakes isn't just checking the label before printing — it's building a workflow where any change to the formulation, to an ingredient's supplier, or to the production process automatically triggers a label review.

How to link labeling to the technical data sheet and batch traceability without duplicating data

One of the most widespread problems in quality departments is siloed management: the product's technical data sheet lives in a Word document, the label is designed in a different program, and batch traceability is logged in a separate spreadsheet. The result is that every update has to be made manually in three or more places, with the resulting risk of inconsistencies.

The solution is to build a document architecture where the label is generated from the product's technical data sheet, not independently of it. That means:

  • The ingredient list on the label should be derived directly from the formulation recorded in the technical data sheet, including the allergen declaration.
  • The nutrition declaration should be calculated from the raw-material composition data, not entered manually on the label.
  • The batch number on the label should be linked to the production record, so that if there's an alert, the affected batch can be traced in minutes, not hours.
  • Any change of supplier or ingredient specification should trigger an alert to review whether it affects the label.

Food quality software like Solved lets you centralize the technical data sheet, labeling and batch traceability in a single environment, eliminating duplicate data and drastically reducing the risk of errors. When the quality manager updates a product's formulation, the system can automatically flag that the label needs review, closing the control loop without relying on memory or manual checklists.

Food labeling isn't a bureaucratic formality: it's the documented reflection of everything happening in your production process. Managing it as part of the wider quality system not only reduces the risk of alerts and recalls, it also saves time and makes audits easier. If you'd like to see how Solved can help you get there, request a no-obligation demo.

References