Expiry vs Retest Date
Expiry date and retest date are different controls with the same intent — ensuring material is fit for use — but they imply different actions. An expiry date prohibits use beyond a fixed point; a retest date requires re-testing before further use, and (if passed) extends the usable window. ICH Q1A(R2), Q1E, Q7 §11.6 and EU GMP Annex 1 distinguish the two precisely, and confusing them is a common source of inventory write-offs and 483 findings.
01Definitions
An expiry date (also expiration date, use-by date) is the date beyond which a material should not be used. It is determined from stability data per ICH Q1A/Q1E and represents the end of the period during which the material is expected to meet its specification under defined storage conditions.
A retest date is the date by which a material must be re-examined to confirm it still meets specification — and, if it does, may continue to be used. After the retest, a new retest date is assigned. ICH Q7 §11.6 explicitly permits retest dating for APIs (drug substances) given their typically greater stability vs. drug products.
02Key differences
| Aspect | Expiry date | Retest date |
|---|---|---|
| Action at the date | Stop using; remove from stock | Quarantine, test, decide |
| Typical use | Drug products, packaged dosage forms | APIs, raw materials with known long stability |
| After the date | Material is non-conforming; usually destroyed | Material may be re-released with new retest date |
| Source | Stability programme + regulatory submission | Stability programme + ICH Q7 justification |
| Regulatory anchor | ICH Q1A(R2), Q1E | ICH Q7 §11.6 |
| Indefinite extension | No | Possible (limited cycles, with justification) |
03How dates are set
Both dates flow from the stability programme. Real-time stability data establishes the shelf life under defined storage conditions; accelerated data per ICH Q1A may support an initial proposed value pending real-time confirmation. The set value is the lesser of: (a) the calculated stability-based limit; (b) any regulatory cap (some regions cap APIs at 60 months absent justification); (c) supplier-declared limits when stricter.
04System enforcement
- Inventory blocks issuing of expired material; warns at configurable thresholds (30/60/90 days).
- Retest-due material auto-quarantines on the retest date; cannot be issued until QC re-release.
- Retest extensions limited to a configured maximum (e.g. 3 cycles) before formal supplier requalification or destruction.
- Reports surface near-expiry and near-retest-due lots for proactive QA action.
- FIFO and FEFO (first expired, first out) picking rules enforced based on expiry/retest attributes.
05Common mistakes
- Treating retest and expiry as synonyms — leads to either wasted material or use beyond stability data.
- No system block at expiry — operator can issue expired material if WMS is permissive.
- Retesting without a documented limit on cycles — material 'rolling forever' on retests is a 483 trigger.
- Retest assessment limited to assay only — should match the original full stability-indicating panel.
- Failing to capture original manufacture date — cannot compute either expiry or retest correctly.
- Inventory not split when partial use crosses an expiry — the remaining portion may quietly slip past.
06Cross-industry examples
- Pharma drug products — expiry only; typically 24–36 months per ICH Q1E evaluation.
- Pharma APIs — retest dates per ICH Q7 §11.6; commonly 24–60 months with periodic retest.
- Biopharma — expiry for drug products; short retest cycles for sensitive raw materials (e.g. media components).
- Medical device sterile components — expiry tied to sterile barrier shelf life, validated per ISO 11607.
- Food ingredients — best-before vs use-by per regional regulations; FSMA traceability ties dates to lots.
- Cosmetics — Period After Opening (PAO) symbol in addition to manufacture-based shelf life.
07How V5 Ultimate handles expiry vs retest
Frequently asked questions
Q.Can an API have both an expiry and a retest date?+
Yes — some sites assign a hard expiry as an outer envelope (e.g. 60 months) within which retest cycles operate (e.g. every 12 months). Most APIs use retest only; the outer envelope is conservative practice.
Q.What if a retest fails?+
The lot moves to Rejected. Some sites permit a single re-sample if a sampling/testing error is suspected; otherwise the lot is non-conforming and follows the disposition procedure.
Q.How many retest cycles are acceptable?+
No regulatory absolute, but the FDA and EMA view material on its third or fourth retest with scepticism. Three is a common policy cap; beyond that requires explicit risk justification.
Q.Is retest testing the same scope as release testing?+
Best practice: same stability-indicating subset of the spec. Reduced retest panels are acceptable only with documented justification and confidence that no degradation pathway is missed.
Q.How are dates handled across timezones?+
Store dates as ISO date (no time component) in the manufacturer's reference timezone defined on the material master. Display in user timezone where appropriate. Date math (expiry, retest) always uses the stored canonical date.
Primary sources
Further reading
V5 Ultimate ships with the Expiry vs Retest Date controls already wired in — audit trail, e-signatures, validation evidence. Free trial, no credit card, onboard in days, not months.