Potency retest & expiry dating for raw materialsRetest Date vs Expiry Date (ICH Q1A / Q7)
A retest date is a promise to re-check, not a promise the material is still good — under ICH Q7 §11.6 and ICH Q1A(R2), a raw material past its retest date must be re-sampled and re-assayed before it can be used, and every requalification that changes the measured potency has to propagate a new potency factor to every open work order drawing on that lot.
How does Potency retest & expiry dating for raw materials apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01Retest date vs expiry date — the distinction that drives everything else
An expiry date is terminal. Past it, the material may not be used, full stop, regardless of what any test shows — it reflects a defined, data-supported point beyond which the manufacturer cannot claim the material still meets specification, typically because degradation is understood to be irreversible, monotonic, and unrehabilitated by mere confirmation of current quality. Finished drug product carries an expiry (shelf-life) date for this reason.
A retest date is different in kind. It marks the point by which a material must be re-examined — re-sampled and re-tested against its full specification, or against the subset of tests relevant to the material's known degradation pathway — before it can be used further. If the material still conforms, it can be released for continued use with a newly assigned retest date (or, per site policy, a defined maximum number of retest cycles or a hard-stop total shelf life). ICH Q7 §11.6 states this directly for APIs: materials held beyond an established period should be tested to confirm continued suitability.
| Attribute | Retest date | Expiry date |
|---|---|---|
| What it means | Must re-test before continued use; conforming result extends usability | Terminal — usability ends regardless of test result |
| Typical application | APIs, many raw materials/intermediates | Finished drug product; materials known to irreversibly degrade past a point |
| Governing guidance | ICH Q7 §11.6, ICH Q1A(R2) | ICH Q1A(R2), ICH Q1E, product-specific stability protocol |
| Action when date is reached | Sample and assay; conforming result → new retest date and updated potency value | Reject / do not use; no test can rehabilitate |
| Potency consequence | New assay result typically changes the potency factor used in dispensing | Not applicable — material is not used |
02The regulatory basis for retest periods
| Clause | What it establishes |
|---|---|
| ICH Q7 §11.6 | APIs held beyond the established retest period should be tested for continued suitability before use in the manufacture of drug product; results feeding this decision must be documented. |
| ICH Q1A(R2) §2.1.7 / §2.2 | Defines retest period as the point of time after which samples of the drug substance should be re-examined to ensure the material is still suitable for use; requires long-term, intermediate, and accelerated stability data to justify the assigned period. |
| ICH Q1E | Provides the statistical framework (regression against stability data, appropriate storage-condition bracketing) used to establish and extend a retest period or shelf life beyond directly observed data. |
| 21 CFR 211.87 | US GMP requirement that components, containers, and closures subject to deterioration be retested at appropriate intervals to assure suitability for use. |
| 21 CFR 211.166 | Requires a written stability testing program that provides a basis for assigning expiration/retest dating in the first place. |
| EU GMP Ch.5 §5.40 | Starting materials should be received against approved specifications and re-checked as appropriate over time; ties into local requalification SOPs. |
| WHO TRS 1044, Annex 3 | International guidance on API stability testing that many non-ICH-region regulators reference for retest-period justification. |
A retest period is not an arbitrary administrative shelf number — it is a statistically derived conclusion from real stability data (long-term storage under labelled conditions, supplemented by accelerated and intermediate conditions per the ICH Q1A(R2) storage-condition matrix), extrapolated per ICH Q1E only as far as the data statistically support.
03Designing a requalification protocol
Requalification is a formal, documented event — not an ad hoc 're-run the assay and see' exercise. A defensible protocol specifies, in advance, what gets tested, how the material is sampled, and what criteria govern the outcome.
- Sampling — pull from a statistically representative set of containers per the site's sampling plan (not just the top container in the pallet), following the same identity-confirmation steps as an initial receipt sample, since a lot can develop container-to-container heterogeneity over long storage.
- Test panel — at minimum, potency/assay against specification; for materials known to be moisture-sensitive, a moisture re-check (LOD or Karl Fischer); for materials with known degradation pathways, a targeted impurity/degradation-product panel rather than a full release panel re-run, justified by the material's characterized stability profile.
- Acceptance criteria — the same specification the material was originally released against, unless a science-based, approved alternative applies (e.g., an impurity limit that only becomes relevant after extended storage and is added specifically for requalification testing).
- Retest interval assignment — the requalified retest date is typically set using the same interval logic as the original (e.g., another 12 or 24 months) unless site policy or stability data dictate a shorter interval for materials nearing the edge of their overall supported storage duration.
- Cycle limits — many quality systems cap the number of times a given lot may be requalified (e.g., two extension cycles) or impose an absolute total-storage-time ceiling, because repeated retesting of the same container without evidence the underlying degradation model still holds becomes scientifically indefensible past a certain point.
- Documentation — the requalification result, the new retest date, and (if changed) the new potency value must be recorded on the lot record with the same rigor as an original CoA disposition, including QA review and approval before the lot re-enters usable inventory.
04Potency drift on ageing actives
Most actives do not degrade instantly at a cliff edge; they drift, typically following first-order or pseudo-first-order kinetics for a hydrolytically or oxidatively unstable molecule, or much more slowly and near-linearly for a chemically robust one. The retest date is set at the point where the manufacturer's stability model no longer confidently predicts the material remains within its assay specification without a fresh check.
| Driver of drift | Typical effect on measured potency | Mitigation |
|---|---|---|
| Hydrolysis (moisture ingress) | Assay declines as parent compound converts to hydrolysis products; LOD/KF often rises in parallel | Moisture-barrier packaging; re-check LOD alongside potency at requalification |
| Oxidation | Assay declines; related-substance/impurity profile shows new oxidative degradants | Inert headspace/antioxidant packaging; track impurity trend, not just assay |
| Photodegradation | Assay declines if exposed to light during storage or repeated container opening | Light-protective containers; minimize repeated exposure during sampling |
| Polymorphic or hydrate-form conversion | Assay may appear stable while physical form (and sometimes bioavailability-relevant properties) shifts | Include a form-specific test (XRPD, DSC) in the requalification panel when relevant |
| Botanical marker-compound decay | Marker percentage drifts independent of bulk mass; can be faster and less predictable than a synthetic API | Tighter requalification interval and marker-specific re-assay; treat with the same rigor as potency factor for synthetics |
Whatever the mechanism, the requalification assay result — not the original receipt CoA value — is the number that must drive every subsequent dispense calculation. A material that assayed at 99.8% on receipt and requalifies at 97.1% eighteen months later has a materially different potency factor, and every open recipe consuming that lot needs to reflect the new number, not the stale one.
05CoA retest dates and supplier storage-claim limits
A supplier's CoA typically states a retest date derived from the supplier's own stability data and labelled storage conditions (temperature, humidity, container/closure system). That date is only valid if the receiving site actually stores the material within those labelled conditions — a material rated for storage at controlled room temperature that spends time in an uncontrolled warehouse corner during a heat event has an unverified basis for its stated retest date, even if the calendar date hasn't been reached yet.
- Verify the supplier's storage-condition claim matches the site's actual storage location and monitored temperature/humidity history for the full duration the lot has been on hand.
- Treat any excursion outside labelled storage conditions as a trigger for an out-of-condition assessment — potentially an accelerated requalification — independent of the calendar retest date.
- Do not extend a supplier-assigned retest date on the strength of the site's own data unless the site has performed (or has access to) stability data specifically supporting that extension; a site cannot unilaterally decide a supplier's material is good for longer without its own scientific basis.
- Where a material is repackaged into smaller in-house containers, treat the repack as a new event: verify whether the supplier's original retest date and container/closure basis still apply to the new packaging, since a different container can have different moisture/oxygen barrier properties.
06How a re-assay updates the potency factor and downstream charge
Requalification is only complete, from a dispensing-control standpoint, when the new assay value has actually propagated into the potency factor the dispensing system uses — not just filed in the lab's LIMS as a passed result.
- Lab performs the requalification assay and records the result under the standard result-review/QA-approval workflow, exactly as for an original receipt assay.
- The lot record's potency factor is recomputed from the new assay value (PF = reference potency ÷ new measured potency, on the correct basis — see potency factor for the anhydrous/as-is/marker/activity conventions).
- The lot's retest date is updated to the new requalification-derived date, and the prior potency value and retest date are retained in the lot's change history for audit reconstruction.
- Every open work order or dispense queue item referencing that lot is flagged for the operator/kiosk to recompute the adjusted dispense target using the new potency factor before any further weighing occurs against that lot.
- If material from the lot was already dispensed under the old potency factor before requalification, that historical transaction is not retroactively altered — the batch record stands as executed — but the deviation/impact assessment for that batch should consider whether the old PF was still within tolerance of the new, requalified value.
07Quarantine, blocking, and propagation rules
The system-level controls that make requalification actually work in practice come down to a small set of blocking rules that must all be enforced consistently.
| Rule | What it prevents |
|---|---|
| Lot auto-quarantines on reaching its retest date, with no manual override without QA disposition | Silent continued use of a lot that hasn't been re-checked |
| Weigh transaction re-validates lot status at time of weighing, not only at work-order creation | Dispensing against a lot whose retest date lapsed mid-campaign |
| Requalification-approved PF change immediately updates all open work orders referencing the lot | New batches computed on a stale potency value |
| Requalification cycle counter enforced against a site-defined maximum | Indefinite re-testing of a lot without a fresh scientific basis |
| Out-of-condition storage excursion auto-flags the lot for accelerated requalification review | Reliance on a calendar retest date invalidated by an undocumented storage excursion |
| Repack event triggers a re-evaluation of the retest-date basis for the new container | Assuming a repackaged material inherits an unverified retest basis |
08Audit findings that recur around retest and requalification
- Material dispensed after its retest date because the dispensing system only checked the date when the work order was created, not at the moment of weighing.
- Requalification performed and passed, but the potency factor on open work orders was never recomputed, so subsequent batches were charged on the pre-requalification value.
- Repeated requalification of the same lot with no documented scientific basis (no ongoing stability data, no cycle limit) for continuing to extend it.
- A material with a documented storage-condition excursion (temperature/humidity) still released for use on the strength of an unmodified original retest date.
- Repackaged material carrying forward the original supplier retest date with no assessment of whether the new container/closure system supports the same period.
- Retest date and expiry date used interchangeably in SOPs or batch records, leading operators to believe a past-expiry material could be 're-tested back into use.'
- Requalification protocol testing only potency, omitting a moisture or degradation-product check for a material whose known instability mechanism involves more than simple potency loss.
Frequently asked questions
Q.Can an API's retest date simply be extended indefinitely as long as it keeps passing assay?+
No. Extension requires an ongoing scientific basis — supporting stability data (from an ongoing program or comparable historical data) and, in most well-run quality systems, a defined maximum number of requalification cycles or an absolute total-storage ceiling. Indefinite extension based only on 'it keeps testing fine' without supporting stability rationale is a recognized audit weakness.
Q.Is a retest date the same thing as a shelf-life date?+
No. Shelf life (expiry) is terminal and applies most commonly to finished drug product. Retest date applies typically to APIs and many raw materials, and means the material must be re-examined before continued use — a conforming re-examination can extend usability, which a shelf-life expiry cannot.
Q.What happens to a batch that was dispensed using a lot's old potency factor right before that lot was requalified with a different value?+
The already-executed batch record stands as it was performed — it is not retroactively altered. However, the deviation or impact-assessment process should evaluate whether the potency factor used at the time was close enough to the newly requalified value to fall within the formulation's tolerance, and document that assessment.
Q.Does a raw material that has never been opened still need requalification at its retest date?+
Yes. The retest date is based on time and storage conditions, not on whether the container has been opened. An unopened container can still undergo the same degradation mechanisms (moisture ingress through packaging, slow chemical decay) that the retest period is designed to catch.
Q.Who is authorized to approve a requalification result and release the lot for continued use?+
The Quality Unit, following the same review-and-approval rigor applied to an original lot release — typically including confirmation the test panel matched the approved requalification protocol and that the new retest date and (if changed) potency value have been correctly recorded on the lot record before it re-enters usable inventory.
Q.Why does a temperature excursion during storage matter if the calendar retest date hasn't been reached yet?+
The retest date is only valid as a prediction if the material was actually stored within the conditions the underlying stability data support. An excursion outside those labelled conditions invalidates the basis for trusting the calendar date and should trigger an out-of-condition assessment, potentially including an accelerated re-assay, independent of how much time remains before the stated retest date.
Q.Does repackaging a raw material into smaller containers reset its retest date?+
Not automatically in either direction — repackaging does not by itself extend or shorten the retest date, but it does require an assessment of whether the new container/closure system provides equivalent protection to the one the original retest period was established against. If it does not, a shorter interval or additional testing may be warranted.
Primary sources
- ICH Q7 §11.6 — Reprocessing
- ICH Q7 §11.5 / §11.6 — Stability monitoring & retest dates
- ICH Q1A(R2) — Stability Testing of New Drug Substances and Products
- ICH Q1E — Evaluation of Stability Data
- 21 CFR 211.87 — Retesting of approved components, drug product containers, and closures
- 21 CFR 211.166 — Stability testing
- EU GMP Part I, Chapter 5 §5.40 — Starting materials
- WHO TRS 1044, Annex 3 — Stability testing of active pharmaceutical ingredients and finished pharmaceutical products
Further reading
- Potency factorThe lot attribute a requalification re-assay updates.
- Assay-adjusted chargeThe dispense-side calculation every open work order must re-run against the new potency.
- Loss on Drying (USP <731>)Moisture re-check often accompanies a potency re-assay at requalification.
- Stability programThe broader data set retest-period justification draws on.
- Weigh and dispenseThe transaction that must be blocked when a lot's retest date has lapsed.
- Certificate of AnalysisWhere the original retest date and storage-condition claim originate.
- DeviationOpened when a lot is found dispensed past its retest date.
- ICH Q7The parent GMP guideline for APIs where §11.6 retest requirements sit.
V5 Ultimate ships with the Potency retest & expiry dating for raw materials controls already wired in — audit trail, e-signatures, validation evidence. Free trial, no credit card, onboard in days, not months.
