GMP weighing and dispensing software: what GMP requires, what the batch record needs – and how software helps

Dispensing is the moment an anonymous raw material becomes a component of a specific batch. Everything afterwards – blending, granulation, filling – rests on the assumption that the right material in the right quantity from the right container was used here. That is why an inspector tracing a batch almost always asks for the dispensing record first. The process itself, step by step, is described under pharmaceutical dispensing system.

Note: the table names chapters, not paragraph numbers, and does not replace regulatory advice.

Per weighing, a dispensing record – paper or electronic – should carry at least: production order and batch (for multi-batch orders: which one), BOM position and target, material and container/lot ID, tare and net, actual quantity and deviation from target, scale (identification, calibration status where applicable), operator, date and time, check result (within/outside tolerance), release or second-person check and – for deviations – the reason. For proof of charging, add confirmation that the quantity actually went into the process vessel. This record is the dispensing part of the batch record.

Electronic batch record (EBR) and MES systems document the whole manufacturing process; weighing is one step among many. A dispensing system covers that one step in depth: it guides the weighing, enforces container and tolerance checks and produces the weighing record that goes into the batch record. If you are looking for batch record software because the dispensing records are the weak point, a dispensing system addresses exactly that step. d-dispensing is a dispensing system – it is not an EBR and does not replace one.

Recurring findings from batch traceability: container ID missing or illegible ("lactose" instead of "lactose, container 4711"); tolerance deviation closed without a documented reason; handwritten, implausible timestamps; scale not identified; dispensing and charging not linked; Excel lists without change protection declared as "electronic records"; legacy software without an audit trail whose vendor no longer exists.

GMP requires evidence, not digitisation. Paper is permitted – but slow to review, error-prone for container IDs and useless for trending. Many plants instead run a terminal from the mid-2010s on a Java runtime nobody patches, installed by copying DLLs into the JRE folder. It works until the one person who can reinstall it leaves. The question is rarely "whether" to switch, but "with how much risk". → Weighing terminal software: replacing a legacy terminal

The twelve points above are the requirements list d-dispensing was built against – and has met in daily use at several manufacturers since 2015, with several million production orders processed to date.

Bench workflow

1. 01Scan the production order. BOM with target, actual and remaining – per batch for multi-batch orders.
2. 02Select the position, scan the container. The container ID is checked against the position; wrong material is refused and the refusal logged. (Checklist 2, 7)
3. 03Weigh. Live weight, progress, GHS pictograms and signal word. Warnings at 50 % and 95 %.
4. 04Finish. Only within the tolerance band: at most 104 % of remaining per weighing, closure between 98 and 102 % of target – checked on the site server, not in the browser. (Checklist 3, 4)
5. 05Store, label, book. Store durably, label with the record ID as barcode, stock movement in ERP and WMS in one transaction. (Checklist 10, 11)
6. 06Proof of charging in the same record. (Checklist 9)

The record and the audit trail

Every weighing, refusal, licence check and software update is an entry in a hash-chained audit trail with trusted timestamp and reason. Later changes become detectable; QA can verify checkpoints; export is built in. (Checklist 5, 6, 8)

Behaviour on failure

The station agent owns scale and printer. On network loss the weighing in progress finishes, is stored locally, labelled and booked idempotently later. New orders need the server – guessing a BOM from cache is not an option. This behaviour is tested and described in the QA brief. (Checklist 12)

What d-dispensing does not do for you

Integration and status

Implemented today: the ERPs myfactory (with xstorage as WMS) and weclapp; scales from Mettler Toledo, Sartorius, RHEWA and more; Zebra/ZPL. Operator UI in German today, built for further languages. In production since 2015, several million production orders processed. Manual installation today, signed Windows installer on the roadmap.