Expiry vs Retest Date

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 remain within its specification under defined storage conditions. Once passed, the material is non-conforming by definition — no testing is required to reach that conclusion, and using it is a deviation regardless of whether the material would still pass the spec.

A retest date is the date by which a material must be re-examined to confirm it still meets specification. If it passes, the material may continue to be used and a new retest date is assigned. If it fails, it moves to Rejected. ICH Q7 §11.6 explicitly permits retest dating for APIs (drug substances) on the basis that APIs tend to have well-characterised, slow degradation profiles and can be re-evaluated by analytical testing — unlike formulated drug products, where degradation is multifactorial and an end-of-shelf-life decision must be made up front.

Most confusion in industry comes from assigning the wrong control to the wrong material. The decision is not a matter of preference — it is largely dictated by the material type, the regulatory framework, and the stability data available.

1. Is the material a finished drug product, medical device, or formulated consumer good? → Use expiry only. Stability data informs a fixed shelf life; the date is in the registration.
2. Is the material an API or raw chemical with a well-characterised stability profile suitable for periodic re-evaluation? → Retest dating is permitted under ICH Q7 §11.6. Many sites combine an outer expiry envelope (e.g. 60 months) with periodic retests (e.g. every 12–24 months) within it.
3. Is the material an excipient or raw material? → Default to the supplier's declared date. If the supplier gives only a retest date, you may retest on receipt and adopt an internal retest schedule, or treat it as expiry per internal policy. Document the choice on the material master.
4. Is the material a primary packaging component (vials, stoppers, sterile barriers)? → Use expiry tied to the sterile barrier or functional shelf life, validated per ISO 11607 (devices) or supplier qualification (pharma).
5. Is the material a reference standard or impurity standard? → Use expiry; retesting reference standards is not standard practice unless explicitly justified.
6. Is the material a biological — cell bank, virus seed, biological reagent? → Typically expiry with periodic identity/potency confirmation. The control is closer to an expiry, but the underlying programme is qualification rather than stability.

ICH Q1A(R2) and Q1E

Q1A(R2) defines the stability study designs (long-term, intermediate, accelerated) and the storage conditions for each ICH climatic zone (I–IVb). Q1E covers how to evaluate the resulting data: significant change criteria, statistical extrapolation rules, and how to set a shelf life from long-term data, optionally extended using accelerated data. The shelf life set under Q1E becomes the expiry date for the drug product.

ICH Q7 §11.6 — Expiry and retest dating for APIs

Q7 §11.6 is the cornerstone of retest dating. It states that APIs may have a retest date instead of an expiry date when stability data supports it. Critically, it requires that after retest the material be used within an appropriate period — not held indefinitely — and that retest cycles be governed by a written procedure. It does not specify a maximum number of cycles; industry practice has converged on 2–3 cycles before formal supplier requalification or destruction.

FDA 21 CFR 211.137 and 211.166

211.137 requires expiration dates on drug products determined by appropriate stability testing per §211.166. The FDA does not formally regulate retest dating for APIs through 21 CFR 211 (which applies to finished drug products) — it inherits ICH Q7 by reference for API GMP. FDA inspectors expect to see retest programmes structured in line with Q7 §11.6 and supported by stability data, with clear SOPs governing the retest cycle.

EU GMP Part II and Annex 19

EU GMP Part II is essentially Q7 transposed into European GMP. Annex 19 covers reference and retention samples, which interact with retest dating: retention samples are held for one year past expiry of the corresponding batch, and retest dates affect when that clock starts.

WHO TRS 1010 Annex 10

WHO's stability guidance largely harmonises with ICH but adds explicit guidance for climatic Zones III/IVa/IVb (hot and humid markets) — relevant for any global supply chain where finished products or APIs ship into Africa, the Middle East, South Asia, and Southeast Asia. Expiry/retest periods established only for Zones I/II may not hold under Zone IV stress conditions and require additional study before they can be assigned for those markets.

Both dates flow from the stability programme. The set value is the lesser of: (a) the calculated stability-based limit; (b) any regulatory cap (some markets cap APIs at 60 months absent specific justification); (c) supplier-declared limits when stricter; (d) any container/closure limit.

Worked example — API X, retest interval

1. Long-term stability study: 0, 3, 6, 9, 12, 18, 24, 36 months at 25°C/60% RH. Accelerated: 0, 3, 6 months at 40°C/75% RH.
2. Assay results trend from 99.8% at t=0 to 98.9% at 36 months long-term — no significant change. Total impurities trend from 0.12% to 0.18%, well within the 0.5% spec.
3. Per ICH Q1E, with three batches showing no significant change over 36 months, retest period may be extended up to 2× the long-term data — capped at +12 months. Initial retest interval: 48 months.
4. Regulatory cap in target markets: 60 months absent additional justification. 48 < 60, so no cap applied.
5. Supplier internal policy: maximum 3 retest cycles per lot. After cycle 3 (cumulative age 192 months), material must be requalified by full release testing against current spec or destroyed.

For a drug product, the same data flow ends in a fixed expiry: typically the long-term data point at which the spec is still met with statistical confidence, occasionally extended using accelerated data per Q1E rules. Once submitted in the registration, that expiry becomes the immovable label date.

A correctly configured ERP/QMS/LIMS enforces expiry and retest controls without depending on operator vigilance. The minimum bar:

• Inventory blocks the issuing of expired material under all conditions. Override requires QA e-signature against a documented deviation — never silent.
• Expiry warnings fire at configurable thresholds (commonly 30/60/90 days) so QA and planning can act proactively.
• Retest-due material auto-quarantines at midnight on the retest date; cannot be issued until QC re-release.
• Retest cycles are counted per lot and capped per material (commonly 3). Exceeding the cap forces a supplier requalification or destruction decision, with full justification recorded.
• Near-expiry and near-retest dashboards surface action lists 30/60/90 days ahead, broken down by material, location, and value.
• FEFO (first expired, first out) picking rules use the lower of expiry or retest as the effective consumption date — so retest-due material is prioritised for use before it auto-quarantines.
• Partial lot consumption splits the residual into its own inventory record with the parent's dates intact, preventing remnants from slipping past unnoticed.
• The full date lineage — original manufacture date, supplier-declared dates, internal recalculations, every retest cycle and disposition — is part of batch genealogy and visible to auditors in one click.

Expiry/retest is a high-frequency 483 and EU GMP deficiency topic. Patterns that recur in published warning letters:

• No documented limit on retest cycles — material observed on its 5th or 6th retest with no requalification trigger.
• Retest panel reduced to identity + assay only, missing impurity and degradation indicators required by the original spec.
• Inventory permitting issuance of expired material with no override audit trail.
• Retest extensions applied retroactively after the retest date had already passed, with the material having been used in the interim.
• Material master defaults inconsistent with the registered shelf life — newer lots inheriting the wrong interval after a spec change.
• Supplier CoA carrying only a retest date interpreted internally as an expiry, leading to premature destruction (not a regulatory finding but an economic one).
• Different storage conditions in practice vs. in the stability programme — fridge vs. ambient, controlled-room vs. uncontrolled warehouse — invalidating the basis for the assigned date.
• No retention sample held for the full period required by Annex 19, because the retention clock was started from retest date instead of expiry envelope.

"Your firm failed to establish written procedures designed to assure that drug products conform to appropriate standards of identity, strength, quality, and purity. Specifically, your firm released [API] for use beyond its retest date without conducting any retesting."

• Treating retest and expiry as synonyms — leads to either wasted material or use beyond stability data. Fix: distinct fields on the material master and on every lot record, never a single 'expiration' field.
• No system block at expiry — operator can issue expired material if the WMS is permissive. Fix: hard block with audited override.
• Retesting without a documented cycle cap — material 'rolling forever' on retests is a 483 trigger. Fix: configurable cap per material (default 3), enforced in software.
• Retest assessment limited to assay only — should match the original full stability-indicating panel unless reduced scope is explicitly justified. Fix: retest sampling plan generated from spec, not a free-form QC choice.
• Failing to capture original manufacture date — cannot compute either expiry or retest correctly. Fix: manufacture date required on lot creation, validated against supplier CoA.
• Inventory not split when partial use crosses an expiry — the remaining portion may quietly slip past. Fix: every issue creates a residual inventory record with parent lot dates.
• CoA dates entered manually with no second-person check — typo risk. Fix: structured CoA capture (OCR or supplier portal) with QA verification.
• Date math done in user timezone rather than canonical site timezone — material flipping to expired a day early or late. Fix: store and compute in ISO date with site reference timezone.

• Pharma drug products — expiry only; typically 24–36 months per ICH Q1E evaluation. Stored in registered packaging under registered conditions.
• Pharma APIs — retest dates per ICH Q7 §11.6; commonly 24–60 months with periodic retest at 12–24 months. Outer expiry envelope often applied as conservative practice.
• Biopharma drug substances — retest dating at short intervals (3–12 months) for sensitive proteins; full release testing on retest given the cost of a wrong decision.
• Biopharma raw materials — short retest cycles for cell culture media components and growth factors; long-stability buffers may use simple expiry.
• Medical device sterile components — expiry tied to sterile barrier shelf life, validated per ISO 11607-1 with accelerated aging per ASTM F1980.
• Medical device non-sterile — often no expiry (durable components) or long expiry (5–10 years) tied to functional or material aging studies.
• Food ingredients — best-before vs. use-by per regional regulations; FSMA traceability in the US ties dates to lots through every node of the supply chain.
• Dietary supplements — expiry per 21 CFR 111; manufacturers must have stability data or justification for any expiration claim made on label.
• Cosmetics — Period After Opening (PAO) symbol in addition to manufacture-based shelf life; expiry mandatory for products with shelf life <30 months in EU per Cosmetic Regulation 1223/2009.
• Cannabis (regulated markets) — expiry typically required by state/provincial regulation; some jurisdictions accept retest dating for bulk inputs and concentrates.
• Veterinary pharma — same Q7/Q1A framework with VICH harmonisation; species-specific stability considerations for some formulations.

The Certificate of Analysis (CoA) is the dominant transmission channel for expiry and retest dates between manufacturers, distributors, and end users. Best practice:

• Both dates explicit on the CoA where applicable — never inferred from manufacture date alone.
• Storage conditions stated on CoA in the same units and ranges as the stability programme.
• Re-issued CoAs after a retest carry both the original manufacture date and the new retest date, with the retest history appended (not replacing prior history).
• Label reflects the controlling date — for APIs with both an outer expiry envelope and a retest schedule, both appear, with the nearer-term retest highlighted as the action date.
• Electronic CoAs (PDF + structured data) reduce transcription error vs. manually keyed values; supplier portals or EDI feeds eliminate it entirely.