← All insights
CMOs and CPOs · Serialization

Serialization Across Customers: A Guide for CMOs and CPOs

Create a repeatable site process with clear customer responsibilities, controlled configurations, and practical testing.

Hakile Life Sciences Advisors

Contract manufacturers and packagers can face different serial number arrangements, packaging structures, and system interfaces for each customer. The goal is a repeatable site process with clearly documented differences for each engagement.

Agree who owns each activity

Before configuration begins, identify who approves product data, allocates serial numbers, records packaging results, sends messages, handles rejections, and approves corrections.

Keep the quality agreement and technical specification consistent. FDA’s guidance explains that a quality agreement cannot transfer away a party’s applicable CGMP responsibilities. See FDA’s contract manufacturing guidance.

A useful responsibility matrix names the process owner, support contact, escalation route, and decision authority for each activity.

Control the customer configuration

Document the approved setup for each customer in one profile:

  • Products, packaging levels, pack quantities, lot and expiry formats.
  • Serial number allocation, uniqueness controls, and reconciliation.
  • Site identifiers, message formats, endpoints, and security settings.
  • Required events, timing, processing confirmations, and correction rules.

Reconcile this profile with line, site, enterprise, and customer systems before the first packaging order. Distinguish standard packaging quantities from the actual serial numbers packed into a specific case.

EPCIS separates the read point, business location, and source or destination information. Map each field to its intended meaning rather than repeating one site identifier throughout the message. See the GS1 EPCIS standard.

Test the production workflow and recovery

Use representative products and customer configurations. Cover commissioning, rejected packs, rework, unused serial numbers, and shipment matching. If aggregation is used, include opening, rebuilding, and partially filling cases.

Also test unavailable endpoints, duplicate messages, and rejected data. Define the evidence that confirms successful processing, plus the conditions for a production stop, shipment hold, and controlled restart.

Illustrative scenario: One package is replaced in a completed case. The quantity remains unchanged, but the contents have different serial numbers. The test checks that the revised relationship reaches every system that relies on it.

Keep market responsibilities distinct

For EU supply, establish the route from the packaging site to the customer’s Onboarding Partner, or OBP. EMVO states that delegation can occur only under the OBP’s full control; it does not grant independent access to third parties acting as delegates. See EMVO’s CMO delegation guidance.

Customer receipt of a production file does not confirm completion of all required EU repository activities. Agree which processing results the customer must check and who follows up on rejected uploads.

Maintain evidence as customers change

Assess new products, customer settings, mappings, and software releases before use. Reuse approved test evidence only where the impact assessment supports it.

For systems within EU GMP scope, Annex 11 addresses validation, interfaces, and controlled changes. Apply it according to the system’s regulated use. See EU GMP Annex 11.

The Hakile team helps CMOs and CPOs align customer requirements, design and coordinate interfaces, test production scenarios, and organize support responsibilities.

Discuss your customer serialization setup.

Put perspective into practice

Explore what this means for your operations.

Discuss your challenge →