# Pharmaceutical Serialization > Site directory and reading guidance: [llms.txt](https://wiki.skusavvy.com/llms.txt). Canonical URL: https://wiki.skusavvy.com/article/pharmaceutical-serialization Published: 2026-11-03T14:03:30.861Z Last updated: 2026-11-03T14:30:23.398Z Category: Supply Chain > This article is AI-assisted reference material. Verify important or time-sensitive claims against the cited sources; AI review does not establish independent factual verification. ## Overview Pharmaceutical serialization is the assignment of a unique serial number to an individual package of medicine, normally alongside a product identifier, batch or lot number, and expiration date. It enables supply-chain participants to distinguish one package from another and supports verification, investigations, and traceability. The [U.S. Drug Supply Chain Security Act (DSCSA)](https://www.fda.gov/drugs/drug-supply-chain-security-act-dscsa) and the [European Union’s medicine safety-features requirements](https://health.ec.europa.eu/medicinal-products/falsified-medicines/safety-features-medicinal-products-human-use_en) are major regulatory frameworks involving serialized identifiers. Other jurisdictions operate their own identification or track-and-trace rules; those regimes are not interchangeable with U.S. or EU requirements. Serialization is not, by itself, proof that a product is genuine: a number can be copied, and an apparently valid identifier must be considered alongside packaging integrity, transaction data, and investigation results. Its operational scope spans packaging, warehousing, distribution, dispensing, and the systems that exchange or verify product information. ## Etymology and Origins [“Serialize”](https://www.merriam-webster.com/dictionary/serialize) means, among other things, to arrange or publish in a series. In pharmaceutical practice, serialization refers to assigning serial numbers to packages, distinguishing individual packages from identification solely by product or manufacturing batch. A definitive first documented use of the term in this specific context is not established here. The terminology developed alongside efforts to prevent falsified medicines from entering legitimate supply chains. The EU’s [Falsified Medicines Directive (Directive 2011/62/EU)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32011L0062), adopted in 2011, established a legal basis for package safety features. In the United States, the [DSCSA](https://www.fda.gov/drugs/drug-supply-chain-security-act-dscsa) was enacted in 2013 as Title II of the [Drug Quality and Security Act](https://www.congress.gov/bill/113th-congress/house-bill/3204), which was signed on 27 November 2013, and established a phased approach to electronic, interoperable tracing of certain prescription drugs. ## Historical Development Before package-level serialization, medicine distribution commonly relied on product codes, lot numbers, paper records, and later computerized inventory systems. Batch information remained important for recalls and expiry control, but a batch identifier alone did not distinguish every package within it. * **1970s–2000s:** Commercial barcode standards and computerized inventory systems made machine-readable product identification more practical. In 2004, the FDA issued a [barcode labeling rule for certain human drug and biological products](https://www.federalregister.gov/documents/2004/02/26/04-4249/bar-code-label-requirements-for-human-drug-products-and-biological-products); this required product identification on covered labels, not the later DSCSA package-level serialization framework. Two-dimensional symbols subsequently supported compact encoding of additional data; the [GS1 DataMatrix standard](https://www.gs1.org/standards/gs1-datamatrix) is relevant to healthcare product identification. * **2011–2016:** The European Union adopted the [Falsified Medicines Directive](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32011L0062) in 2011. [Commission Delegated Regulation (EU) 2016/161](https://eur-lex.europa.eu/eli/reg_del/2016/161/oj) subsequently specified detailed rules for the unique identifier and anti-tampering device. * **2013–2019:** The U.S. Congress enacted the DSCSA in 2013, initiating phased requirements for product identification and tracing. In the EU, safety-feature rules became applicable in most member states on 9 February 2019. The delegated regulation also provided longer transitional arrangements for certain countries, including Greece and Italy. * **2020s:** Electronic exchange, package verification, and interoperable systems became more prominent as U.S. enhanced drug distribution security requirements were implemented. FDA has issued implementation guidance and policies, including phased or discretionary enforcement positions; organizations should check current FDA communications rather than assume that a single transition date applies to every trading partner or requirement. Key institutions include the U.S. Congress and Food and Drug Administration, the European Commission, and standards organization GS1. The cited legislation and standards are more reliable milestones than attributing the practice to a single inventor. ## Core Concepts A serialized package identifier typically combines a product code and serial number. Depending on the applicable regime, the machine-readable carrier also includes the batch or lot number and expiration date. Under the EU safety-features rules, covered packs generally bear both a unique identifier and a separate anti-tampering device. [GS1 DataMatrix](https://www.gs1.org/standards/gs1-datamatrix) can encode identifier elements in a compact two-dimensional symbol; the precise identifiers and data carriers required depend on the jurisdiction. A typical workflow is: 1. **Commission:** Generate or allocate a serial number, print it on the package, inspect the print, and record the package as validly introduced into the system. 2. **Aggregate where used:** Associate individual packages with a case, and cases with a pallet. Aggregation enables a parent scan to represent its recorded contents, but the association must be maintained if a container is opened or repacked. Aggregation is an operational practice where used; it should not be assumed to be required in the same way, or for the same products, in every jurisdiction. 3. **Exchange or verify:** Transfer required transaction information to trading partners or check the identifier against the relevant verification system. 4. **Investigate exceptions:** Isolate and investigate unreadable, unknown, duplicated, or otherwise suspect identifiers according to applicable procedures. 5. **Change status:** Record events such as dispensing, destruction, or other authorized status changes where required by the relevant system. [GS1 EPCIS](https://www.gs1.org/standards/epcis) is an event-data standard that can describe what happened to identified objects, and when and where. It is distinct from the barcode printed on a package and is not itself a legal requirement. Likewise, ordinary [lot and expiration-date management](https://www.skusavvy.com/docs/guides/lots-and-expiration-dates) is complementary to, but not a substitute for, package-level serialization. ## Regulatory Frameworks ### United States The [DSCSA](https://www.fda.gov/drugs/drug-supply-chain-security-act-dscsa) applies to defined categories of prescription drugs and trading partners, subject to statutory exceptions and regulatory policies. Its provisions address product identifiers, tracing information, verification, and the handling of suspect and illegitimate products. For covered products, the product identifier includes a standardized numerical identifier, lot number, and expiration date. Requirements differ by trading-partner role, and organizations should consult current FDA guidance and applicable exemptions when designing processes. ### European Union The EU framework generally requires covered medicines to bear a unique identifier and an anti-tampering device. Under [Delegated Regulation (EU) 2016/161](https://eur-lex.europa.eu/eli/reg_del/2016/161/oj), the unique identifier includes the product code, serial number, batch number, and expiry date, and verification and decommissioning occur at specified points in the supply chain, including dispensing, subject to the regulation’s detailed rules and exceptions. Product scope and obligations should be checked against current national implementation as well as EU law. The two frameworks should not be treated as interchangeable: the EU model centers on repository-based verification and decommissioning, while the U.S. framework includes requirements for interoperable electronic tracing and verification among trading partners. ## Warehouse and Distribution Applications At receiving, a distributor can compare the physical shipment with the expected product and transaction information, then investigate mismatches before releasing stock. At dispatch, recorded aggregation can help reconcile cases and pallets with their contents. If a case is broken for partial fulfillment, its parent–child relationships must be updated or rebuilt to prevent inaccurate records. Warehouse systems can support related controls such as [mobile scanning workflows](https://www.skusavvy.com/mobile-warehouse-management-system) and [lot and expiration tracking](https://www.skusavvy.com/docs/guides/lots-and-expiration-dates). When selecting equipment, check scanner and label compatibility against the required [barcode formats](https://www.skusavvy.com/docs/guides/barcodes), including the relevant [GS1 DataMatrix](https://www.gs1.org/standards/gs1-datamatrix) symbols. These capabilities should not be assumed to provide DSCSA or EU serialization compliance: buyers must independently verify serial-level functionality, data exchange, validation, and regulatory coverage. For example, a wholesaler receiving a case of 48 serialized cartons may scan the case identifier and use a trusted aggregation record to identify its contents. If five cartons are removed for an order, the system must reflect the changed case contents and preserve the applicable transaction and verification records. This is an illustrative workflow, not a substitute for checking the rules applicable to the shipment. ## Benefits, Challenges, and Best Practices Serialization can narrow investigations to affected packages, improve visibility into product movement, and make certain forms of diversion or falsification easier to detect. It also adds costs and complexity: packaging lines need suitable printing and inspection, trading partners must exchange consistent data, and unreadable codes or mismatched aggregation records can delay shipments. A valid serial number alone cannot establish physical authenticity if the identifier has been copied. Recommended practices include: * **Map obligations by market and role.** Document which products, facilities, and trading partners are covered; use the relevant [FDA framework](https://www.fda.gov/drugs/drug-supply-chain-security-act-dscsa) and [EU rules](https://eur-lex.europa.eu/eli/reg_del/2016/161/oj) as starting points, and do not assume one market’s data model satisfies another. * **Validate the physical and digital process.** Test printing, barcode readability, serial-number uniqueness, line rejection, aggregation, and recovery after equipment or network failure. Include damaged labels and partial-case handling in acceptance tests; the [GS1 DataMatrix standard](https://www.gs1.org/standards/gs1-datamatrix) is a starting point for symbol requirements. * **Define exception handling.** Quarantine suspect or mismatched goods, preserve evidence, and assign investigation and escalation responsibilities. Distinguish a data mismatch requiring investigation from a confirmed illegitimate product; follow the applicable [FDA framework](https://www.fda.gov/drugs/drug-supply-chain-security-act-dscsa) or [EU rules](https://eur-lex.europa.eu/eli/reg_del/2016/161/oj). * **Test partner interoperability.** Agree on identifier formats, event semantics, exchange protocols, and reconciliation procedures before production use; [EPCIS](https://www.gs1.org/standards/epcis) provides a common event-data standard where the parties choose to use it. * **Maintain controlled records.** Restrict access, retain audit trails according to applicable requirements, and periodically reconcile physical inventory with serial and aggregation data. ## Source links - [Drug Supply Chain Security Act]() - [Safety Features for Medicinal Products for Human Use]() - [Falsified Medicines]() - [GS1 DataMatrix]() - [Commission Delegated Regulation (EU) 2016/161]() - [GS1 EPCIS Standard]() - [Lots and Expiration Dates]() - [Mobile Warehouse Management System]() - [Serialize]() - [Bar Code Label Requirements for Human Drug Products and Biological Products]() - [Barcodes Guide]() - [Directive 2011/62/EU (Falsified Medicines Directive)]() - [H.R.3204 — Drug Quality and Security Act]()