TL;DR
Choose a multi-site API CDMO when the second site can supply comparable API before a disruption exhausts inventory. Test six gates: continuity risk, capacity, technology transfer, analytical comparability, regulatory status, and governance. A second address without completed transfer, matching controls, site-specific evidence, and clear activation ownership adds cost without creating usable backup supply.
Use six gates to choose a multi-site API CDMO, a contract development and manufacturing organization: continuity, capacity, transfer, analytics, regulatory status, and governance. Choose two sites only when the second site can supply comparable API before a disruption exhausts inventory.
An API is the active pharmaceutical ingredient in a drug product. A qualified alternative site has completed the process, analytical, quality, and regulatory work needed for that exact API and market.
Do We Need More Than One API Manufacturing Site?
A second site earns its cost when it removes a real single point of failure. It does not earn its cost because a supplier has a larger global footprint.
Use this decision table before you request proposals.
| Decision Area | Add a Second Site When | Keep One Site When | Request |
|---|---|---|---|
| Continuity risk | One loss stops product supply | Same weak point remains shared | Site and upstream-risk map |
| Capacity | Both sites prove required campaigns | Backup lacks API-specific capacity | Batch range and slots |
| Transfer readiness | Qualification work is complete | Route still changes frequently | Transfer protocol and status |
| Analytical comparability | Both sites release comparable API | Methods or controls differ materially | Batch comparison package |
| Regulatory status | Each site fits target filings | Site scope is unclear | Site-specific dossier route |
| Programme complexity | Interruption cost exceeds upkeep | Duplicate work delays launch | Maintenance and governance plan |
The table means that “two sites” is not the decision. The decision is whether the second site can operate as a usable route when the first route fails.
The FDA’s shortage framework requires certain drug and API manufacturers to develop redundancy risk-management plans. Start with the failure that would interrupt your product, then decide whether a second site removes that failure.
What Risks Does a Second API Site Solve?
A second qualified site can protect against a plant shutdown, local utility outage, regional transport interruption, inspection-related pause, or capacity constraint at one facility. It does not protect against risks both sites share.
Map these common causes before you call a network resilient:
- Critical starting materials: Two plants using one qualified supplier may still stop together.
- Process technology: A difficult reaction, purification train, or containment requirement may exist at only one site.
- Quality control: A shared release laboratory, method owner, or reference-standard source can block both sites.
- Subcontractors: A common micronization, packing, storage, or logistics provider can remain a single point of failure.
- Regulatory scope: A site may make the API but lack the documented route for your US, EU, or other target market.
- Programme ownership: One CDMO can simplify governance, but one delayed investigation or change-control decision can still affect both sites.
FDA’s API GMP guidance requires manufacturers to evaluate and approve suppliers of critical materials against agreed specifications. That makes an upstream map as important as a plant map. FDA Q7 guidance
For a US generic-drug programme, connect the continuity review to the exact molecule, manufacturer, site, and filing route. API suppliers for US generic drug manufacturers gives the broader qualification context.
What Must Match at a Backup Site?
A backup site must make the same controlled product, not merely a product with the same name.
ICH Q12’s small-molecule alternative-site example requires acceptable site compliance status, similar equipment or materials of construction, completed technology transfer and process qualification, and no change to the synthetic route, control strategy, impurity profile, physicochemical properties, material specifications, or release and stability methods. ICH Q12 conditions
Technology transfer is the controlled handover of process knowledge, methods, materials, and acceptance criteria to the receiving site. Ask both sites to identify every difference in:
- Starting-material source and specification
- Reaction equipment and scale
- Solvents, reagents, and reaction conditions
- Isolation, drying, milling, and packaging
- Critical process parameters and in-process controls
- Release specifications and analytical methods
- Impurity profile and physical form
- Stability protocol and storage conditions
The relevant question is not “Do both sites use HPLC?” The relevant question is “Can both sites use appropriate methods to show the same API quality attributes, including product-specific impurities and physical properties?”
ICH Q11 calls for comparative analytical testing of relevant drug-substance batches when manufacturing sites change. It also calls for the site, scale, route, date, and intended batch use to be documented. ICH Q11 guidance
For steroid, hormone, and other complex small-molecule work, use our manufacturing capability checklist to keep equipment, analytics, documentation, and commercial evidence in one review.
How to Test Technology Transfer Readiness
A supplier should answer this section with documents, not assurances. Run these five checks in order.
-
Read the process package. Request the process flow, material specifications, critical parameters, in-process controls, impurity strategy, and batch records or representative batch summaries.
-
Compare the equipment train. Match reactor materials, agitation, temperature control, filtration, drying, milling, containment, and cleaning approach. Similar nominal volume alone does not establish process fit.
-
Review analytical transfer. Request the method-transfer protocol, method status, reference-standard controls, sample handling, system suitability, and acceptance criteria for batch comparison.
-
Test representative material. Compare batches from both sites against the agreed release specification and the attributes that matter to the API. Include assay, related substances, residual solvents, water, physical form, and any molecule-specific controls.
-
Assign change ownership. Name who approves deviations, raw-material changes, equipment changes, method changes, and activation of the alternative site.
FDA Q7 requires formal change control, impact assessment, suitable validation and documentation, and approval of contractual changes by the contract giver. FDA change control
Peptide programmes need added attention to sequence-specific impurities, purification, and stability. Peptide CDMO process-development stages helps teams frame those questions before a site transfer begins.
What Does Two-Site Supply Add?
Two-site supply adds work that must remain funded after the first launch. Budget the activities, not a vague “redundancy premium.”
The ongoing scope usually includes transfer batches, process qualification, analytical transfer, comparative testing, stability work, site audits, quality-agreement management, capacity reservation, periodic review, and requalification after material or process changes.
For approved US ANDAs, certain changes to approved conditions require a supplemental application before implementation. A site strategy must therefore involve regulatory affairs before activation planning. FDA ANDA requirements
Additional API facilities can also affect the API-related fee calculation in the circumstances described in FDA’s generic-drug fee guidance. FDA facility-fee example
Set one governance calendar. It should cover capacity review, change notifications, critical-material status, open deviations, stability commitments, site compliance status, and the decision authority for activating the second site.
What to Put in Your Multi-Site CDMO RFQ
Send the same technical request to every candidate. Comparable answers reveal whether a supplier has a backup route or only a network description.
- Identify every site and legal entity that will develop, manufacture, test, release, pack, store, or subcontract the API.
- Identify the primary and alternative site for the exact API form and target market.
- State which disruption scenarios the alternative site solves.
- Identify critical materials, laboratories, subcontractors, and logistics services shared by both sites.
- Provide the validated batch range, equipment train, campaign frequency, and available commercial slots for each site.
- List every process, equipment, material, and control difference between sites.
- Provide the technology-transfer protocol, acceptance criteria, completed work, and remaining qualification work.
- Provide analytical-method transfer status and side-by-side batch-comparison data.
- Provide impurity, physical-property, and stability comparability evidence.
- Provide GMP/compliance evidence for each site and activity.
- Identify the DMF, ASMF, CEP, or other product-and-site documentation supporting each market.
- Assign responsibility for deviations, changes, audits, interruption response, and alternative-site activation.
For a molecule-specific request, adapt our steroid API RFQ checklist rather than relying on a generic capacity questionnaire.
FAQs
Does One CDMO Contract Mean Two Qualified Manufacturing Sites?
No. One contract can cover several facilities, but each activity still needs a named site, defined responsibility, and applicable qualification evidence. Ask where development, manufacture, testing, release, packing, and subcontracted work occur.
Should We Use Two Sites in One CDMO or Two CDMOs?
Choose one CDMO with two sites when shared quality systems and coordinated transfer ownership reduce your main risk. Choose independent CDMOs when CDMO-level, regional, or governance risk remains your largest concern. In both models, map shared materials and service providers first.
How Often Should a Backup Site Stay Active?
Set a maintenance schedule tied to your API’s retest period, stability plan, change history, capacity reservation, and regulatory commitments. The quality agreement should state which batches, reviews, and requalification events keep the alternative route usable.
Do Shared Analytical Methods Prove Comparability?
No. Shared methods are useful only when both sites can apply them to show comparable results from relevant API batches. The comparison must address the API’s impurity profile, physical properties, and other quality attributes affected by the transfer.
Who Approves a Change at a Contract Manufacturing Site?
The contract giver must be informed and approve process, equipment, test-method, specification, and other contractual changes under FDA Q7. FDA contract controls
At Aarise Pharma, we manufacture steroid, peptide, hormone, and general pharmaceutical APIs for generic manufacturers, contract formulators, and pharmaceutical distributors. Our API manufacturing page details our Haridwar facility, WHO-GMP and ISO 9001:2015 certifications, and the COA and MSDS supplied with each shipment.
