Pharmaceutical ERP Consultant, India

Own plants, loan license and third-party manufacturing

Many Indian pharmaceutical brands do not make everything they sell. A marketing company may own the brand and the distribution network while a third-party manufacturer produces under its own license and invoices finished goods. Under a loan license arrangement, the brand owner typically supplies some or all materials, and the plant charges for conversion. Larger groups run their own plants for some products and outsource others.

Each model changes the ERP design:

• Third-party purchase: finished batches arrive with the manufacturer's batch number, expiry, MRP and certificate of analysis, and enter quarantine until your QA team accepts them.
• Loan license: materials you own sit at someone else's plant, so you need stock at the job site, issue and consumption records per batch, and reconciliation of what came back.
• Own plant: formula versions, batch orders, material issue from released lots, yield and batch costing.

Getting these flows right decides whether your product cost and inventory figures are trustworthy. I map them first with purchasing, production, QA and finance together. The general pharmaceutical process map is described on my pharmaceutical ERP page. GST treatment of job work and e-way bills for plant movements are explained on my India manufacturing ERP page instead.

Batch-wise MRP, price control and trade schemes

In India, the maximum retail price is printed on each pack, so two lots of one product may legitimately show different MRPs after a revision. Certain formulations fall under the national drug price control framework, which sets ceiling prices and governs how increases may be taken. The details are for your regulatory and commercial teams to confirm, but the ERP consequences are clear.

The requirements I write usually include:

• MRP held at batch level, not just item level, and printed on invoices and dispatch documents from the batch record.
• A ceiling price reference for controlled formulations, with a check that blocks a batch MRP above the permitted level.
• A procedure for price revisions: which batches carry the old MRP, which carry the new one, and how stock in the channel is treated.
• Price to stockist and price to retailer derived consistently from MRP, with margins agreed by your commercial team.
• Trade schemes such as bonus quantity or discount offers, with start and end dates, eligible customers and their cost visible by product.

When MRP and schemes live in spreadsheets, invoice errors and margin leakage follow. I make these rules part of the scenarios tested during ERP evaluation, so the chosen platform has already shown it can handle them. GST on medicines and schemes should be confirmed with your tax advisor.

CFAs, stockists and the return flow of expiry and breakage

A typical Indian pharmaceutical distribution chain moves stock from plant or central warehouse to carrying and forwarding agents in each state, who bill stockists on the company's behalf. Stockists then supply retailers, hospitals and sub-stockists. Every step adds data the company needs: stock at each CFA by batch and expiry, stockist receivables, and claims coming back.

The return flow causes the most pain. Stockists send back expired, near-expiry, damaged and breakage goods, often in bulk and against settlement policies that differ by product and region. Without proper ERP design, the company cannot see its real liability until the credit notes arrive.

I write requirements for:

• Stock transfer to CFAs with batch, expiry and MRP, and CFA-level inventory and billing.
• Customer records with drug license numbers and their validity, checked before billing.
• Claims recorded by batch and reason, approved against your returns policy, and settled as credit notes.
• Provisions for expected expiry returns based on stock in the channel, agreed with your finance team and auditors.
• Secondary sales and stock data from stockists, imported where available, to guide production and dispatch planning.

Batch-wise records across this chain also make a recall possible down to stockist level. I test that path during UAT with a real batch from your current data.

Export barcoding, licenses and the quality boundary

Indian pharmaceutical exports carry their own documentation. Export consignments may need barcodes at different packaging levels and batch data shared through the government track-and-trace arrangements for exported drugs, and importing countries add their own serialization or labeling requirements. Active ingredients may also need codes carrying batch details on their labels. Exactly what applies to your products and destinations is for your regulatory and export teams to confirm.

The ERP's role is to hold accurate item, batch, packaging hierarchy and shipment data, and to pass it to the barcoding or serialization software at the packing line. I specify that interface using my ERP integration method, so the ERP, the line software and the export documents agree.

Licensing runs through the system too: manufacturing and sale licenses for your own sites, drug licenses for customers, and stricter record keeping and storage for narcotic and psychotropic products where you handle them. The ERP can store license details with expiry dates, restrict locations and require extra approvals, following rules your compliance staff define. Deviation, CAPA, change control and document management usually sit in a QMS, and lab data in a LIMS. With that split agreed, QA knows exactly which ERP functions to look at when weighing validation. For process-heavy bulk drug plants, my Hyderabad ERP consultant page covers stage-wise API costing.

From Tally and distributor software to a pharma ERP, remotely

Indian pharmaceutical companies frequently run accounts in Tally, distribution through a separate pharma billing package at CFAs, and batch, MRP and claims records in spreadsheets. When they move to a full ERP, the migration must carry batch stock at every location with expiry and MRP, open stockist balances, pending claims, customer license data and active schemes. I plan it with reconciliation steps signed off by finance, distribution and QA, and I usually recommend a short parallel period at a few CFAs before the full switch.

Platform choice depends on whether you manufacture or outsource, the size of your CFA network, how much export you handle and your budget for licenses and implementation. The platform notes below summarize where each option tends to fit, and the comparison is then run on your own scenarios.

All sessions run online: process workshops, shared diagrams, a numbered requirement list and recorded UAT, with work scheduled in Indian working hours. Plant and warehouse walkthroughs over video usually give me what I need, and in-person meetings are possible by arrangement. For other Indian engagements, see my ERP consultant India page or the India hub.