When a contract packer runs a serialized pharmaceutical line, the marketing authorisation holder (MAH) keeps legal responsibility for the product and its serialisation data. The contract packer can perform agreed line tasks such as printing, verification, commissioning, reject handling, and reporting. An authorised, affiliated onboarding partner may upload data to the European Hub for the relevant MAHs. This means activities can be delegated, but accountability must stay clear from the start, because unclear roles often lead to delays, data issues, and slower batch release.
• The MAH remains accountable for the medicine and the serialisation data, even when line activities are outsourced.
• The contract packer can execute agreed tasks on the line, but it does not take over legal responsibility.
• Teams should define number ownership, system access, status rules, and returned records before the first batch.
• Batch close must include a reconciliation of used, unused, rejected, damaged, and scrapped codes.
• A clear technical agreement and quality agreement help prevent errors during routine production and rework.
Why serialization with a contract packer starts with a responsibility split
Serialization with a contract packer works best when the first decision is about responsibility. Teams usually ask who owns the serial numbers, who uploads FMD data, and who stays responsible when an external line is used. The answer is simple at a legal level: the MAH remains accountable for the product and for the marketing authorisation holder serial data linked to it. An independent contract packer can carry out agreed operational steps, but it does not become legally responsible just because it prints and verifies codes.
If your team wants a basic outsourcing view before going deeper into serialisation, it helps to read about what co-packing means first. This matters because the operating model and the data model are inherently linked. Once outsourcing starts, both the physical batch flow and the data flow must work together under one agreed process.
In some setups, a European Hub onboarding partner uploads data on behalf of the relevant MAHs. This can answer part of the common question about who uploads FMD data. However, the upload route does not change accountability. Therefore, CMO serialisation responsibilities should be written clearly into the project documents before the first batch is planned.
After the split is defined, outsourced execution becomes easier to control. We provide pharmaceutical contract packaging with serialisation as one route for line execution and reporting. This supports day-to-day operations, but it does not shift regulatory responsibility away from the MAH.
What serialization with a contract packer means for data ownership and system access
Product master data and number ownership
Before production starts, teams should agree on product master data, coding fields, artwork points that affect the printed code, and any pack hierarchy needed for the target market. They should also define the number source. During serialization with a contract packer, this step is critical because number ownership affects system setup, approvals, and later reconciliation. Some customers provide serial number ranges. Other approved models allow for authorised generation and serial number randomisation within agreed controls.
These points should not stay general. The MAH serial data, the source of numbers, the approval steps, and any market-specific coding requirements should all match the approved operating model. If the number model is vague, release decisions and investigations become harder, as teams cannot easily confirm what happened to each unit and its status.
Interfaces and access rights
The data exchange model should be defined in the technical agreement and the contract packer's quality agreement. There is no single standard for every customer because file types, handover points, and approval rules can differ. For this reason, access rights should be agreed upon before validation or before the first engineering batch. Teams should know who sends data, who receives it, who approves it, and who can trigger serial status changes.
System visibility also matters. Some users may need line-level event access, while others only need approved reports after batch close. In co-packer serialisation, a line can perform well physically while the data process still fails in the background. Therefore, access control and interface rules reduce risk by making the process easier to monitor and investigate if an exception appears.
How the line is prepared for a serialized batch
Line setup and test prints
Once data, ownership, and interfaces are agreed upon, the line must be prepared for routine use. This usually includes printer setup, camera setup, line control checks, test prints, test scans, and sample packs. The camera recipe should be approved before the batch begins, as the reject logic must match the printed code, the pack layout, and the expected read quality. If those settings are not aligned, false rejects or missed defects can appear during the batch.
Teams should check print quality, code position, readability, and the response to failed reads. A saleable pack should only be commissioned after the agreed checks are passed. In this way, contract packaging serialisation starts from a controlled line state instead of relying on manual fixes later.
Repeatable execution in routine batches
A successful test run is useful, but routine performance matters more, because commercial production creates more variation and increased pressure on speed, handling, and reporting. We support this with commercial packaging designed for reliable processing. This helps because a pack that runs well at scale reduces avoidable stops, rejects, and extra handling. That is important when serialization with a contract packer must work perfectly every time, not only under test conditions.
How serialization with a contract packer runs during batch execution
Printing, verification, and commissioning
During the batch, the line prints the required code, and the vision system checks whether it is present, readable, and linked correctly to the batch process. If all agreed checks pass, the pack can be commissioned according to the approved model. Serialization with a contract packer depends on strong control at this stage because line events directly affect serial status and subsequent reporting.
The contract packer may receive authorised number ranges or generate numbers under the approved setup. In some models, it may also apply serial number randomisation if this has been agreed upon in advance. What matters is that every action follows the authorised process, the defined access rights, and the approved product data. If any of those elements are unclear, an apparently successful run can still create a data problem later.
Reject handling and code status control
If a code does not print correctly or does not read, the pack should be rejected through the approved logic. If a pack is damaged, destroyed, or scrapped, the matching serial status must also be handled in the agreed way. This is where scrapped code decommissioning becomes important, as the physical pack result and the system status must stay aligned.
A simple example shows why this matters. If one carton has a blurred code and the camera rejects it, that carton should be separated, recorded, and processed under the batch rules. The serial status should then follow the approved path so the final serial number reconciliation report matches the real pack flow. Without this link between physical handling and data status, investigations and release checks become much more difficult.
What serialization with a contract packer requires at batch close
Reconciliation and final records
At batch close, numbers must reconcile. This means used, unused, damaged, rejected, and scrapped codes should be counted and matched to the batch outcome. During serialization with a contract packer, reconciliation is one of the most important controls because it confirms that the line result and the data result match. A clear serial number reconciliation report helps the customer confirm that no status gap remains between the physical stock and the digital record.
The MAH will usually need batch records, line reports, exception logs, and serialisation reports before its own release process can continue. The exact returned record set should be defined before production starts. If that list is missing or unclear, release can slow down even after a technically successful run, because quality teams still need evidence of what was printed, what was rejected, what changed status, and what remained unused.
One partner across the packaging chain
We work as a single partner across the packaging chain: design, manufacturability, component production, primary and secondary packing, and serialisation. This can reduce handovers between a pack designer, component supplier, coding party, and contract packer. Fewer handovers often help because packaging choices made early in the project can affect print quality, camera performance, reject handling, and reporting later on the line.
You can see this joined process in the 4-in-1 packaging case. It is a useful example of a complex packaging project where clear procedures and records matter when several steps must work together.
Exceptions, rework, and data control
Rework and opened cases
Exceptions should be discussed before the first batch, as rework decisions affect both the pack and its serial status. Teams should ask what happens if a printed code fails to read after printing, how that event is recorded, and what status path applies next. During pharma serialisation rework, physical handling and data handling must stay connected throughout the event.
Opened case work needs the same discipline. If one pack inside a case is rejected, the case may need to be opened, separated from its original relationship, and rebuilt under a controlled process. The rebuilt result should be linked back to the batch record and the correct serial status history. This helps during later reviews because every changed unit still has a traceable story.
Data protection, retention, and deviation handling
Serial data should be stored, protected, backed up, and kept for the agreed period. Teams should know where records are held, how they are secured, and how long they remain available. This matters because an investigation can begin long after the batch has left the line, and missing records can delay both root-cause reviews and corrective actions.
Deviation handling should also be clear across company boundaries. The packer, quality teams, and the MAH should know who raises the event, who investigates it, who approves the action, and who receives final closure. These steps should be documented as part of CMO serialisation responsibilities so that an issue does not stall between organisations. Strong communication helps because many issues surrounding serialization with a contract packer are solved faster when physical evidence and data evidence are reviewed together.
Supplier checklist for serialization with a contract packer
Before outsourcing a batch, teams should review the same practical questions with every potential partner. This makes supplier comparison easier for procurement, quality, supply chain, and packaging teams because each area can check the same control points. It also helps expose gaps before transferring production to an external line.
• Ownership: Who owns the serial numbers, and what approved model is used for supply or generation?
• Upload route: Who uploads FMD data, and is a European Hub onboarding partner involved?
• Status control: What serial statuses can the contract packer apply during production and exception handling?
• Reject logic: How are rejects, damaged packs, destroyed packs, and unreadable codes handled on the line and in the data?
• Reconciliation: What is the method for matching used, unused, damaged, rejected, and scrapped codes at batch close?
• Rework: What happens if a case is opened, disaggregated, and rebuilt?
• Returned records: Which reports, logs, and reconciliation files come back after the batch?
• Agreements: What is defined in the technical agreement, and what is defined in the quality agreement?
• Deviation handling: How are events escalated, investigated, approved, and closed across company boundaries?
If you want to review your current model with us, you can discuss contract packaging serialisation with our team. Please bring the product markets, batch plan, data model, and quality agreement status, as these points shape the right setup from the start.
FAQ
Who owns the serial numbers when a contract packer runs the line?
Ownership depends on the approved setup, but accountability stays with the MAH. A contract packer may handle authorised number ranges or generate numbers under the agreed process. Running the line does not transfer legal responsibility for the product or its serialisation data.
Who uploads FMD data?
The upload route depends on the approved onboarding model. An authorised, affiliated onboarding partner may upload data to the European Hub for the relevant MAHs. The task can be arranged in different ways, but the MAH remains accountable for the data.
What does a contract packer usually do in a serialised batch?
The packer can carry out agreed tasks such as printing, camera verification, commissioning, reject handling, reconciliation support, and report return. The exact scope should be defined before production, because a contract packer can execute many activities while the MAH still keeps legal accountability.
What records should come back after batch close?
The customer usually needs batch records, line reports, exception logs, and serialisation reports. It may also need a final reconciliation output for used, unused, damaged, rejected, and scrapped codes. The exact record set should be listed in the technical agreement and quality agreement before the batch runs.
Why is reconciliation so important?
Reconciliation confirms that the physical packs and the serial data match. This matters because release decisions depend on reliable evidence. If used, rejected, damaged, or scrapped codes do not match the final stock outcome, the MAH may need further investigation before release can continue.
Request a free sample now!
