Manufacturing ERP where the batch is the record
Batch numbers, expiry and test results are not reporting. They are the product record, and they have to be one record.
What does a pharma manufacturer need from an ERP?
The batch has to be the unit everything attaches to: material issued, QC results, expiry and retest dates, and the despatch document. When quality data lives in a parallel register, the two versions disagree eventually, and an audit is usually where you find out.
Quality data belongs against the batch, not beside it
In-process checks, finished goods analysis and the certificate of analysis all attach to the batch that production actually ran. A QC register maintained in parallel is the single most common finding, because it drifts from the production record and nobody notices until someone compares them.
Expiry and retest dates drive stock decisions
Raw material has a retest date, finished goods have an expiry, and both have to drive issue order rather than sit as a field somebody looks up. First expiry first out has to be what the system suggests, not what a storekeeper remembers.
Yield reconciliation per batch is a compliance question
Theoretical yield against actual, explained where they differ, per batch. This is an ordinary production number in most sectors and a documented requirement here, which changes when and how it has to be captured.
A recall has to be answerable in hours
Given a batch, which raw material lots went into it, which finished goods came out, and which customers received them. Forward and backward in one query. If that takes two days of spreadsheet work, the answer arrives after it mattered.
The despatch document carries the batch QC refers to
The batch on the invoice, on the certificate of analysis and on the carton have to be the same batch. Sounds obvious, and it is where a surprising amount of manual reconciliation goes.
Batch production and traceability
The batch as the record: material issued against it, yield reconciled per batch, and forward and backward traceability from raw lot through to the customer who received the finished goods.
Quality control
In-process and finished goods results recorded against the batch itself, with the certificate of analysis produced from those results rather than compiled separately.
Inventory and stores
Retest dates on raw material and expiry on finished goods driving issue order, so first expiry first out is what the system proposes rather than what someone remembers.
Despatch, GST and e-way bill
Despatch documents carrying the same batch the QC record refers to, with e-way bills generated from the same despatch.
Does Facto keep quality data against the batch?
Yes, and that is the design point. In-process checks and finished goods analysis attach to the batch production ran, so the quality record and the production record are the same data rather than two registers that have to be reconciled before an audit.
How quickly can we trace a batch for a recall?
Forward and backward from one batch: the raw material lots that went in, the finished goods that came out, and the customers who received them. It is a query rather than a reconstruction, which is the difference between answering in hours and answering in days.
Does the system handle expiry and retest dates?
Raw material carries retest dates and finished goods carry expiry, and both drive the issue order the system proposes. That makes first expiry first out the default suggestion rather than something depending on which storekeeper is on shift.
