Navigating Retest Periods and Expiry Dates in Regulatory Submissions
Updated September 2025 — A compliance-ready guide for CMC teams to correctly justify and document retest periods (drug substance) and expiry dates (drug product) in eCTD dossiers.
When regulators review your dossier, they expect absolute clarity on one deceptively simple distinction: retest period vs. expiry date. For drug substances, you assign a retest period — the time during which the material is expected to remain within specification if stored under defined conditions. For drug products, you assign an expiry date — the time beyond which the product must not be used. Confusing the two is one of the most common CMC deficiencies cited in FDA and EMA reviews.
This guide provides a step-by-step framework to properly design, justify, and document retest and expiry claims in alignment with ICH Q1A(R2), Q1E, and WHO stability guidelines. Whether you are drafting Module 3.2.S.7 (drug substance stability) or Module 3.2.P.8 (drug product stability), this article gives you the checklist regulators expect to see.
Defining the Terms Clearly
- Retest Period: The timeframe during which a drug substance can be re-examined and, if still compliant, used in manufacture. It assumes re-testing, not guaranteed use beyond the date.
- Expiry Date: The final date a finished drug product can be used safely and effectively; no further testing extends this claim.
ICH explicitly notes this distinction, but sponsors frequently blur the lines, leading to regulatory questions, inspection findings, and label corrections.
Where Retest and Expiry Dates Live in the CTD
- Module 3.2.S.7 (Stability): Presents stability data and justification for the proposed retest period of the API.
- Module 3.2.P.8 (Stability): Provides real-time/accelerated data and justification for the expiry date of the finished product.
- Module 2.3 (Quality Overall Summary): Summarizes and harmonizes claims for quick reviewer reference.
- Labeling (Module 1): Storage statements and expiry dates as approved, which must match stability data conclusions.
Designing Stability Programs That Support Both
To justify retest and expiry claims, sponsors must align with ICH Q1A(R2) expectations:
- Use at least three production-scale batches for both API and finished product studies.
- Test at long-term (e.g., 25°C/60% RH), intermediate (30°C/65% RH), and accelerated (40°C/75% RH) conditions as applicable.
- Apply validated, stability-indicating methods capable of detecting degradation products.
- For APIs, emphasize chemical purity, assay, and physical stability (e.g., polymorph transitions).
- For finished products, include assay, degradation products, dissolution, microbiological quality, and physical parameters.
Statistical Justification of Periods and Dates
ICH Q1E guides the statistical treatment of stability data:
- Regression analysis: Model key attributes over time with confidence intervals to predict compliance.
- Pooled vs. individual slopes: Justify batch pooling or provide individual batch expiry estimates.
- One-sided confidence limits: Ensure 95% lower confidence bounds support claims.
- Significant change criteria: Predefine thresholds such as ≥5% assay drop or OOS impurity results.
For APIs, this results in a retest period. For drug products, this defines the expiry date.
Regulatory Expectations and Common Deficiencies
- Mislabeling retest as expiry (or vice versa): A frequent FDA finding that undermines credibility.
- Expiry exceeds observed data: Submitting a 36-month claim with only 12-month long-term support.
- No intermediate condition data: Especially problematic if accelerated studies fail.
- Bracketing/matrixing poorly justified: Regulators challenge unsupported assumptions.
- Data gaps at submission: Agencies may accept provisional approvals but cut shelf life until full data arrives.
Case Examples
Case 1 — API Retest Period (EMA): A crystalline API showed stable assay and impurities for 36 months at 25°C/60% RH. EMA accepted a 36-month retest period, conditional on ongoing stability reporting.
Case 2 — Expiry Date (FDA): An oral suspension exhibited microbial growth risk after 18 months. FDA approved the product but restricted the expiry to 12 months with a label warning, pending reformulation data.
Case 3 — WHO Prequalification: A generic injectable filed with mismatched retest/expiry definitions. WHO requested resubmission with corrected labeling and SOP alignment before granting prequalification.
10-Step Compliance Checklist
- Define retest (API) vs expiry (drug product) upfront in development plans.
- Design stability protocols per ICH Q1A(R2), covering all required conditions.
- Include three representative commercial-scale batches in both studies.
- Apply validated, stability-indicating analytical methods.
- Trend results statistically per ICH Q1E, using regression and confidence limits.
- Apply pooling only with statistical justification; otherwise, treat batches separately.
- Align stability data with claims in CTD Modules 3.2.S.7, 3.2.P.8, and 2.3.
- Ensure labeling reflects claims exactly — no mismatch tolerated.
- Maintain ongoing stability commitments post-approval.
- Train staff on the distinction to prevent misstatements in submissions and inspections.
Key Takeaways for CMC Teams
The difference between retest and expiry is more than semantics; it is a regulatory expectation tied to quality, safety, and labeling integrity. APIs get retest periods, drug products get expiry dates. Confuse them, and you risk deficiencies, label restrictions, and credibility loss. Build ICH-compliant protocols, defend claims statistically, and maintain alignment across CTD modules and labels — this is how dossiers pass without delay.