Documenting Retest vs Expiry Terms for Bulk APIs in Pharma

Thu, 10 Jul 2025 20:23:39 +0000

In pharmaceutical manufacturing, accurately documenting the shelf life of active pharmaceutical ingredients (APIs) is crucial. However, confusion often arises between the terms retest date and expiry date—particularly for bulk APIs. Misuse or misinterpretation of these terms can lead to compliance issues, rejected dossiers, or product recalls. This tutorial clarifies the regulatory expectations and GMP practices for documenting retest and expiry terms for APIs.

Why the Distinction Matters

Authorities like EMA, CDSCO, and USFDA expect clear and consistent usage of “retest” and “expiry” terms in registration dossiers, COAs, and GMP documentation. Mislabeling or incorrect document trails can lead to:

❌ Product rejection during inspections
❌ Questions during market authorizations
✅ Stability failures due to extended use of expired APIs

Understanding when to use “retest” vs “expiry” is foundational to GMP and regulatory compliance.

Definitions: Retest vs. Expiry for APIs

Retest Date: The date up to which the API should be tested again to verify compliance before use. If the material passes, it may still be used.
Expiry Date: The date beyond which the API should not be used. No retesting is permitted; product must be discarded.

The use of either depends on the nature of the material and its regulatory status. Most APIs are assigned a retest date, not an expiry date, unless otherwise mandated.

Regulatory Guidance: ICH and USFDA Perspectives

ICH Q7 (GMP for APIs) and USFDA guidelines distinguish between retest and expiry terms:

✅ For APIs: Assign retest date unless stability data mandates an expiry
✅ For sterile APIs or those in dosage form: Use expiry date
✅ Retesting after assigned date is permitted if supported by current data

ICH Q1A also supports this distinction based on stability data generated under long-term and accelerated conditions.

Step-by-Step Documentation in GMP Systems

To ensure regulatory compliance, companies should document retest and expiry terms systematically across their QMS, ERP, and labeling systems.

Step 1: Assign Based on Stability Protocol

✅ Determine retest period from real-time stability data
✅ Evaluate if any degradation leads to fixed expiry
✅ For short-shelf-life or hygroscopic APIs, consider expiry

Include these terms in your SOP on API stability assignment.

Step 2: COA and Batch Records

Ensure COA reflects either:

✅ “Retest Date: MM/YYYY”
or
✅ “Expiry Date: MM/YYYY”

Do not use both unless specifically required by the customer or agency.

Step 3: Label Control

✅ Bulk containers must display retest/expiry date visibly
✅ Include storage condition (e.g., Store below 25°C)
✅ Ensure retest/expiry is visible even after repacking

Step 4: ERP and Inventory Control

Configure ERP systems to flag API lots approaching retest date. Include:

✅ Auto-alerts 30/60/90 days prior to retest date
✅ Retest scheduling as a mandatory QA activity
✅ Expiry block to prevent material usage post expiry

This integration ensures GMP control over inventory use and prevents inadvertent use of expired raw materials.

Step 5: Retesting Protocol and Requalification

If retest is assigned, companies must have SOPs for requalification testing. Include:

✅ List of tests to be repeated (e.g., assay, related substances, loss on drying)
✅ Re-test intervals based on data trend
✅ Clear acceptance criteria

Retest must be completed before usage or manufacturing scheduling. No “in-process” adjustment is permitted to extend shelf life.

When to Use Expiry Instead of Retest

Assign an expiry date instead of retest date if:

✅ API shows time-dependent degradation with no recovery potential
✅ Sterile APIs or high-risk materials (e.g., controlled substances)
✅ Regulatory filing mandates fixed expiry (e.g., in MA applications)

Once an expiry date is assigned, the material cannot be used beyond it—even if testing passes.

Labeling Case Study: Misuse of Expiry vs. Retest

In a recent USFDA inspection, a company was cited for labeling a bulk API with an expiry date but continuing to use the lot after it passed a retest. This violated their own SOP and led to a Form 483 observation.

Lesson: Once expiry is assigned, no retest can override it.

Training and SOP Best Practices

Ensure your QA and warehouse teams are trained on:

✅ Differences in terminology and use
✅ How to read COA and label expiry/retest dates
✅ How to request requalification testing

Integrate these procedures into your GMP training programs and product release SOPs.

Documentation Audit Checklist

✅ Is the retest or expiry clearly stated in COA?
✅ Are labels consistent with documentation?
✅ Is there an SOP for assigning shelf life?
✅ Does ERP restrict expired material usage?
✅ Are requalification procedures established?

Conclusion

Retest and expiry dates are not just terminology—they are critical compliance points in the pharmaceutical lifecycle of APIs. Proper understanding, usage, and documentation of these terms ensure that GMP controls are effective and regulatory filings are accepted without delay.

Pharma teams must embed clear guidelines in SOPs, train stakeholders, and validate ERP and QMS systems to ensure consistent expiry/retest controls for all API lots used in production.

retest vs expiration date pharma – StabilityStudies.in