12 must‑have capabilities in 2026 for a CDMO ERP selection

Contract developers and manufacturers don’t run like standard discrete plants. work in make‑to‑order environments, often with client-owned materials, regulated quality, and audit trails that must satisfy customers and regulators. The right CDMO ERP should support that reality from day one, so you avoid late add-ons, rushed rework, budget overruns, and compliance fixes after go-live.

Based on our life sciences experience supporting outsourced operators, including contract development and manufacturing organizations (CDMO) and contract research organizations (CRO), this guide summarizes the ERP software selection requirements vendors must prove, demo, and document. It is informed by recurring requirements from anonymized user requirements specifications (URS), requests for information (RFI, and functional requirements documents (FRD).

1. End‑to‑end batch/lot genealogy with retained samples)

   • Why it matters - Auditors and clients will ask you to show where every gram came from and where it went.

   • Require - Full lot genealogy from inbound materials through work in process to finished goods, plus retained sample tracking with storage location, pull dates, and test history.

   • Ask vendors to demo - Receive a raw material lot, generate a sampling plan automatically, hold it in quarantine until it is released, consume it into a batch, and provide one click genealogy from the finished lot back to every input, including retained sample details.

2. Specifications, potency, and expiry with certificates of analysis (COA) and certificates of conformance (CoC) out of the box

   • Why it matters - Specifications are not notes. They drive acceptance, calculations, and expiry.

   • Require - Target potency with minimum and maximum ranges, shelf life and expiry at the item or lot level, and certificate of analysis (COA) generation at release and shipment.

   • Ask vendors to demo - Enter potency on batch completion and confirm yield, potency adjusted quantity, and expiry flow through to the certificate.

3. Quality control (QC) planning, sampling, and laboratory information management system (LIMS ) and instrument handoff

   • Why it matters - Manual triggers and spreadsheet lab records break data integrity.

   • Require - Item and lot rules that automatically trigger quality control, destructive and non-destructive sampling, and integration patterns for laboratory systems and instruments such as high performance liquid chromatography (HPLC) and gas chromatography (GC), with result attachment and status control.

   • Ask vendors to demo - Automatically send lots to test, capture results even if attached, and block release until the result passes.

4. Nonconformance and material review board (MRB) workflow with true quarantine

   • Why it matters - Quarantine labels without system enforcement are audit bait.

   • Require - System enforced status and locations such as quarantine, rejected, and released, plus material review workflows, labeled segregation, and disposition logging.

   • Ask vendors to demo - Fail a lot, open a nonconformance, route it through material review for disposition, and show that quarantined stock cannot be shipped.

5. Client owned materials with chain of custody and billing uplifts

   • Why it matters - Many CDMOs convert the client’s material on your line. You must track custody and bill fairly.

   • Require - Separate ownership flags, custody history, and automated handling and processing fees on pass through items, using either percentage or fixed charges.

   • Ask vendors to demo - Receive it as client owned material, convert it, and invoice with uplift lines generated automatically.

6. Shop floor data capture ready for electronic batch records (EBR) and electronic device history records (eDHR)

   • Why it matters - Paper travelers do not scale. Auditors want who, what, and when tied to each step.

   • Require - Barcoded issuance and returns, labor and machine time capture, and controlled step sign offs with electronic signatures and audit trails.

   • Ask vendors to demo - Start and stop machine and labor on a batch, capture a deviation, and require a supervisor electronic signature before continuing.

7. Stability studies and environmental monitoring (EM)

   • Why it matters - Trending, pull schedules, and excursions are central to many programs.

   • Require - Stability protocols with pull schedules and storage conditions, environmental monitoring capture for rooms and equipment, and trend charts with alerting.

   • Ask vendors to demo - Create a stability study tied to a finished lot, schedule pulls, and record temperature excursions with an impact assessment.

8. Equipment calibration and preventive maintenance with process gating

   • Why it matters - If equipment is not calibrated, the lots it produced should be treated as invalid.

   • Require - Calibration and preventive maintenance (PM) schedules, certificate storage, and the ability to block production if calibration is overdue.

   • Ask vendors to demo - Attempt to start a batch on an overdue scale, show the hard stop, and demonstrate how documenting calibration allows work to proceed.

9. Controlled labeling and artwork management, including unique device identification (UDI) and GS1 standards when applicable

   • Why it matters - Printing outside control breaks traceability and labeling regulations.

   • Require - Controlled printing with revision controlled templates, role based access, and support for unique device identification (UDI) and GS1 standards when the product requires it.

   • Ask vendors to demo - Change a label version, restrict who can print by role, and support serialization and aggregation when required.

10. Client segmentation, entities, and revenue models

    • Why it matters - CDMOs need to see margins by client, program, molecule, and sometimes by clinical versus commercial business.

    • Require - Reporting dimensions for each client and program, support for consolidating across multiple legal entities, and flexible billing such as time and materials, milestones, per batch or per test, and pass through charges.

    • Ask vendors to demo - Run two invoices, one for a milestone and one for time and materials plus pass through lab fees, then show margin by client and program.

11. Supplier qualification, incoming quality control (QC), and approved vendor lists (AVL)

    • Why it matters - Qualification and approved vendor lists drive release and risk.

    • Require - The system should track supplier status, verify certificates of analysis (COA) at receipt, support third party lab workflows, and enforce approved vendor lists (AVL) at the item level.

    • Ask vendors to demo - Receive from an unqualified supplier and show the system enforcing a hold until approval.

12. Validation package, 21 CFR Part 11 controls, and audit readiness by design

    • Why it matters - Validation cost and time balloon when you start from zero.

    • Require – 21 CFR Part 11 electronic signatures and audit trails, vendor validation accelerators such as pre built test scripts and traceability matrices, a clear release cadence, and change impact documentation.

    • Ask vendors to provide - Example installation, operational, and performance qualification scripts, also known as IQ, OQ and PQ, an electronic signature configuration guide, and a regression test plan tied to upgrades.

    
    

Building your scorecard and how to weight it

A selection scorecard is a structured way to rate each vendor against your requirements, using clear criteria and weighting so the decision is evidence based. It is used throughout our ERP Software Selection process to compare RFI and demo results, document trade-offs, and create a measurable recommendation.

The following is an example of a weight set, but you should tune it based on your business risk and validation impact. During our ERP Software Selection process, we require vendors to answer each requirement with a simple key: 1 = out‑of‑box, 2 = light customization, 3 = native ISV, 4 = heavy custom, U = unknown.

Typical weight set (tune to your risk):

• GxP and data integrity including 21 CFR Part 11, audit trail, and electronic signatures - 15 to 20 percent

• Quality control (QC), laboratory systems (LIMS), and batch genealogy - 15 to 20 percent

• Client model and billing including client owned material, uplifts, and milestones - 10 to 15 percent

• Stability and environmental monitoring (EM) plus equipment gating - 10 to 12 percent

• Shop floor capture for electronic records (EBR/eDHR) - 10 to 12 percent

• Labeling, unique device identification (UDI), and shipping documents - 8 to 10 percent

• Finance including entities, dimensions, and revenue recognition - 8 to 10 percent

• Supplier qualification and approved vendor lists (AVL) - 5 to 8 percent

• Implementation and validation accelerators - 8 to 10 percent

Vendors then complete scripted demos using your data to prove the high-risk workflows, such as receiving client owned material, sampling and release, batch execution, certificates packaged for shipment, and milestone billing. We consolidate written responses, demo results, services estimates, and five-year total cost into a single steering committee ready comparison view.

Validation and audit tips that save months

• Traceability from demo to PQ - Reuse demo scripts as test scripts. Map each one to user requirement IDs so auditors can see clear lineage.

• Lock roles early - Define least privilege roles for operations, quality control, quality assurance, finance, and information technology before user acceptance testing. This shortens 21 CFR Part 11 testing.

• Favor maintained connectors - For lab systems, labeling, electronic data interchange, and tax, select validated connectors that can withstand cloud upgrades.

• Bundle the ship docs - Certificates of analysis or conformance, bills of lading, temperature logs, and client specific certificates should be assembled as a single, versioned packet at ship confirmation.

• Plan hypercare - Four weeks of post go live support with quality assurance present is common in regulated go lives.

  
  

How we can help with CDMO ERP selection

We have supported CDMO teams through ERP selection and delivery planning, with an emphasis on batch traceability, client owned materials, quality workflows, and controlled documentation that hold up under customer and regulatory scrutiny. Our approach is operations first and evidence based, using real workflows and scripted demos to surface fit gaps before they become rework and budget risk.

We bring CDMO specific user requirement libraries, demo scripts, and weighted scorecards so ERP software vendors cannot gloss over gaps during your ERP software selection. If you are currently selecting an ERP software solution and need a vendor neutral shortlist or a sanity check on an existing ERP software solution, contact us to review your requirements and selection approach and we will share anonymized templates plus a validation ready plan for roles, test scripts, and change control you can put to work immediately.