Retest dates and expiry dates need different inventory controls

A production order slips by two weeks. Its allocated API reaches the recorded retest date during the delay. A planner changes the date in the enterprise resource planning (ERP) system so the allocation stops showing as overdue, expecting quality control (QC) to complete the work later. The immediate scheduling problem disappears, but the stock record now implies a decision that nobody has made.

The system should instead expose the dependency: the planned use crosses a controlled date and needs the authorised assessment defined by the material's procedure. Whether that assessment permits use, requires more work or results in rejection must remain a quality decision supported by the appropriate evidence.

This guide concerns API and intermediate inventory controls. It does not establish a universal retesting schedule or a method for extending the shelf life of a finished medicine.

Preserve the meaning of each date

In ICH Q7, a retest date identifies when material needs re-examination for suitability, while expiry dating limits the expected period of specification compliance under defined storage. Its dating provisions rely on stability information. ICH Q7, glossary and section 11.6.

An expiry date is not a retest trigger: material should not be used after its expiry date. Those different meanings should survive data entry, document extraction and integration. A single field called “valid until” makes it difficult to tell whether the next action is a retest assessment or control of expired material. Renaming the field on a dashboard does not fix a source system that has already discarded the distinction.

Capture the original date value, its type, source document and applicable material or batch scope. When the source is unclear or conflicting, create a data-resolution task. Do not infer the date type from whichever field is easiest to populate in ERP.

The approved material procedure should determine the operational effect of reaching the date and the authorised route for reassessment. Avoid configuring an automatic extension simply because a laboratory test result is recorded as passing.

Build the material rule before the reminder

Start by selecting a representative material and establishing how its dates are currently managed. Which document supplies the initial date? Which record governs a later quality decision? Which role can approve the resulting activity? Does the rule apply to an entire batch or a specifically justified container scope?

Separate the event that triggers review from the decision that completes it. A reminder might be generated before the date to allow planning. A laboratory request might then be created and accepted. Neither event changes the authorised use of the material by itself.

Agree the treatment of time zones and date-only values if sites operate across regions. A midnight software default should not silently decide an operational boundary that the procedure has not defined.

Follow a delayed production order

Consider an illustrative API allocation of 120 kg to an order originally scheduled for 8 November. The material's recorded retest date is 10 November. The order moves to 22 November because an equipment issue delays the campaign.

The planning system detects that the proposed use now crosses the retest boundary. It creates an exception linked to the material, allocation and revised use date. The stock remains visible, but the proposed use follows the required hold or assessment path rather than being treated as assured supply.

QC reviews the material history and the work required under the approved procedure. A laboratory request, where required, is linked to the assessment. The planner can see that work is pending and can compare rescheduling or another eligible supply option without changing quality records.

When the authorised reviewer records a decision, the system applies only the approved scope and conditions. It preserves the earlier date and the basis for the new state. The example intentionally supplies no universal replacement date: the supporting evidence and applicable procedure determine the actual outcome.

If the work does not support the intended use, the exception remains actionable for planning. A completed laboratory task must not become a favourable decision merely because the scheduling team needs the material.

Keep testing, review and disposition separate

An instrument result, a reviewed laboratory report and a material-use decision are different records. The workflow should show their relationship without treating them as interchangeable.

A test can be analytically complete while its review is still open. A reviewed result may raise a question about storage history or the representativeness of the sample. A quality assessment may require additional information before deciding whether the proposed use is supported.

Design the integration around these stages. If the laboratory system sends “completed,” establish precisely what that event means. An ERP rule should not interpret every completion message as permission to issue stock. Include the responsible quality decision and its scope in any status change that affects use.

For supporting laboratory planning, see the stability study workflow. Stability-study records and routine inventory reassessment can be related, but one should not be silently substituted for the other.

Handle split containers and conflicting evidence

A material batch may have been divided among containers or storage locations. Keep those relationships visible when a review is initiated. Different handling histories may matter to the assessment; the software should provide the evidence rather than assume that one favourable result automatically covers every remaining container.

Similarly, a supplier document and an internal record may disagree about the date or its type. Record both observations and route the discrepancy to the appropriate owner. Avoid the tempting rule “take the latest date” because it produces a favourable answer without establishing why that answer is valid.

Correcting a transcription error is also different from making a new quality decision. Preserve the correction reason and supporting document so a reviewer can distinguish an administrative repair from a change to the material's authorised state.

The inventory-status guide explains how those scoped decisions affect warehouse activity. The date workflow should use the same authoritative status model rather than maintaining a separate unofficial list of usable materials.

Give planning visibility without promising an outcome

Planning needs an expected assessment timeline, an owner and a clear statement of what is unresolved. It does not need a hidden assumption that all reassessments will succeed.

Show pending quantity separately from eligible supply. If an expected laboratory completion date changes, update the planning exception while preserving the earlier assumption. Allow the planner to evaluate alternative supply or revised production dates using the current uncertainty.

For frequent reassessment work, forecast the queue from the stock portfolio and planned uses. Distinguish a material likely to be consumed before the boundary from one with no confirmed demand. The stability and sample inventory guide addresses a related record population that should remain distinguishable from production stock.

Test the transitions that can fail silently

Use representative examples with a use date just before and just after the controlled boundary. Include a postponed order, an overdue assessment, a conflicting supplier document and a result message arriving before its review decision.

Verify that the system retains the original date, identifies the affected allocations and prevents an unauthorised user from changing the date to bypass the workflow. Test a corrected record separately from an authorised reassessment outcome. Confirm that an older message cannot restore a superseded state.

Measure missing date types, unresolved discrepancies and planning exceptions without assigned owners. Review whether reminders arrive early enough for the actual operating process; avoid choosing a universal reminder interval with no relationship to laboratory capacity or material use.

NextEdge Labs can help model the records and interfaces so reminders, laboratory work and quality decisions remain connected. The useful starting point is one complete material history, including a case where the expected use was delayed.

Summary and next actions

Retest and expiry dates carry different meanings. Preserve that distinction and let the authorised assessment determine the next permitted activity instead of letting a date edit resolve a scheduling problem.

• Inspect material records for missing or ambiguous date types and source documents.
• Map the review trigger, required evidence and authorised decision for one representative API.
• Reconstruct a delayed production order and check how its allocation responded to the date boundary.
• Test conflicting documents and out-of-order laboratory messages before automating status changes.