ERPNext for Pharma Formulations Manufacturing
ERPNext for Pharma Formulations Manufacturing
Revised Schedule M did something quietly significant: it moved a large part of Indian GMP out of the SOP file and into the system. Quality review, audit trails and data integrity are now expectations your software has to meet, not paperwork your team can catch up on before an inspection.
Revised Schedule M under the Drugs and Cosmetics Rules took effect for large manufacturers from 1 January 2025, with an MSME extension to 31 December 2025 under G.S.R. 127(E); it brings Indian GMP closer to WHO-GMP and adds Pharmaceutical Quality System, Product Quality Review, computerised systems and ALCOA+ data-integrity expectations, overseen by CDSCO. Source checked July 2026.
Formulations manufacturing is finished dosage: tablets, capsules, liquids and creams made in batches, packed, released and shipped. The discipline has always been the batch, but revised Schedule M has changed where that discipline has to live. A Pharmaceutical Quality System, Product Quality Review, computerised-system control and ALCOA+ data integrity are now expectations, and none of them are satisfied by a well-kept binder. ERPNext for a formulations plant is judged on whether it can hold a batch manufacturing record as the work happens, carry batch and expiry the length of the chain, and produce the review and the audit trail an inspector now asks to see.
What formulations manufacturing demands of a system
Start with the batch record, because it is the unit of everything here. Each run has its own record: the materials issued and their lots, the yield, the in-process checks, the batch number, the manufacturing date and the expiry. If a line runs more than one product, a line clearance has to sit between them. The system has to hold that record as the batch is made, because a batch record assembled afterwards from notes is the exact thing revised Schedule M and every auditor is trying to eliminate.
The second is batch and expiry along the whole chain, because finished medicine does not stop at your gate. Stock sits with depots, distributors and hospitals, each carton carrying an expiry, and it has to move oldest-first, be traceable to a recall wherever it has reached, and come back as an expiry return. The system has to carry batch and expiry beyond the plant, because expiry managed only inside the warehouse is expiry not managed at all.
The third is the part that is genuinely new: data integrity and computerised-system control. Revised Schedule M expects a quality system, a periodic Product Quality Review, and records that satisfy ALCOA+, meaning attributable, legible, contemporaneous, original and accurate, with an audit trail behind changes. That is a software requirement, not a documentation one. The system has to record who did what and when, keep the trail, and let you produce a product quality review from real batches rather than a spreadsheet built for the occasion.
A batch record made as the batch is
Materials and their lots, yield, in-process checks, batch number and expiry captured during the run, with line clearance enforced between products on a shared line.
Batch and expiry past the gate
Batch and expiry carried to depots and distributors, oldest-first despatch, traceable to a recall wherever the stock has reached, and returns brought back against the batch.
Data integrity that stands up
Who did what and when, kept as an audit trail behind changes, so records meet the ALCOA+ expectations revised Schedule M now makes explicit.
Product Quality Review from real batches
A periodic review built from actual batch, yield, deviation and complaint data, rather than assembled by hand the month an inspection is due.
How we deliver formulations on ERPNext
We start with the batch record and stock, because everything else reads from them. The record captured during the run, materials traced to lots, batch and expiry carried on every movement, and line clearance where a line is shared. This looks like configuration and it is the point: a plant that records the batch after the fact can pass on paperwork for a while, and fails the moment an inspector asks how the record was made.
Then the layer revised Schedule M added: user-level attribution and audit trail so changes are accountable, and a Product Quality Review that draws on real batch, yield and deviation data. The reporting is only worth trusting once the batch record and traceability beneath it are captured honestly, because a quality review assembled from a spreadsheet proves nothing about the quality system.
What revised Schedule M asks of your system
| Expectation | What it means | What it looks like in the system |
|---|---|---|
| Pharmaceutical Quality System | A defined quality system rather than a set of standalone SOPs. | Deviations, change control and approvals recorded in one place, tied to the batches they affect. |
| Product Quality Review | A periodic review of each product’s performance. | Built from real batch, yield, deviation and complaint records, not compiled by hand each year. |
| Data integrity (ALCOA+) | Records that are attributable, legible, contemporaneous, original and accurate. | Named users, timestamps and an audit trail behind every change to a batch or a master. |
| Computerised systems | Systems that are controlled, access-managed and traceable. | Role-based access, no shared logins, and a trail an inspector can follow through the system. |
We prove the batch record and its audit trail on live production before building reports on them, because a record that cannot show how it was made is the finding an inspector writes up first. In formulations the capture is proven early, because there is no rebuilding contemporaneous evidence after the batch has shipped.
Own-brand or contract? The one distinction that changes the build
If you make your own brands, the system is comparatively clean: your materials, your batches, your finished goods, and the discipline is depth of record rather than separation of ownership. The work concentrates on the batch record, expiry across your distribution, and the quality review.
If you make for other people, on loan licence or third-party contract, ownership becomes the hard part. The materials and finished goods may belong to the marketing company, the conversion is job-work rather than a sale, and one principal’s material must never be consumed on another’s batch. That is a materially different build, and it is the one most Baddi plants need. Our Baddi page covers that case in full.
Are you ready? A short readiness check
- Is your batch manufacturing record captured during the run, or written up afterwards?
- Where a line runs more than one product, is a line clearance enforced between them?
- Do batch and expiry travel with the stock to depots and distributors, not just inside the plant?
- Can you show who changed what and when, with an audit trail behind it?
- Could you produce a Product Quality Review from real batch data this week, without assembling it by hand?
Four or five clear answers means you are close, and the work is formalising what your quality team already does. Two or fewer means the first phase is the batch record and its audit trail, and with revised Schedule M inspections now live, that is the difference between a plant that demonstrates its quality system and one that describes it.
Frequently asked questions
Does revised Schedule M actually require an ERP?
It does not name a product, but it expects a Pharmaceutical Quality System, a Product Quality Review, controlled computerised systems and ALCOA+ data integrity with audit trails. Those are system properties. A plant can attempt them on paper, but attribution, contemporaneous capture and an audit trail are much harder to evidence without software doing it.
What is ALCOA+, in practical terms?
It means records should be attributable to a named person, legible, contemporaneous with the work, original, and accurate, with completeness and consistency alongside. In an ERP that translates to named user accounts rather than shared logins, capture at the point of work, and an audit trail behind changes.
Can ERPNext hold a batch manufacturing record?
Yes. Each run holds its materials and their lots, yield, in-process checks, batch number, manufacturing date and expiry, captured as the batch is made, so the record is a by-product of the work rather than a document reconstructed later.
How does it handle expiry and recall across distribution?
Batch and expiry are carried on stock beyond the plant, despatch moves oldest-first, and any batch can be traced to where it went, so a recall names the affected shipments and returns come back against the correct batch.
How long does an ERPNext implementation take for a formulations plant?
Ten to eighteen weeks for a typical plant, because the batch record, traceability and audit trail have to be modelled and proven on live production. A single-product own-brand plant is faster; contract and loan-licence work, and multi-market packing, are what extend it.
Key takeaways
- Revised Schedule M moved a large part of GMP into the system. Quality review, audit trail and data integrity are now software expectations, not paperwork.
- The batch manufacturing record has to be captured as the batch is made. A record assembled afterwards is the finding, not the defence.
- Batch and expiry have to travel past your gate, so despatch moves oldest-first and a recall can name where the stock went.
- Contract and loan-licence work is a materially different build from own-brand, because the stock you make may not be stock you own.
Planning ERPNext for a formulations plant?
Start with a team that will build your batch record and audit trail before it prints a quality report. KlyONIX Tech™ is a Frappe Certified Partner working with pharmaceutical manufacturers across India, from contract formulators to own-brand plants.
Revised Schedule M under the Drugs and Cosmetics Rules applied to large manufacturers from 1 January 2025, with an extension for MSME units to 31 December 2025 under G.S.R. 127(E) dated 11 February 2025 conditional on a CAPA plan; it aligns Indian GMP more closely with WHO-GMP and introduces Pharmaceutical Quality System, Product Quality Review, quality risk management, computerised-system control and ALCOA+ data-integrity expectations, administered by CDSCO. Source checked July 2026.
ERPNext for Pharmaceutical · Pharma serialization and track-and-trace · ERPNext in Baddi · ERPNext in Dehradun