This checklist-style article serves as a reference for pharmaceutical QA professionals to implement and audit robust systems for re-test documentation. It aligns with ICH Q7, GMP requirements, and other global regulatory expectations.

1. Re-Test Assignment Documentation

• ☐ Stability study data available for 3 batches (minimum)
• ☐ Signed QA-reviewed protocol for storage and test intervals
• ☐ Summary report for data trend analysis and justification
• ☐ Assigned re-test date documented in Quality Overall Summary (QOS)
• ☐ Change control raised for new re-test period implementation

2. CoA and Batch Record Updates

• ☐ “Re-test Before” clearly mentioned on Certificate of Analysis (CoA)
• ☐ Date format used: DD-MMM-YYYY (e.g., 30-JUN-2026)
• ☐ Internal batch records reflect assigned re-test period
• ☐ Re-test assignment rationale attached with each batch record
• ☐ Document version control maintained in the QMS system

3. Warehouse Labeling and Storage

• ☐ Container labels include bold “Re-test Before” field
• ☐ Storage conditions indicated on label: 25°C/60% RH or as per protocol
• ☐ Label checked during QA line clearance of storage areas
• ☐ Separate identification of nearing re-test date inventory
• ☐ Barcode system links inventory to re-test database (if digital system exists)

4. Re-Test Scheduling System

• ☐ QA master log of all API and intermediate re-test dates
• ☐ Calendar reminders set for re-test due dates
• ☐ Responsibility assigned for sample withdrawal and testing
• ☐ Periodic QA review to identify materials approaching re-test window
• ☐ Re-test results logged with timestamp and analyst signature

5. Requalification and Result Documentation

• ☐ Retesting results meet the current specifications in the DMF or QMS
• ☐ Analyst sign-off with review by QC lead
• ☐ QA approval documented before re-approval for further processing
• ☐ New CoA generated (if required) with updated re-test period
• ☐ Batch disposition note added to ERP system post-approval

For CoA formatting best practices, refer to pharma SOP templates.

6. Regulatory Filing and CTD Updates

• ☐ Re-test periods declared in Module 3.2.S.7 of CTD format
• ☐ Summary of stability data included in Module 3.2.R
• ☐ In-country variation filings updated post re-test period extension
• ☐ Re-test assignment linked to internal justification note
• ☐ Submission status tracked in regulatory tracking tool

7. SOP Coverage and QA Training

• ☐ Re-test period assignment covered under stability protocol SOP
• ☐ Retesting flow covered under warehouse material handling SOP
• ☐ Labeling requirements defined in packaging SOPs
• ☐ Annual QA training includes re-test documentation guidelines
• ☐ Mock audits simulate re-test data traceability checks

Refer to GMP QA training modules to stay updated on inspection readiness for re-test documentation.

8. Change Control and Deviation Handling

• ☐ Any re-test date extension supported by controlled change
• ☐ Deviation documented for missed or delayed re-test
• ☐ Risk assessment performed for late retesting events
• ☐ CAPA raised for procedural lapses and QA-reviewed
• ☐ Deviations summarized in annual product quality review (APQR)

9. Audit Trail and Inspection Readiness

• ☐ Electronic audit trail for digital re-test logs maintained
• ☐ Paper-based logbooks verified and controlled
• ☐ All changes to re-test period traceable to source data
• ☐ Re-test compliance included in internal audits
• ☐ Inspection readiness folder created for re-test documentation

10. Cross-Linking with Other Departments

• ☐ Regulatory Affairs notified of re-test updates for filings
• ☐ Production department advised of material re-approval
• ☐ QC team aligned on re-test sampling and analysis
• ☐ Warehouse trained to handle re-test-labeled materials
• ☐ Quality Council reviews re-test issues quarterly

Sample Template: API Re-Test Logbook Entry

Best Practices

• Establish a centralized QA master sheet for all re-test batches
• Use unique re-test date codes for digital traceability
• Conduct annual review of re-test process effectiveness
• Integrate re-test logs into APQR and product lifecycle management
• Document rationale for any re-test date deviation or extension

QA teams can refer to clinical protocol compliance logs for analogous documentation controls in R&D settings.

Conclusion

Documenting re-test periods is not just a regulatory formality—it ensures that pharmaceutical materials remain suitable for use over time. A structured QA checklist enhances traceability, reduces risk of non-compliance, and prepares your team for regulatory inspections. By following this 10-point documentation framework, pharma companies can establish a gold-standard quality assurance system for re-test management.

References:

• ICH Q7, Q1A
• Re-Test Period GMP Documentation
• QA SOPs and CoA Templates
• Training & Validation Protocols
• Regulatory Submission Guidelines

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.

References:

• ICH Q7: GMP for APIs
• USFDA 21 CFR Part 211
• EMA API Stability Guidelines
• CDSCO Drug Substance Documentation