Key takeaways
- Serialization is a per-product decision, not a plant-wide switch. Most manufacturers run a hybrid, serializing high-consequence units and keeping low-risk inputs at batch level.
- Budget for aggregation and verification, not the mark. Printing a code costs cents. Linking each item to its case and pallet and confirming every code at line speed is where the costs accumulate.
- Confirm which mandate applies before you invest. Different countries and industry regulations require different serialization levels for different parts and products. Determine which mandates and serialization level applies to your industry and operations before implementing a new process.
What does serialization mean?
Serialization assigns a unique serial number to individual items, batches of products, or aggregated containers. It provides enhanced supply chain data, quality control measures, product recall efficiency, counterfeit detection, and regulatory compliance. Serialization is directly connected to tracking and tracing operations. Tracking monitors an item’s movement from its origin to the destination, while tracing documents how, when, and where an item was manufactured or processed.
That distinction matters because serialization exists on a spectrum. Each level of serialization comes with costs and an implementation strategy:
| Serialization Level | What Gets a Unique ID | Typical Use | Relative Cost and Complexity |
|---|---|---|---|
Item / instance (item-level serialization) | Every individual unit | Drug packages, EV batteries, safety-critical assemblies | High |
Batch / lot | A group made together | Bulk fasteners, coatings, low-risk food inputs | Low |
Aggregation (parent-child) | Unit linked to case, case linked to pallet | Full supply-chain track-and-trace and returns handling | Highest |
Table showing that cost and complexity rise sharply as identification granularity increases, from low-cost batch tracking, to high-cost item-level serialization, to the highest-cost aggregation model that links units to cases and pallets.
Expert Insight: Determining whether a part is serialized individually or at the batch level
Tomáš Minařík, Applications Engineer: "If we leave regulatory requirements aside, the deciding factor is typically the value of the product. The higher the product value, the higher the potential cost of a customer complaint, field failure, or recall. In these cases, serialized identification, together with the related processes, can help manufacturers investigate issues faster and identify affected products more precisely. This ultimately helps reduce losses and avoid unnecessarily broad corrective actions.
On the other hand, if products are manufactured in very large volumes and the value of each individual item is very low, implementing serialized identification may not be economically justified. For example, I have not yet seen serialized identification implemented on individual commodity components such as nuts and bolts."
Which regulations require product serialization in 2026?
Three regulations shape the serialization decision in 2026, and they point in different directions. In the U.S., the Drug Supply Chain Security Act (DSCSA) requires electronic, batch-level serial data for medicines. The stabilization period set by the Food and Drug Administration (FDA) ended when the deadline for wholesale distributors passed in 2025 and dispenser deadlines in 2026. The practical question is no longer whether to serialize, but how to do it well. Medical devices already require unit-level identity through the Unique Device Identification (UDI) system.
The main U.S. food-safety rule, the Food Safety Modernization Act Rule 204 (FSMA 204), requires traceability only at the lot or batch level, so producers trace a group of products rather than each individual unit. Its compliance date has been pushed back to July 20, 2028, giving the food industry more time to deploy compliance measures.
The newest driver is the European Union (EU) Battery Regulation (2023/1542). Starting February 18, 2027, every electric vehicle battery, light transport battery, and industrial battery above 2 kWh sold in the EU will need a digital battery passport that anyone can open with a QR code, and each passport must carry a serial-level identifier unique to that battery. This is the first digital product passport to take effect, and regulators have signaled that textiles and electronics will follow under the Ecodesign for Sustainable Products Regulation (ESPR).
| Regulation | Industry | Level Required | Status and Key Date |
|---|---|---|---|
| DSCSA | Pharma (US) | Package / item-level serial | Live; large dispensers since Nov 27, 2025; small dispensers exempt to Nov 27, 2026 |
| FSMA 204 | Food (US) | Lot-level | Compliance date moved to July 20, 2028 |
| EU Battery Regulation 2023/1542 | EV and industrial batteries above 2 kWh | Serial-level (unique battery ID) | Passport mandatory Feb 18, 2027 |
| UDI | Medical devices | Device-level identifier | In force |
Table comparing four traceability regulations, showing that mandates increasingly push toward unit-level serialization for pharma, batteries, and medical devices, while food traceability remains lot-level and its deadline has been pushed out to 2028.
Expert Insight: What is forcing manufacturers toward item-level serialization? What should manufacturers do now to prepare?
Tomáš Minařík: "One major driver of item-level serialization is the growing complexity of assemblies and manufactured products. In the event of a failure, item-level serialization can reduce risk by identifying which supplier delivered a specific subcomponent, and which operators were involved in assembling the final product. Accurately establishing liability can help prevent broad and costly recall actions.
Manufacturers should also closely follow the latest technological developments. Marking, machine vision, and code-reading equipment are making continuous strides to keep up with higher line speeds and more complex challenges."
Where are the costs in serialization?
Most serialization budgets are allocated to aggregation, full verification, and the data infrastructure that connects units to cases to pallets. Printing a package serial number costs cents. Confirming that every code is present, legible, and correctly matched at production speed is where costs accumulate.
Aggregation deserves its own budget line. Linking a unit to its case and pallet, then handling every exception, adds equipment and validated software on top of unit-level marking.
The recurring costs are the ones teams underestimate:
- Verification: Moving from sampling-based quality control to 100% inspection means reading and grading every code. Barcode verifiers grade print quality against ISO and GS1 standards so failures get caught in-line.
- Data infrastructure: This layer includes EPCIS repositories, cloud data exchange with trading partners, and master data management. On a fast line, codes can change five to six times a minute, so line speed and overall equipment effectiveness (OEE) take a real hit.
- Process and training: Standard operating procedures (SOPs) IT, warehouse, and even forklift operators all have to learn the serialized workflow.
Expert Insight: Most teams overspend on marking hardware. What's one line item that almost never makes the first budget draft?
Tomáš Minařík: "That’s true for the most part. At first glance, it may seem that simply printing a 1D or 2D code on the product is enough. However, this is a misconception. The line must also be able to read the code reliably, verify its quality or validate the data, and then, for example, link this information to a database or another higher-level system.
However, I have also seen cases where issues were caused by insufficiently robust or poor-quality marking technology. If the mark itself is not consistent, durable, or readable under real production conditions, even the best code reading system will struggle to deliver reliable results."
What do you actually get back from item-level serialization?
Item-level data enables recall precision, a credible defense against counterfeiting and diversion, and unit-level genealogy for faster root-cause analysis. When something goes wrong, you isolate the affected units instead of quarantining an entire production run.
Recall precision provides the most immediate value. A batch recall would rescind everything sharing a lot code, including thousands of good units. A recall using item-level serialization would target the exact units in question, which reduces scrap, waste, and limits reputational damage. The stakes scale with the product. Major automotive recalls have run into the billions once replacements and settlements are counted, and that tail risk is exactly what serialized containment manages.
Even if recalls aren't a concern, counterfeiting can justify the investment in serialization. The Organization for Economic Co-operation and Development (OECD) and the European Union Intellectual Property Office (EUIPO) put global trade in counterfeit goods at roughly $467 billion in 2021, about 2.3 percent of world trade. A unique serial number turns a product into something a distributor, regulator, or customer can authenticate.
Finally, there's genealogy – the benefit engineers value. Item-level data ties a single unit back to the machine settings, operator, and component lots that produced it. That's a sharper root-cause exercise than "somewhere in this batch," and it feeds the digital-twin traceability that Industry 4.0 and IIoT programs are built on.
Expert Insight: Can you share an example of a project that required serialization?
Tomáš Minařík: "One example comes to mind. It involved a large manufacturing plant with several separate departments, including stamping, welding, assembly, and quality. Whenever the quality department detected a defect on the final product during the end-of-line inspection process, a major investigation was initiated.
The challenge was that no department was willing to accept responsibility for the defect. As a result, the individual departments often debated where the issue had actually occurred and which process step was responsible.
To address this, the plant decided to implement item-level serialization together using vision inspection systems. In the final database, each part had its own unique serial number, inspection results from the output vision checks performed by each department, and even associated images.
This created a clear and objective traceability record for every product. It was no longer possible for one department to shift responsibility to another, because the data showed exactly where the product had been inspected, what the result was, and what the part looked like at each stage of the process."
Is item-level serialization worth it?
It depends on risk, and the reality is that most manufacturers land on a hybrid. Serialize the units where a recall, a counterfeit, or a warranty claim would hurt most, and keep low-risk inputs at batch level. Match the serialization level to the consequence of getting it wrong.
Work through the decision in this order:
- Check your mandate first. If DSCSA, the EU battery passport, or UDI applies, the level is decided, and the work is implementation.
- Run a mock recall. Quantify how many good units would be affected in a batch recall. That number is your exposure, and often the most persuasive figure in the business case.
- Score each line by consequence. High-consequence units earn item-level serialization. Low-risk inputs stay at batch. Expect a mix.
- Use the vision you have. If inspection cameras are already on the line, adding code verification is incremental, not a new implementation.
Serialization makes sense when the cost of not knowing which unit failed is higher than the cost of tracking every unit. For a growing list of products, regulators have already done that math for you. For everything else, a mock recall often reveals the answer.