Labeling is the point where regulatory requirements and physical product meet. A label error is not a document problem — it is a product problem, with direct consequences for patients, consumers, and the organizations responsible for getting it right.
Labeling compliance means more than having the correct information available. It means verifying that the right information appears accurately on every version of every product, across every market, every language, and every revision — reliably, and in a way that can be demonstrated after the fact. This guide covers what labeling compliance requires across pharma, medical devices, and FMCG/CPG, where labeling failures most often originate, and what a defensible labeling compliance process looks like regardless of industry.
Scope note: this guide provides a cross-industry overview. For full regulatory depth in a specific industry, see the dedicated guides linked throughout — Medical Device Labeling Requirements, Pharma Artwork Approval, and the FMCG/CPG allergen and PPWR guides.
Compliance labeling is broader than getting the text right. It has four components that apply across every regulated industry:
Content accuracy — the information on the label matches what was approved by the relevant regulatory authority: the right dosage, the right ingredient list, the right warnings, the right identification codes.
Version control — the label released for production is the same version that was approved, not a subsequent edit that was never re-reviewed, and not a superseded version that should have been replaced.
Format integrity — the approved content survives the process of becoming a printed or digital label without alteration. Text flattened into an image during a file conversion, a symbol rendered at the wrong size, a barcode that doesn't decode correctly — all represent a gap between approved content and released content, even when no one edited the words themselves.
Multilingual and multi-market accuracy — every language version and every market variant reflects the same approved content, verified against each other and against the approved master, not reviewed independently and assumed to be consistent.
These four components apply whether the product is a prescription drug, a surgical instrument, or a bottle of shampoo. What differs by industry is which regulatory bodies set the requirements, what specific content must appear, and what the consequences of failure look like.
Pharmaceutical labeling is governed in the US primarily by 21 CFR Part 201, which sets out the content requirements for prescription and over-the-counter drug labels — established name, active ingredients, dosage, warnings, and the manufacturer's identification. In the EU, Directive 2001/83/EC governs the Community code for medicinal products, including the labeling and package leaflet requirements, and Article 56a specifically requires Braille on the outer packaging of medicinal products.
Pharma labeling compliance carries some of the highest stakes of any industry, because the consequence of an error reaches a patient directly. A peer-reviewed ten-year analysis of FDA drug recall data found that labeling and packaging issues accounted for roughly 19% of drug recalls between 2012 and 2023 — a substantial and largely preventable share, behind impurities and contamination and control-related issues.
The specific compliance risks that recur in pharma labeling: version confusion during multi-round approval cycles, where a last-minute change is applied to the production file without triggering a full re-review; multilingual patient information leaflets, sometimes required in twenty or more languages, where a correction made in the master isn't propagated consistently; and the approaching shift to electronic Product Information (ePI), which changes labeling content from static PDF to structured, machine-readable data.
For full depth on pharma labeling requirements and how to build a compliant artwork approval workflow, see the Pharma Artwork Approval guide.
Medical device labeling compliance is governed by Regulation (EU) 2017/745 (EU MDR) in Europe and 21 CFR Part 801 in the US. Device labeling is distinct from pharma labeling in one important respect: it must be verified consistently across every level of packaging, not just on the primary label.
Under MDR Annex VI, the Unique Device Identifier (UDI) must appear on the device itself, on its packaging, and on all higher levels of packaging — and all levels must carry consistent, accurate UDI information. This consistency requirement is the most common source of device labeling non-conformities: a label revision updates the UDI at unit level, but intermediate packaging or case labeling is not updated in the same cycle.
Device labels must also carry ISO 15223-1 symbols that meet the current standard version — the 2021 revision superseded the 2016 edition, and a label using an outdated symbol version is non-compliant even if the symbol is visually similar to the current one. Instructions for Use (IFU) carry their own compliance burden: they must be provided in the official language(s) of every EU market the device is sold in, and revisions must propagate accurately across every language version.
For full depth on device labeling requirements — FDA, EU MDR, UDI, IFU, and ISO symbols — see the Medical Device Labeling Requirements guide.
FMCG and food labeling compliance is anchored by EU Regulation 1169/2011 (the Food Information to Consumers Regulation), which has required mandatory allergen declaration and specific typographic highlighting in ingredient lists since December 2014. In the US, the FALCPA and FASTER Act govern allergen labeling requirements for the nine major food allergens.
More than a decade after EU 1169/2011 came into force, undeclared or incorrectly declared allergens remain the leading cause of food recalls. A peer-reviewed study of global food recall data found that incorrect, missing, or undeclared allergen information accounted for 93% of allergen-related recall root causes — evidence that the persistent failure is procedural rather than a knowledge gap. Brands know the allergen rules; the errors occur because label review processes check each language version independently rather than comparing them against each other, and because the specific highlighting requirement — bold or otherwise typographically distinguished allergen text — is easy to apply correctly in the source language and lose in translation.
The EU's General Product Safety Regulation (Regulation (EU) 2023/988), fully applicable since December 2024, adds a further compliance layer: where a labeling error triggers a product recall, brands are now required to follow a standardized recall notice template and, where possible, contact affected consumers directly — raising the operational cost of a labeling error that reaches the shelf.
For full depth on FMCG/CPG allergen labeling and PPWR packaging requirements, see the Food & FMCG Allergen and Packaging guide and the PPWR compliance guide.
The specific failure patterns recur across industries, even though the regulations differ:
The missed highlight. An allergen or a required warning is present in the correct wording but not formatted according to the highlighting or emphasis requirement — bold text for allergens under EU 1169/2011, a specific symbol size under ISO 15223-1. The content is technically present; the compliance requirement is not met.
The unpropagated correction. A change made to the approved master — a corrected dosage, an updated allergen declaration, a revised IFU instruction — is applied to one language version or market variant but not to the others, because each version was reviewed independently rather than compared against the master and against each other.
The consistency gap across packaging levels. Specific to medical devices, but structurally similar to any multi-level packaging compliance requirement: information that is correct at one level (the unit label) is not correctly reflected at another (case-level packaging), and no single review step checks all levels against each other.
The format-integrity failure. A conversion between file formats — PDF to Word, or a rasterized export — alters text that was correct in the source file: a character encoding change, a symbol replaced by a visually similar but incorrect glyph, text flattened into a non-machine-readable image. None of these failures involve anyone editing the content; they occur in the technical process of producing the final artwork file.
The wrong-baseline comparison. The final check before release compares the current file against the previous version — a delta review — rather than against the approved master specification. A delta review shows what changed since the last version; it does not show whether the current file, in its entirety, matches what was approved. An error introduced several revisions earlier, and never corrected, can survive multiple delta reviews undetected. (This failure pattern is explored in depth in a dedicated article.)
Despite the differences in what regulations require content-wise, the process requirements for demonstrating compliance are consistent across pharma, medical devices, and FMCG/CPG:
A version-controlled master document. Every industry's compliance model depends on there being a single, unambiguous, approved version of record — the master — against which every subsequent file is verified. Without a controlled master, "compliant" becomes a claim about a specific file rather than a verifiable state.
Systematic comparison before release. The final check before a label goes to print or a device ships needs to compare the release candidate against the approved master, not against the previous draft. This is the distinction between a delta review and a master comparison, and it is the single most consistent gap in labeling compliance processes across every industry covered in this guide.
A documented review trail. Under 21 CFR Part 11, EU GMP Annex 11, and equivalent frameworks, the systems used to review and approve labeling content must produce an audit trail — who reviewed what, against which version, when, and what the outcome was. This is not optional documentation; it is often the specific evidence a regulatory inspection asks for first.
Validation of any software used in the compliance process. Where a computerized system — including artwork comparison and proofreading software — is used to make or support a decision that affects product release, that system is within the scope of GxP validation requirements. A tool that performs comparison accurately but was never validated to GAMP 5 standards creates a compliance gap of its own.
A compliant labeling process, regardless of industry, rests on four practical components:
Master document discipline. The approved content — regulatory text, IFU, formulation-linked allergen declarations — is locked as the single source of truth before any artwork production begins. Every subsequent file, in every language and market variant, is measured against this master, not against each other or against the previous draft.
Automated comparison at the verification stage. Character-level text comparison, pixel-level graphic comparison, and — where relevant — barcode and Braille verification are run against the master before release. Automated comparison does not replace human judgment about what changes are intentional; it replaces manual visual comparison as the method of detecting what changed, which is a task human review performs unreliably at scale and under time pressure.
A cross-version, not sequential, multilingual review protocol. Every language version and market variant is compared against the master and against each other, not reviewed independently by different reviewers with no comparison step between them. This is the specific process change that catches the allergen-highlighting and IFU-propagation failures described earlier in this guide.
An audit trail from comparison through sign-off. Every comparison run, every deviation identified, and every resolution decision is captured automatically and tied to the specific document version involved — producing a review record that supports both internal quality processes and external regulatory inspection without requiring reconstruction after the fact.
Evaluating a platform to support this process? The Buyer's Guide to artwork verification software covers the specific criteria to look for.
Labeling compliance is, at its core, a verification problem: confirming that what was approved is what gets released, consistently, across every version and every market, and being able to demonstrate that confirmation happened. Content Compare runs that verification — text, graphic, barcode, and Braille comparison against the approved master, in a single validated session — across pharma, medical devices, and FMCG/CPG, with the audit trail built into every comparison.
See how labeling compliance verification works on your own documents. Request a demo at informait.com.