Four Elements of the DSCSA Product Identifier

The Drug Supply Chain Security Act (DSCSA) uses product identifiers to support package-level tracing and verification of covered prescription drugs as they move through the supply chain. The identifier is more than an NDC. It combines product identity, a unique serial, a batch identifier, and the package’s expiration date.

How the four elements work together

Think of the NDC as the product description, the serial number as the package-level identity, the lot as the manufacturing group, and the expiration date as the time limit. A pharmacy may see many packages with the same NDC and lot; each package’s serial number makes the identifier unique at the package level. A lot number alone cannot distinguish two packages in the same batch, and an NDC alone does not identify which individual package is being checked.

Where the identifier appears

For a covered individual saleable package, the product identifier is generally shown in human-readable form and in a machine-readable 2D data matrix barcode. The data need to match. Scanning lets a trading partner read the encoded elements efficiently; staff should still know how to interpret the printed NDC, serial, lot, and expiration fields when a barcode is damaged or a discrepancy appears. Packaging and product categories can have specific statutory exceptions, so the DSCSA scope rules still matter.

Do not confuse the saleable package with its case

The barcode requirement depends on the packaging level. FDA guidance explains that an individual saleable package generally carries a 2D data matrix, while a homogeneous case may use a linear barcode or a 2D data matrix. A case is not a substitute for identifiers on the packages inside it. Read the scenario carefully: a bottle intended for individual sale and an outer case containing multiple bottles are different units.

The human-readable portion matters too. When a code is unreadable, staff should follow pharmacy policy to hold and escalate the product or transaction for resolution. Manually entering the printed elements may help investigate, but it does not authorize changing the identifier or bypassing verification procedures.

Product identifier versus transaction information

The product identifier is printed on the package and is not the entire DSCSA tracing record. Transaction information, transaction statements, authorized-trading-partner checks, verification, and electronic interoperable tracing requirements address the transfer and history of product through the supply chain. Do not answer a question about package data with the contents of a transaction statement, or assume that scanning four fields alone completes every DSCSA obligation.

How a technician uses the information

• Match the product and package to the correct NDC and strength before processing or investigating a discrepancy.
• Use lot number and expiration date when checking inventory, recalls, returns, or short-dated stock.
• Treat a serial mismatch, unreadable code, or verification alert as an escalation issue under pharmacy policy.
• Do not alter, reuse, or invent identifiers when product is repackaged; follow the applicable DSCSA, labeling, and pharmacy procedures.
• Refer unresolved product tracing questions to the pharmacist or designated compliance contact.

Exam traps

• Leaving the serial number out and listing only NDC, lot, and expiration.
• Saying the NDC uniquely identifies an individual package.
• Confusing serial number with lot number: one is package-specific, the other identifies a batch.
• Treating the barcode as a substitute for the human-readable data or the broader tracing system.
• Assuming DSCSA applies identically to every drug, package, and trading partner without checking scope and exceptions.

Key takeaway

Memorize NDC + serial number + lot number + expiration date. The NDC tells you what product, the serial tells you which package, the lot tells you which batch, and the expiration date tells you when it expires.