DSCSA Serialization Labels: What NJ Pharmaceutical Manufacturers Need in 2025

New Jersey is the beating heart of American pharma. The Route 1 corridor between Princeton and New Brunswick — “Pharma Alley” — is home to Pfizer, Johnson & Johnson, Bristol Myers Squibb, and dozens of smaller manufacturers and contract packagers. For all of them, one federal law decides what has to appear on the label: the Drug Supply Chain Security Act.

The Four Data Elements Every Package Needs

FDA requires that each saleable unit — the smallest package sold to a dispenser — carry a product identifier with four elements, encoded in a GS1 DataMatrix barcode and repeated in human-readable text. Tap any element for the specifics your serialization system has to get right.

National Drug Code (NDC) — as a GTIN

Your NDC is encoded as a GTIN-14 using GS1 Application Identifier (01). This is the product-level identifier — it says what the drug is. It’s the one element that stays constant across a batch, which is why it’s often part of the pre-printed artwork rather than the variable field.

Serial Number — unique to every package

Encoded with Application Identifier (21), the serial number is a unique value for each individual package, and it must stay unique within each NDC for a minimum of 5 years. This is the element that makes serialization serialization: no two packages share one, so it can’t be pre-printed en masse — it changes label to label as variable data.

Lot Number — the batch identifier

Encoded with Application Identifier (10), the lot number ties a package back to its production batch. It’s essential for targeted recalls and quality tracing, and it typically prints as variable data alongside the serial number and expiration date.

Expiration Date — encoded YYMMDD

Encoded with Application Identifier (17) in YYMMDD format. Like the lot number, it usually prints as a variable field so it can update per production run rather than locking you into a single dated label stock.

Why a 2D GS1 DataMatrix, and not a linear barcode

Older pharma labels used linear barcodes (Code 128 or Code 39) for NDC and lot data. DSCSA mandates the GS1 DataMatrix — a two-dimensional matrix symbol — for three reasons. Density: it packs all four required elements plus AI delimiters into a symbol small enough for unit-dose packaging. Error correction: built-in redundancy lets the symbol scan even when it’s partially smudged, scuffed, or worn — routine hazards in a pharmacy. GS1 standardization: GS1 syntax (Application Identifiers, GTINs derived from registered NDCs) means any GS1-compliant scanner in the chain, from your line to the dispensing pharmacy, can read it.

These four elements have to appear on every package — from the smallest unit like a single blister card, up through intermediate packaging and homogeneous cases.

Size, Print Quality, and Human-Readable Text

A DataMatrix is only compliant if it actually scans. Three requirements decide that.

Minimum symbol size. FDA guidance and GS1 standards specify a GS1 DataMatrix of at least 5mm × 5mm — roughly 0.2” × 0.2”. On unit-dose packaging (oral solid blisters, unit-dose syringes, prefilled pens), that’s a real design constraint. Where the 5mm minimum can’t be met without crowding out other required labeling, FDA allows a reduced-size symbol with demonstrated scan reliability.

Print quality. GS1 requires DataMatrix symbols to meet ISO/IEC 15415 verification grades, and Grade 1.5 or higher (on a 0–4 scale) is typically required for pharmaceutical applications. This is not a “looks fine to me” judgment — it’s a graded, measured result.

Human-readable text. Alongside the machine-readable symbol, FDA requires the same four data elements printed in human-readable text next to the barcode, so a pharmacist can cross-check by eye during dispensing.

Saleable Returns: The Barcode Has to Last

One of the most operationally significant DSCSA requirements now in full effect is verifying saleable returns before redistribution. When a wholesale distributor takes back a returned prescription drug, they must verify the product identifier — by scanning the DataMatrix or through a system-to-system verification request — before it goes back into saleable stock.

That means your DataMatrix has to stay scannable across the entire product shelf life, including after the package has been opened, handled, and shipped back. Labels that degrade, peel, or smudge on the package surface don’t just look bad — they create supply chain disruption for your distributor customers.

Serialization Is a Variable-Data Problem

Because every package needs a serial number that’s unique within its NDC — and usually a lot number and expiration date that change per run — the serial, lot, and expiration fields all have to print as variable data. This is the piece that makes pharma labeling different from a standard flexo run, and it’s a capability we build the whole label design around. There are two common approaches:

Inline variable-data printing at your facility

A digital or thermal-transfer print engine on your packaging line applies the serialized fields to a pre-printed label at packaging time. We produce the fixed elements — brand, NDC, inactive ingredients, warnings — on our flexographic presses, and your line prints the variable fields inline. See more on our variable data printing capability.

Pre-serialized labels from us

If you don’t have inline printing, we can pre-serialize — printing unique serial numbers on every label in a roll or sheet, sequential or algorithmically generated. Your serialization system tracks which serial-number range shipped in which batch of labels.

Either way, you need a serialization management system that can generate unique serials, retain records for 6 years post-transaction, and respond to FDA verification requests.

Built for the NJ Pharma Supply Chain

New Jersey manufacturers have supply-chain quirks that shape label design:

• Cold chain. Biologics, insulin, and other cold-chain products need labels that keep the DataMatrix readable through temperature cycling. We test adhesion and print quality through 2°C–8°C refrigeration cycles and at -20°C for frozen biologics.
• Contract packaging. If you’re a CMO labeling for multiple manufacturers, your serialization system has to juggle multiple NDC/GTIN pools and keep chain-of-custody records per DSCSA.
• Inspection readiness. NJ has a high density of FDA district inspectors and frequent facility inspections. Your barcode verification results and serialization batch records should be retrievable on demand.

We’ve been printing pharmaceutical labels for NJ manufacturers since 1986, with hands-on experience in GS1 DataMatrix, NDC barcode printing, and variable-data serialization — and we back every order with ANSI/ISO barcode verification and inline video web inspection.

---

DSCSA compliance is non-negotiable, and it succeeds or fails on the label itself. If you’re mapping out serialization for a new product or tightening up an existing line, let’s talk it through. Call (908) 495-6235 or request a quote — we’ll review your requirements and spec labels that scan reliably from your line to the pharmacy shelf.