In this guide 6 sections
Start with a ready product for what every plant shares, stock, batches, quality records and dispatch, and build custom only where clients differ, such as batch record layouts. Gaps show up fast. Test your two hardest clients first. Invoicing by service is the third edge.
What a contract manufacturer needs that an own-brand plant does not
An own-brand tablet plant answers to one set of specifications, while a contract suite answers to many, and each client owns its formula, artwork and approved vendor list. Some even dictate the batch record.
That changes the software question. Material belonging to Client A must never be drawn for Client B, and retention samples, stability pulls and quality agreements all sit under a client name. Each auditor asks for them separately.
Each client can audit you, and each audit starts from that client’s own paperwork and quality agreement, so records must filter easily by owner. Ready products handle one owner well. Contract work adds a second owner to every record, and dispensing logs, release certificates and retention sample registers feel the strain first.
- Client-owned raw material and packaging stock kept apart
- Quality agreement terms attached to each client
- Client approval before a batch is released
- Separate retention sample and stability schedules
- Tolling charges, not just product sales
What a ready product already does well
Dispensing, batch numbering, in-process checks, yield reconciliation, label control and expiry tracking are common to every plant, and a mature ready product already has them working. Many sites have already tested them, from granulation to blister packing.
Building them again is slow. Your team gains nothing from a custom stock ledger, so buy that part and spend the engineering effort on the client facing edges where your contracts differ.
Ask a vendor to run one real batch from a recent client through a demo, from dispensing to dispatch, and watch where the screens fight you. Short demos hide gaps. A full batch exposes them.
Where client specific demands break the standard
Three areas usually fail first. The first is the batch record, where one client wants its own signature blocks and another wants your standard record with extra checks bolted on.
The second is client reporting, where a multinational client may want a yield trend, deviation count and open CAPA list in its own layout. Others want just a PDF.
The third is invoicing, because contract work bills granulation, compression, coating, blister packing and testing as separate lines, plus any materials you supplied. Standard sales invoicing sees one product sold.
- Template per client for the master batch record
- Scheduled client report with fixed columns
- Service line invoicing with a rate card per client
- Client portal view limited to its own batches
A split that works: ready core, custom edges
Most contract plants do best with a hybrid, keeping the ready product for stock, batches, quality events and dispatch and adding a thin custom layer on top. Clients who value speed will accept a standard portal, but clients with their own quality systems want records in formats their auditors already know.
The edge layer reads from the core and writes nothing back, so upgrades to the ready product leave the rate cards, the report builder and the portal alone.
Check how the ready product exposes data through an API, a database view or scheduled CSV exports, because a closed product forces you to copy figures by hand. Copying rebuilds the old spreadsheet.
Run a scored trial before you commit
Pick your two most demanding clients, list every document each expects in a month, and score the ready product line by line as covered, configurable or missing.
Count the missing lines. A handful points to configuration and a small edge build, while a long list from several clients points to a larger custom scope.
Add artwork approvals, certificate of analysis formats, stability pull schedules and tolling rate cards to that list first, since ready products most often miss these lines. Show the list to every vendor. A vague wish becomes a priced scope. Do it before the second demo.
Contract client demand scorecard
A single sheet that gives each client document or report its own line: batch record, certificate of analysis, monthly yield report and invoice. Columns are client, document, owner, covered by ready product, needs configuration, missing and notes, with a totals row at the foot counting missing items per client.
Open a blank worksheet to printQuestions owners ask
Can one ready product serve several contract clients?
Often yes, provided it keeps stock and records separated by client owner and lets a batch record template be set per client. Try issuing Client A stock to Client B.
Is a custom build slower to get running?
Usually, because a custom build starts from written requirements and screens still to be drawn, while a ready product starts from a working base that already runs stock. Hybrid first, edges later.
What if our clients keep changing their formats?
Favour tools where you edit batch record templates and report layouts yourself without a developer, because if every format change needs code, the cost grows with every client.
Who should join the vendor demo?
Send a production manager, a QA person and whoever raises invoices, because each sees a different gap and the invoicing gap is often found last.