Keep physical stock separate from stock authorised for use

A warehouse dashboard shows 1,000 kg available. Production reserves 700 kg and prepares an order. The quality team has authorised only 600 kg for the intended use; another 300 kg is pending and 100 kg has been rejected. Every kilogram exists, but the availability calculation answers the wrong question.

The operating problem begins when possession, acceptance and availability share one field. A reliable inventory model answers each question separately: where is the material, what activities are authorised, and how much remains eligible after commitments? This article describes a proposed system design around those decisions. The quality procedure determines whether a particular lot can have distinct quantity or container dispositions at all.

Define the activity before naming the status

“Released” needs a clear object and purpose. A quality decision may cover a particular material, container group, specification or intended use. A commercial reservation may cover the same physical stock without authorising production consumption. A warehouse transfer may be permitted while the material remains unavailable for use.

Write a simple activity matrix with quality assurance (QA) and operations. For each existing status, establish whether receipt, sampling, internal movement, reservation, picking, consumption and dispatch are allowed. Mark any conditional activity and the person who resolves that condition. Do not assume that a status name conveys the same meaning in the enterprise resource planning (ERP) system, the laboratory system and a handheld application.

ICH Q7 addresses quarantine and release controls for incoming materials used in API manufacture. Its API scope matters when selecting applicable controls. ICH Q7, section 7.2.

Use that applicable quality framework and the approved local procedure to establish decisions. Then configure software to express them accurately. A user interface cannot compensate for an unresolved policy about which activities a pending material may undergo.

Keep three quantities visible

A useful warehouse view distinguishes physical on-hand quantity, quantity eligible for the requested activity and quantity already committed. The stock shown as available for a new transaction should follow the latter two, rather than physical quantity alone.

In a simple case, available eligible quantity equals eligible on-hand quantity minus active eligible reservations. Real implementations also need to handle picked stock, open transfers, concurrent requests and units of measure without double subtraction.

Treat the table as a responsibility discussion, not a universal organisational chart. In a smaller operation one person may perform several roles, but the recorded decisions should remain distinguishable.

Reconcile the 1,000 kg example

Consider an illustrative receipt containing identifiable containers totalling 1,000 kg. Assume the approved procedure permits the separate dispositions in this example and QA has documented their exact container scope.

An existing reservation consumes 150 kg of the released group. A new request for 700 kg therefore faces only 450 kg of unreserved eligible stock and a 250 kg gap. The total physical quantity remains 1,000 kg because reservation does not itself move material.

The system should explain the shortfall in these terms. “Insufficient stock” leaves the planner guessing; “450 kg eligible and unreserved; 300 kg pending quality decision” identifies both the current limit and the dependency. It should not represent the pending 300 kg as guaranteed future supply.

If the approved procedure requires a single disposition for the entire lot, do not implement the example by inventing partial release. Model the actual decision scope and keep the affected quantity unavailable until that decision permits use.

Preserve container identity when quantities split

A partial movement needs more than a changed total. Record the source container, moved quantity, destination container or location, unit and movement identity. Preserve the relationship to the source lot and relevant disposition.

Avoid automatically copying a favourable status to a new container without checking the permitted operation. Conversely, an internal movement need not erase a valid decision if the approved process preserves its applicability. The rule should be explicit and testable.

For bulk stock or shared vessels, the design can be more complex because physical separation and identity may differ from packaged containers. Resolve that process model with the responsible specialists before adopting a generic pallet-and-bin configuration. A warehouse data model should follow the actual material operation.

Propagate a hold through active work

A hold can arrive after reservation but before picking, or after picking but before consumption. Define the response at each stage. Relevant work may need to stop, enter an assessment queue or be checked for already completed activity according to the approved procedure.

Build an affected-transaction view that links the disposition scope to open reservations, picks, transfers and completed movements. The quality owner determines the necessary assessment; the system helps identify its reach. Do not silently cancel transactions and lose the record of what was planned or performed.

When two applications exchange status, include the authoritative decision reference and a controlled version or ordering mechanism. An older release message must not overwrite a newer hold just because it arrived later. Failed or unacknowledged updates need an owner and an operational response, particularly where picking depends on a local copy.

Make concurrency part of the design

Suppose two planners each see 450 kg available and simultaneously request 300 kg. A screen refresh is not sufficient protection. The reservation operation should verify and commit against a shared authoritative balance so the second transaction sees the remaining 150 kg or receives a clear shortage response.

Likewise, a picker can scan material immediately before a hold becomes effective. Agree where eligibility is checked and which event governs the transition. Record the outcome rather than assuming all systems share a perfectly synchronised clock.

For network interruptions, define the permitted local activity and reconciliation process before enabling offline work. The offline barcode receiving guide develops that problem. Reconnecting a device must not convert an unconfirmed local action into an authorised stock movement without the required checks.

Pilot with evidence that exposes mistakes

Choose a manageable material family and map its real status transitions. Reconcile physical, eligible and committed quantities manually before trusting a dashboard. Include a material that cannot be partially released, so the configuration demonstrates its scope restrictions.

Run scenarios covering a receipt still pending review, a scoped rejection, a hold during picking, two concurrent reservations, a duplicate movement and a delayed status message. For each, specify the expected balance, blocked activity, responsible owner and retained evidence.

Measure unresolved status mismatches and the time taken to identify affected transactions. A high automated release rate is not a useful success measure for this project: the system implements authorised decisions rather than creating them. The computer system validation guide addresses how to establish confidence in the intended behaviour.

Once eligibility is reliable, the FEFO allocation guide explains which eligible stock should be considered first. NextEdge Labs can help map these decision boundaries into the ERP, warehouse and quality interfaces and define a pilot with observable acceptance outcomes.

Summary and next actions

Physical stock, authorised stock and unreserved stock answer different operational questions. Keep them connected through traceable quantities and decisions so planning and execution use the same eligibility rules.

• Map the activities permitted by every current quality and warehouse status.
• Reconcile one receipt into physical, eligible and committed quantities using its actual decision scope.
• Identify how a new hold reaches reservations, picking and relevant completed movements.
• Pilot concurrent requests and delayed messages, checking both balances and decision history.