Labeling in manufacturing is the printing and application of product identification, barcodes, lot and date codes, serial numbers, and required regulatory text, onto items and their packaging, so every unit can be scanned, tracked through the supply chain, and proven compliant. A label is small, but a wrong one can stop a shipment or trigger a recall.

On the floor, labeling sits at the end of the line where it is easy to treat as an afterthought, until a customer rejects a pallet for an unreadable barcode, or a regulator flags a missing allergen line. This guide covers the main labeling methods, what regulators require on a label, what serialization is and when you need it, how to verify a label is actually correct before it ships, and how labeling ties into plant-wide traceability.

What Are the Main Labeling Methods?

Manufacturers apply identification four common ways, chosen by speed, surface, and how permanent the mark must be.

Most plants mix methods: a pressure-sensitive consumer label on the unit, a print-and-apply case label on the shipper, and a direct-printed date code on the primary pack. The failure modes differ, a peeled label, a blurred ink-jet code, a misencoded RFID tag, but the operational goal is the same: the right, readable identifier on the right unit, every time.

Anatomy of a compliant case labelWhat is actually on the labelPRODUCT NAME · 12 x 500 mL(01) GTIN barcodeLOT: 4471-BDATE: 2026-07-16EXP: 2027-07-16serialized 2D codeHuman-readable + machine-readable, lot/date, and a unique serial in one label
A compliant case label carries human-readable text, a scannable barcode, lot and date codes, and, where required, a unique serialized 2D code.

What Goes on a Compliant Label?

The required content depends on the product, but every regulated label carries the same idea: enough information for a buyer to identify the product and for the supply chain to trace it. Two of the most common regimes in U.S. plants are food and medical devices.

RequirementFood (FDA)Medical device (FDA)
IdentityStatement of identity (product name)Device name and labeler
QuantityNet quantity of contentsPackage quantity
CompositionIngredient list + Nutrition FactsNot applicable
Safety textAllergen "Contains" statement (9 major allergens)Warnings, sterilization status
Traceability codeLot / date code (recommended, often required)UDI, human- and machine-readable
Machine-readableGS1 barcode (GTIN)UDI barcode via an FDA-accredited agency

On the food side, the U.S. Food Allergen Labeling and Consumer Protection Act (FALCPA) requires plain-language declaration of major allergens; the FASTER Act added sesame as the ninth major allergen, effective January 1, 2023. On the device side, the FDA Unique Device Identification (UDI) system requires most device labels to carry a UDI in both human-readable and machine-readable (AIDC) form, with the device-identifier portion submitted to the FDA's GUDID database. Getting these fields right is a quality-system obligation, not a graphics choice, which is why labeling belongs inside your quality management system.

What Is Serialization, and When Do You Need It?

Serialization is giving each individual unit a unique identifier, not just its product code and lot, but a serial number that belongs to that one item. A lot code says "this came from batch 4471"; a serial says "this is unit 4471-000238 and no other unit shares that number." That uniqueness is what lets you track, authenticate, and if necessary recall a single item rather than a whole batch.

You need serialization when regulation or customers demand item-level traceability: pharmaceuticals under track-and-trace rules, many medical devices under UDI, and increasingly high-value or counterfeit-prone goods. Serialization raises the operational bar because every unit now needs a unique code printed, applied, and verified in-line at full speed, a natural fit for print-and-apply with vision verification. It also feeds anti-counterfeiting and warranty programs, since a scanned serial can be checked against a database of what was legitimately produced.

The jump from lot-level to item-level tracking is bigger than it looks. A lot code is printed once per batch and reused across thousands of units; a serial changes on every unit, so the printer, the applicator, and the verifier all have to stay perfectly in step with the line. If one unit gets two serials, or two units share one, the whole point is lost, so serialized lines lean hard on in-line verification and on a system that reconciles the serial printed against the serial actually shipped. Done well, that reconciliation is also a gift to the aftermarket: a scanned serial can pull up the exact build, warranty status, and service history of one specific item.

How Do You Verify a Label Is Correct Before It Ships?

Verification means confirming, in-line, that the label printed, applied, and scans correctly, before the product leaves the building. A printed barcode is not automatically a readable barcode; ink starvation, label wrinkle, low contrast, or a quiet-zone violation can drop a code below the grade a scanner needs. Barcode verifiers grade print quality against ISO standards on an A-to-F scale so a plant can catch a failing code at the printer instead of at the customer's dock.

The print-apply-verify-reject loopCatch the bad label before it ships1 · PRINTlive lot/date/serial2 · APPLYto moving product3 · VERIFYscan + gradeA–F qualityPASS →to shippingREJECTdivert + alertgrade below spec?
An in-line loop prints, applies, and grades every label, diverting failed units and alerting the line, so a bad code never reaches the customer.

A mislabel that gets caught in-line is a minor stop; one that ships is a customer complaint or a recall. Treating labeling as a mistake-proofed step, a poka-yoke that will not let a wrong or unreadable label pass, is far cheaper than sorting a returned pallet. Labeling faults also show up in the numbers: repeated reject-and-clear cycles at the labeler eat into line availability, which is exactly the kind of loss an OEE calculation surfaces.

How to Prevent Mislabels: A Control Workflow

Most labeling errors trace to the same handful of gaps. This ordered workflow closes them.

  1. Master the label data. Keep approved label templates and the fields that fill them (GTIN, allergens, net weight) in one controlled source, not in a printer someone edited last shift.
  2. Bind the label to the job. Pull lot, date, and serial from the live work order, so the label reflects what is actually running, not the last product on that line.
  3. Prove the first label. A first-off check against the print and spec before the run, the labeling equivalent of a first-article inspection.
  4. Verify every label in-line. Grade the barcode and check placement automatically; divert and alert on any failure.
  5. Log what shipped. Record which label, lot, and serial went on which unit, so a later question, or a recall, can be answered in minutes.

Why Do Mislabels Cause Recalls?

Because a wrong label is a safety defect, not a cosmetic one. If a package fails to declare an allergen it contains, a consumer with that allergy has no warning, so an undeclared allergen from a labeling error is treated as seriously as contamination. Undeclared allergens are consistently among the leading reasons for FDA food recalls.

FactDetailSource
Major food allergens9, milk, egg, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, sesameFDA FALCPA
Sesame added9th major allergen under the FASTER Act, effective January 1, 2023FDA Food Allergies
Device UDI formatHuman- and machine-readable UDI on labels; DI submitted to GUDIDFDA UDI System

The lesson is that labeling errors are a top-tier operational risk, not a printing nuisance. A plant that verifies labels in-line and logs what shipped turns a potential recall into a caught-and-cleared reject.

How Does Labeling Connect to Traceability and the Plant System?

A label is only useful if the code on it points to real records, which lot, which line, which shift, which inspection results. That link between the physical mark and the digital history is the whole point of traceability and it is where labeling stops being an end-of-line task and becomes part of the plant's operating system.

Most plants still reconcile labels against paper logs and separate label software, so answering "prove which units carried lot 4471" means an afternoon of digging. Harmony connects the labelers, line equipment, and the paperwork around them into one live record, so what was printed, verified, and shipped is captured at the source rather than re-keyed, no rip-and-replace (see how the platform works). That same connected record is what keeps downtime at the labeler visible and folds labeling into a broader lean effort to remove waste at the end of the line. For a look at replacing paper logs with live production data, read the CLS case study. Labeling is also front and center in medical device manufacturing where UDI and serialized traceability are non-negotiable.