How cosmetics contract manufacturers manage batch records for multiple clients
When you are producing for 20 different brand clients in one facility, paper batch records do not scale. Here is what managing batch records across multiple clients actually looks like, and what software needs to handle.
How cosmetics contract manufacturers manage batch records for multiple clients
When you are producing for 20 different brand clients in one facility, paper batch records do not scale. Here is what managing batch records across multiple clients actually looks like, and what software needs to handle.
Why multi-client batch records are uniquely complex
A single-brand cosmetics manufacturer has one batch record template, one quality system and one set of release criteria. A cosmetics contract manufacturer has none of those luxuries. Every brand client arrives with its own preferred batch record format, its own retained sample protocol, and its own list of in-process checks the QA team insists on seeing on the certificate.
The complexity compounds with markets. The same emulsion produced for a UK indie brand and an EU prestige client may need two different sets of documentation: SCPN evidence for the UK SKU, CPNP-supporting batch data for the EU SKU, and FDA cGMP / MoCRA-compatible records if either brand is shipping into the US. Toxicology references, allergen disclosure positions and stability data all sit alongside the production record because the client expects to see them attached to the batch they receive.
QC protocols differ too. One client wants viscosity at 25°C and pH on every batch. Another wants both, plus a microbiological release before dispatch. A third wants the analyst signature, the instrument serial number and the calibration date on the certificate of analysis. The contract manufacturer who tries to operate one universal template ends up producing the lowest-common-denominator record and then re-keying everything client-by-client at release.
What breaks down with paper
Paper survives in a single-brand environment. In a CMO it falls over in four predictable ways.
The first is re-keying. The operator fills in the paper traveller on the floor. Days later, someone in QA types the same data into the client's template, often from handwriting that has already gone home for the weekend. Every transcription is a place an error can land, and every error costs a release.
The second is version control. Client A revised the batch record format three months ago. The pre-printed travellers in the operator's office still carry the old version. Nobody noticed until the audit.
The third is audit prep time. When an ISO 22716 or MoCRA inspector arrives, three weeks of evenings go into collating travellers, lining them up against QC certificates and chasing missing signatures. The cost of paper is mostly invisible until the auditor walks in.
The fourth is format inconsistency. Two operators on two shifts capture the same in-process check in two slightly different ways. The reviewer can usually work out what was meant. The client's auditor cannot.
What electronic batch records need to do in a CMO environment
In a contract manufacturing environment, an electronic batch record (EBR) has to do more than digitise the paper traveller. It has to handle client-specific templates without forcing the floor to learn 20 different workflows. The operator should see one consistent shop-floor experience; the client-facing batch record format should be generated at close-out, automatically, from the same underlying data.
It has to be connected to the QMS. When an in-process check fails, the deviation needs to raise a QMS event in the same system, against the same batch, with the same data behind it. Manual handoffs between EBR and QMS are where deviations get lost.
It has to handle lot traceability per batch. For any finished SKU, the system needs to walk backwards from dispatch through filling, semi-finished bulk, raw material lot and supplier in a single query. Adverse event investigations under MoCRA and recall responses under ISO 22716 both depend on this.
And it has to be audit-ready by default. Continuous timestamped audit trail, controlled access, immutable records. Not a feature you switch on for the audit, but the baseline state of every batch.
What to look for in batch record software for a contract manufacturer
The single biggest decision is whether to buy EBR as a standalone tool or as part of the production system.
A standalone EBR slots in alongside the existing ERP, MES, LIMS and QMS stack and adds the batch record layer. The pitch is appealing on a slide. In practice, the standalone EBR has to be integrated to the formulation system, the inventory system, the QC instruments, the QMS and whatever the client uses for purchase orders. Each integration is a project. Each integration is a place the data can drift. And every time a client asks for a tweak to their batch record format, the change has to be plumbed through every integration to land.
Batch record software built into the production system removes the integration tax. The formula record the EBR pulls from is the same record the regulatory team works from. The QC result that releases the batch is the same QC result the certificate of analysis is generated from. A deviation at step 12 creates a QMS event in the same system, against the same batch, with no manual handoff. There is one source of truth, not five connected at the edges with brittle pipework.
When evaluating, ask the vendor:
- Where does the formula record live?
- Where do QC results land, and how do they attach to the batch record?
- How are deviations raised and tracked, and against which record?
- What happens when a client wants the same batch record in a different format?
- Can per-client batch record formats be configured by the regulatory team, or does every change need a vendor ticket?
If the answers depend on an integration, budget for it.
How Worldover handles it
Worldover runs paperless batch records as part of one operating system, not as a bolt-on. The formula is one record across PLM, regulatory and production. The shop floor executes against that record in real time, with every weighing, in-process check, deviation and sign-off captured at source. QC results flow from the LIMS module into the batch record the moment they are released.
Per-client batch record formats are configured once, then generated automatically at close-out. The operator sees one consistent workflow on the floor. The client gets their batch record in their template, with the data they expect, signed off and audit-ready. In-process deviations raise QMS events in the same system, against the same batch, so nothing is lost between systems.
Audit prep stops being a project. An ISO 22716 or MoCRA inspector can be walked through any batch end to end in minutes, and per-client margin updates every shift because the cost data is on the same record as the production data.