MES for Cosmetics Manufacturing: CPKB Batch Records Without Binders
A cosmetics plant lives and dies by its batch documentation. CPKB, the Indonesian good cosmetics manufacturing practice (Cara Pembuatan Kosmetika yang Baik), set out in PerBPOM No. 31 of 2020 and amended by PerBPOM No. 27 of 2025, expects every production batch to be documented: batch production records, quality control records, and traceability from raw material to finished goods. And unlike a food plant inspected site-wide, a CPKB audit is conducted per building, which means a plant with two production buildings maintains and defends two documentation sets. For most cosmetics factories the answer to that expectation is a binder: a thick printed batch ticket, a QC annex, signing pages, and a shelf of completed binders arranged by month.
The binder passes audits. It also eats the plant: hours of transcription, signatures chased across shifts, and a Head of Production who spends the first week of every month assembling evidence instead of running the floor. This post is about replacing the binder work with a record that assembles itself while the batch runs.
What CPKB Actually Asks For
Read past the legal formatting and CPKB's documentation demands come down to three things per batch:
- Batch production documents: what was made, in what quantity, on which equipment, by whom, following which formulation and procedure.
- QC records: the in-process and finished-goods checks the product's specification requires, with results and the identity of who performed them.
- Traceability: which raw material lots went into the batch, and where the batch went afterward, so a quality problem can be traced in both directions.
The regulation does not demand paper or software; it demands that the record exists, is accurate, and can be produced when the inspector picks a batch at random. That last part, production on demand, is where binders hurt: an auditor asks for batch code K-2409-118 from the Cileungsi building, and the next hour is a search through a shelf while the auditor waits. If your next CPKB surveillance visit is approaching, work through a BPOM audit preparation checklist before changing anything else; the checklist tells you where your documentation actually stands.
The Cosmetics Reality: Variants, Small Batches, and Volume
Cosmetics production breaks batch documentation in a way food and pharma do not. One base formulation spawns twenty shade or fragrance variants. Batches are small, often a few hundred kilograms, so a busy day produces more batch records than a food plant running the same tonnage. And the market grows fast: a brand doubling volume in a year does not double headcount in the documentation office.
Here is what that looks like concretely. A plant running 15 batches a day on paper batch tickets, each ticket needing formulation printout, material lot entries, in-process check sheets, and QC annex, needs every operator and analyst to be perfectly disciplined, every shift, for every batch. At 30 batches a day after a strong sales year, the same discipline has to hold at double speed with the same people. It does not. Batch numbers get reused because the numbering register lives in a spreadsheet only one supervisor edits. An in-process pH check is written at end of shift from memory. A material lot entry is left blank because the drum label was illegible, and the blank is discovered at month-end when fixing it means reconstructing which lot was actually at the station three weeks ago. None of this is visible in the binder, which by then contains a tidy, partly fictional record.
What a CPKB-Ready Electronic Batch Record Covers
An electronic batch record (EBR) is not a scanned binder. It is the batch's history, captured at the line as the batch runs. Per batch, it must cover:
- Materials and lots: every raw and packaging lot consumed, keyed or scanned at the step where it was used, checked against the formulation on the work order.
- Operator and station: who performed each step and on which equipment or mixer, so the per-building audit question (who, where) is answered by the record itself.
- In-process checks: pH, viscosity, fill weight, appearance, microbial sampling references, recorded at the step, against the specification, with any out-of-spec result flagged immediately rather than at month-end.
- Deviations and NCRs: what went wrong, how it was dispositioned (rework, reprocessing, reject), and what corrective action followed, attached to the batch permanently.
- Release: the QC decision that releases the batch, with the checker's identity, so an unreleased batch cannot quietly ship.
This is the same skeleton as the electronic batch record for BPOM food audits; cosmetics adds the variant dimension, where one work order per shade means the formulation check (right pigment, right fragrance) happens at the terminal instead of in the operator's head. Traceability itself is a system property, not a document; the lot genealogy model shows how batch-to-lot links work in both directions, and our Bahasa primer on apa itu traceability covers the concept for the wider team.
The Head of Production's Monthly Evidence Pull
Then: it is the first Monday of the month, and a customer or distributor documentation request has landed, or the CPKB self-inspection is due. The Head of Production allocates two days. Two QC staff pull binders for the requested batch list, photocopy the ticket and QC annex, cross-check that every signature line is signed (find the missing one, chase the operator), verify the material lot entries against the warehouse log, and compile a PDF. Real cost: two person-days per request, plus the risk that a gap surfaces mid-compilation.
Now: the same request is a filter and an export. Select the batches, generate the audit pack, one printable document per batch with genealogy, operations, inspections, NCRs, and downtime, or one zip for the whole month. The Head of Production reviews the pack in twenty minutes instead of directing a two-day archaeology project. The record was already assembled, while each batch ran, by the people doing the work. Month-end stops being a documentation event and becomes a review.
The difference is not software magic. It is capture at the station: the operator confirms the work order at a terminal, keys or scans the lot as it is consumed, records the in-process check, and the system stitches the events into the batch record. A binder is a reconstruction. An EBR is a biography.
Frequently Asked Questions
Does CPKB allow electronic records?
Yes. The regulation's requirement on documentation is that records are accurate, complete, and retrievable when needed; it does not mandate paper. The obligations transfer to the system: access control so entries are attributable to a named person, records that cannot be silently edited, and retrieval that works when an auditor is standing in the room. If your electronic system ensures those properties, electronic records satisfy CPKB the same way a well-kept binder does, at a fraction of the retrieval cost.
Do we still have to print and wet-sign?
That is your QA policy decision, not a software one. Many plants continue printing a release page per batch for the signature ritual while the electronic record becomes the system of record; others go fully digital once QA is satisfied with access control and audit trail. What changes either way is upstream of the signature: the entries feeding the record are captured at the line as events happen, so the thing being signed is complete by construction instead of being checked line by line at month-end.
We already pass CPKB audits with paper. Why change?
Because passing describes the audit, not the cost of getting there, and the cost scales with volume. Every added SKU line, variant, and building multiplies binders, transcription hours, and the chance of a transcription error reaching the shelf. The trigger we see most often is growth: a plant that doubled output finds batch numbering slipping and in-process checks recorded late, and fixes it by moving capture to the station rather than by hiring a second documentation team. If your audits are clean and your volume is flat, the paper system is working; revisit this when the next expansion lands.
CPKB Batch Records That Assemble Themselves
Voltrus MES records every batch at the station: materials and lots, operator and equipment, in-process checks, deviations, and release, assembled into a per-batch audit pack. See what ships today.
See Voltrus MES