📋 Background of the Incident

The event occurred at a mid-sized pharmaceutical company exporting APIs to the US, EU, and Indian markets. The Quality Assurance (QA) team received an FDA Form 483 observation following a routine inspection, citing “labeling inconsistencies and incorrect use of expiry date on API batch containers.”

Initial Clues:

• 📌 The Certificate of Analysis (CoA) showed a “re-test date” as 18 months post-manufacture
• 📌 The product label printed an “expiry date” of 18 months post-manufacture — matching the re-test period
• 📌 No retesting data was available; the batch was used based on visual inspection alone

This labeling error triggered an investigation and batch quarantine, and it prompted queries from overseas regulatory authorities.

🔍 Root Cause Analysis

The Quality Risk Management (QRM) team initiated a deviation investigation to identify the root cause of the mislabeling. After cross-functional review and audit trail assessment, the following contributors were identified:

• ❗ Labeling SOPs lacked clear differentiation between re-test and expiry terminology
• ❗ QA label review checklist used a generic term “validity date,” leading to misinterpretation
• ❗ The labeling system software had only one date field — leading to improper manual entry
• ❗ The QA team had insufficient training on re-test vs expiry requirements per ICH Q7

The failure was not due to an isolated incident but a combination of procedural, training, and system-level gaps.

📖 Regulatory Expectations for Re-Test vs Expiry

Global regulators such as USFDA, EMA, and CDSCO distinguish between expiry dates (for finished drug products) and re-test periods (for APIs or intermediates).

Misusing these terms can mislead customers and regulatory inspectors — and may cause unsafe drug use if expired materials are mistaken for re-testable ones.

🔧 Corrective and Preventive Actions (CAPA)

To address the non-compliance, the company implemented a comprehensive CAPA plan:

Corrective Actions:

• ✅ Recalled mislabeled API containers from distribution chain
• ✅ Updated labels with accurate “Re-test by” wording per region-specific requirements
• ✅ Trained QA, QC, and warehouse staff on proper date terminology

Preventive Actions:

• ✅ Revised SOPs for labeling APIs and intermediates
• ✅ Implemented dual-date fields in the labeling software (re-test and expiry)
• ✅ Updated label approval checklists to explicitly mention both dates

The CAPA actions were submitted to the FDA and CDSCO with supporting documentation and evidence of effectiveness.

🛠️ Technology and Digital Tools Involved

One overlooked contributor was the legacy labeling software used across production and packaging. It only allowed a single date entry, with no field-specific labeling logic. This was addressed through a digital validation project.

• 💻 New software with dual date validation was deployed
• 💻 Audit trail functionality was enabled for all label edits
• 💻 Role-based approval workflows were implemented for QA and RA

Visit pharma validation resources to understand how such systems can be qualified under GMP standards.

📊 Audit Outcome and Regulatory Closure

After the CAPA was implemented, the FDA conducted a follow-up audit. The following outcomes were reported:

• ✅ No further observations on labeling practices
• ✅ CAPA found effective and sustainable
• ✅ Training records and SOP revisions verified
• ✅ System enhancements accepted by auditors

This closure not only restored the company’s compliance status but also strengthened its internal control framework around re-test and expiry date management.

📑 Lessons Learned and Best Practices

• 💡 Labeling software must accommodate both expiry and re-test fields separately
• 💡 SOPs should provide clear definitions and usage of re-test vs expiry
• 💡 QA review checklists must explicitly include both dates for verification
• 💡 Training should emphasize regulatory language differences
• 💡 Periodic internal audits should include label verification exercises

Reinforce labeling processes through regular audits, data traceability tools, and documented workflows to avoid similar errors.

👥 Stakeholder Involvement in Compliance

In this case, coordination between the QA, regulatory affairs, IT, and training departments played a critical role in addressing the issue.

Key Takeaway:

Compliance is not the responsibility of one department — it requires synchronized action across multiple units to avoid, detect, and correct labeling issues.

Refer to pharma SOP writing examples for cross-functional labeling workflows and audit readiness templates.

📅 Real-World Implications of Mislabeling

This case highlights the potential risks of mislabeling due to confusion between re-test and expiry terminology:

• ❌ Product recalls and reputational damage
• ❌ Regulatory actions, import alerts, and fines
• ❌ Delayed approvals in global markets
• ❌ Loss of customer confidence

Such incidents can be avoided through technology, SOP clarity, training, and audit preparedness.

📚 Conclusion

Confusion between re-test dates and expiry dates is more common than expected, especially in global pharma operations. This case study demonstrates that such errors can be prevented through a structured approach: refining SOPs, using validated labeling tools, implementing cross-checks, and delivering periodic training. Regulatory expectations are clear — companies must distinguish and document both terms accurately to ensure safety, traceability, and compliance.

References:

• ICH Q7: GMP for APIs
• USFDA Labeling and Stability Guidance
• CDSCO Regulatory Requirements
• EMA Labeling Guidelines
• WHO Technical Series on Stability