Why parallel testing of API and formulation is insightful:

During product development and commercial lifecycle management, degradation can originate from the active pharmaceutical ingredient (API) itself or as a result of interactions within the formulation matrix. By testing both the API and the final dosage form under the same stability conditions, teams can pinpoint the source of degradation pathways. This helps separate intrinsic API instability from formulation-induced or excipient-driven degradation, enabling more targeted optimization and control strategies.

Risks of testing only the finished product:

When API stability is not evaluated in parallel:

• Degradation may be misattributed to formulation excipients
• False conclusions about formulation performance may arise
• Root causes of impurity generation may remain unidentified
• Regulatory bodies may challenge impurity justifications

Running concurrent stability studies helps build a detailed degradation profile and supports robust impurity control justifications.

Regulatory and Technical Context:

Guidance from ICH and WHO on degradation pathway analysis:

ICH Q1A(R2) and WHO TRS 1010 mandate the use of stress testing and stability studies to understand the degradation behavior of both APIs and finished products. ICH Q3B further requires the identification and qualification of degradation products and their sources. Regulatory submissions should reflect a clear understanding of whether observed degradants stem from the API itself or are formulation-induced. This distinction is often highlighted in CTD Modules 3.2.S.7 and 3.2.P.8.3.

Inspection and dossier impact:

Auditors may inquire:

• Have you tested the API and formulation under similar conditions?
• Can you differentiate degradation due to packaging vs. formulation matrix?
• How was the degradation pathway confirmed or ruled out?

Providing parallel degradation data helps validate shelf life, impurity limits, and label storage instructions.

Best Practices and Implementation:

Design your protocol to compare API and formulation degradation:

Test the API (pure, unformulated) and finished dosage form under:

• Long-term (25°C/60% RH or 30°C/75% RH)
• Accelerated (40°C/75% RH)
• Photostability and oxidative stress (if applicable)

Use the same analytical method (preferably stability-indicating) to assess degradation behavior at identical time points.

Track impurity trends and distinguish their origin:

Compare impurity profiles:

• If an impurity appears in both API and formulation – it’s likely API-originated
• If it appears only in the formulation – it may be formulation- or excipient-induced
• Use stress testing data to confirm oxidative, hydrolytic, or thermal causes

Map degradation kinetics and calculate impurity growth rates to distinguish catalytic or synergistic effects in the formulation matrix.

Document findings and support regulatory claims:

Include:

• Comparative tables of impurity profiles for API vs. formulation
• Trend charts showing impurity levels over time
• Scientific rationale for attributing degradation sources

Reference this data in your stability summary and impurity justification section of the CTD, strengthening your impurity control strategy and supporting shelf-life extensions or formulation changes.

Running parallel stability studies on both API and formulation is a powerful approach to deconvoluting degradation pathways, supporting impurity justifications, and ensuring a deeper scientific foundation for pharmaceutical stability claims.

Why API-specific testing is crucial in FDC stability programs:

Fixed-dose combinations (FDCs) involve two or more active pharmaceutical ingredients (APIs) formulated together into a single dosage unit. While convenient for patient compliance, these formulations introduce complexities in stability testing. Each API may degrade differently, exhibit varying sensitivities to temperature or moisture, and potentially interact with other components in the formulation. Testing individual API stability ensures that degradation pathways are understood and controlled throughout the shelf life.

Risks of evaluating only the total formulation:

If stability tests only measure total potency or do not track each API independently:

• Early degradation of a single API may go undetected
• Degradation products may be misattributed or missed
• Incorrect shelf-life assignments may occur
• Regulatory questions may arise during filing or audits

This risk is heightened in FDCs where APIs differ in chemical class, stability profile, or pharmacopoeial status.

Regulatory and Technical Context:

ICH and WHO guidance on FDC stability requirements:

ICH Q1A(R2) and WHO TRS 1010 emphasize that each API in an FDC must retain its stability over the claimed shelf life. WHO guidelines for multisource products (Annex 10) clearly state that each active should be individually tested using validated, stability-indicating methods. The CTD Module 3.2.P.8.3 must include time-point assay data for each API along with impurity profiling and degradation trend analysis.

Expectations during inspections and submissions:

Regulators will expect:

• Separate assay results for each API at every time point
• Individual impurity and degradation tracking
• Data showing no cross-degradation or incompatibility

Missing or pooled data may lead to queries, data rejection, or delayed approvals—especially in global markets like the EU, US, or WHO PQ program.

Best Practices and Implementation:

Develop and validate API-specific analytical methods:

Use HPLC or UPLC methods capable of resolving each API and its impurities. Ensure:

• Method validation for linearity, specificity, and accuracy per ICH Q2(R2)
• Robustness under stress conditions (acid, base, oxidation, light, heat)
• Adequate resolution and tailing factors

Document method validation and include results in Module 3.2.S.4 and P.5.2 of the dossier.

Monitor degradation behavior under all study conditions:

Include each API in:

• Assay and related substances testing at each time point
• Impurity profiling and trending across accelerated and long-term studies
• Photostability and stress studies (as applicable)

Compare degradation rates between APIs to identify any significant imbalance or potential interaction, particularly under high-humidity or thermal stress conditions.

Report individual API stability in regulatory documents:

Include:

• Time-point assay results for each API
• Impurity tables highlighting each compound’s behavior
• Conclusion on compatibility or interaction risk

Address findings in CTD Modules 3.2.P.5.5 (Characterization) and 3.2.P.8.3 (Stability), and ensure that shelf life is assigned based on the most sensitive API’s stability data.

Evaluating individual API stability in FDCs ensures clarity, confidence, and compliance—allowing your formulation to meet therapeutic expectations and global regulatory benchmarks throughout its lifecycle.

Why residual solvent monitoring matters in API stability:

Residual solvents are organic volatile chemicals used during synthesis or purification of Active Pharmaceutical Ingredients (APIs). While they are removed during drying or crystallization, trace levels may remain. Over time, these levels may change due to evaporation, degradation, or interaction with container closure systems—potentially altering safety, purity, or pharmacopoeial compliance. Routine monitoring during stability ensures control and supports shelf-life decisions.

Potential issues caused by solvent variability:

Unexpected increases may indicate ingress or solvent generation due to degradation, while decreases may suggest evaporation through closures or moisture-driven displacement. Either case can affect toxicological compliance, especially for Class 1 and 2 solvents regulated under ICH Q3C. For genotoxic or tightly controlled solvents, variability can trigger OOS results or risk-based audit concerns.

Regulatory and Technical Context:

ICH and pharmacopoeial guidelines on solvent control:

ICH Q3C (R8) sets permitted daily exposure (PDE) limits for Class 1, 2, and 3 solvents. API manufacturers must ensure solvent content remains within specified thresholds throughout shelf life. USP , EP 2.4.24, and IP protocols guide analytical procedures, primarily using gas chromatography (GC). Stability protocols should include residual solvent testing if the API involves high-risk solvents or if prior data shows variability over time.

Regulatory audit and submission expectations:

During GMP audits or dossier reviews, regulators may request stability trend data for solvents, especially for Class 1 (e.g., benzene) or Class 2 (e.g., methylene chloride) solvents. Failure to include this data may lead to queries or requests for additional testing. In CTD Module 3.2.S.7, residual solvent stability trends should be presented alongside general impurity profiles if relevant.

Best Practices and Implementation:

Design targeted testing based on solvent class and risk:

Include residual solvent analysis in your long-term and accelerated stability protocols for APIs manufactured with Class 1 and 2 solvents. For low-risk Class 3 solvents, perform initial stability testing and then move to skip-lot or annual trending unless variability is observed. Align sampling points with standard time frames (0, 3, 6, 12, 24 months).

Use validated GC methods with appropriate detectors (FID or MS) and quantification limits below PDE thresholds.

Trend solvent levels to detect volatility or ingress patterns:

Evaluate solvent data over time to detect increasing or decreasing trends. Use statistical tools to assess whether changes are significant or remain within acceptable variability. Link findings to packaging permeability, storage conditions (temperature/humidity), and analytical reproducibility.

Flag any upward trends for further toxicological evaluation or packaging revalidation, especially for sensitive APIs or those in permeable containers.

Integrate findings into QA reviews and regulatory files:

Summarize residual solvent stability trends in your Annual Product Quality Reviews (PQRs). Include trending graphs or tables in CTD Module 3.2.S.7 (Impurities) and annotate the section to reflect long-term control. If retesting or shelf-life adjustment is needed due to solvent drift, initiate a change control and notify regulatory authorities as required.

Document all test results, raw chromatograms, method validation files, and justification for testing frequency in your quality management system (QMS).