Coordinate vaccine inventory with session and delivery demand

One depot requests emergency replenishment while another holds more stock than its near-term requirements. The network total looks adequate, yet the available stock may have the wrong presentation, insufficient remaining life or no feasible route to the receiving depot before it is needed.

Vaccine inventory coordination requires more than pooling quantities. The planner needs a product-specific view of eligible supply, demand timing and the practical conditions for moving stock. The relevant programme and clinical authorities determine vaccination policy and clinical use; this article concerns the logistics records that support approved demand.

WHO's distribution guidance relates storage conditions to product information. WHO TRS 1025 Annex 7, section 12.34. Actual handling and use requirements must come from the applicable product and programme instructions.

Define the unit before adding the balances

Specify the product and presentation represented by the inventory unit. A carton, pack, vial and dose are different measures, and conversions can depend on the presentation. Use controlled mappings and preserve the original units in transaction records.

Do not combine different presentations into one apparently interchangeable balance without an authorised basis. A network view can show them side by side while keeping their eligibility and demand relationships distinct.

Record the location, lot, relevant dates and current quality status. Separate physical on hand from stock eligible for the proposed distribution activity and from quantity already committed. Incoming stock should carry its expected timing and unresolved conditions.

The goal is a view that a planner can reconcile with the underlying transactions. If a total cannot be explained by product, unit and status, it is too ambiguous to support a transfer decision.

Separate approved demand from planning uncertainty

Capture the source, date and scope of each demand input. A confirmed delivery request differs from an estimate for a future session or a historical consumption pattern. Keep those categories visible rather than combining them into one number labelled “required.”

Where a programme uses specific planning rules, implement the approved rule and retain its version. Do not invent clinical eligibility, dose schedules or wastage assumptions in the inventory application. The responsible programme owner supplies the basis for those decisions.

Show uncertainty in the planning view. A range or clearly labelled scenario can be more useful than a precise forecast whose assumptions are hidden. The pharma demand forecasting guide develops this distinction for broader supply planning.

Agree how late updates affect commitments already made. A changed requirement should identify affected transfers and delivery plans without silently rewriting the history of the earlier decision.

Work through a two-depot transfer

Consider an illustrative example using one defined logistics unit of the same product and presentation. Depot A has 400 eligible, uncommitted units and planned demand of 150. Depot B has 100 eligible, uncommitted units and planned demand of 250 for the relevant period.

The network holds 500 units against 400 units of demand. B's local gap is 150 units. A transfer of 150 from A to B would leave A with 250 and B with 250, before their planned distributions.

The arithmetic identifies an option, not an approved transfer. The planner must establish whether the selected stock meets the relevant product, remaining-life and handling requirements and can arrive in time through an appropriate arrangement.

If the route or receiving capacity cannot support the movement, the network surplus does not solve B's immediate shortage. The decision record should show the failed condition and the owner of the next action rather than treating the transfer as available merely because the calculation balances.

Check feasibility before confirming the movement

Assess the selected lots against the actual delivery date and applicable remaining-life requirements. The FEFO allocation guide explains why eligibility comes before rotation order.

Confirm the dispatch and receiving arrangements, relevant storage capacity and transport scope. A receiving depot may have nominal space but lack capacity under the conditions required for the specific product. Keep these operational assumptions connected to the transfer.

The lane qualification guide covers the transport arrangement. A previously used route is not automatically suitable for a different packaging configuration or changed handover.

Record the approved transfer as a linked commitment. Until receipt and the applicable checks are complete, distinguish it from eligible stock physically available at B. Avoid counting it as uncommitted supply at A after it has been allocated to the transfer.

Replan when demand or conditions change

A session or delivery requirement can move after the transfer is planned. A quality hold can affect the allocated lot. A route delay can change the feasible receipt date. Each event should identify the commitments that depend on the changed assumption.

Give the planning owner a clear view of alternatives and consequences. Cancelling a transfer before dispatch is different from redirecting goods already in transit. The latter needs the relevant authorised operational assessment and cannot be treated as a simple spreadsheet reassignment.

Preserve the earlier plan and reason for change. This helps distinguish a forecasting problem from a transport delay or an inventory-status issue when reviewing performance.

Where a shortage remains, escalate through the approved programme and business process. Logistics software can show eligible quantities and feasible dates; it should not make undocumented clinical prioritisation decisions.

Review expiry exposure at the network level

Show stock approaching its relevant date alongside eligible demand and transfer feasibility. A surplus at one depot may be useful elsewhere, but only if the destination can receive and use the stock under the applicable requirements.

Avoid moving stock simply to improve one depot's expiry report. A transfer that pushes an unresolved problem to another location does not reduce network exposure. Evaluate the expected outcome after receipt and planned distribution.

Keep reasons for unallocated stock visible: no suitable demand, insufficient remaining life for a particular order, a quality restriction or an infeasible route. Each reason points to a different responsible decision.

Use the same unit and cutoff convention across the network report. Changes in presentation or pack conversion can otherwise make exposure appear to improve without any physical or operating change.

Pilot with a realistic planning week

Choose two depots and a defined product scope. Reconcile opening eligible stock, commitments and planned demand manually. Then replay a week containing a changed request, a delayed transfer and an affected lot.

Verify that the proposed transfer is counted once, that the receiving depot sees its conditional status and that updated requirements reach the responsible planner. Check that a quality hold cannot be overridden by a demand update.

Measure feasible transfers completed as planned, late demand changes, unexplained stock differences and expiry exposure using explicit definitions. Do not attribute changes in vaccination outcomes to the inventory workflow without appropriate evidence; this pilot evaluates logistics performance.

NextEdge Labs can help connect depot records and planning events into a shared decision view. The first useful deliverable is a transfer calculation that remains explainable when a key assumption changes.

Summary and next actions

Network stock can resolve a local gap only when the product, timing and handling conditions make the transfer feasible. Keep demand uncertainty and conditional supply visible throughout the decision.

• Standardise product, presentation and inventory units across the selected depots.
• Separate confirmed requirements from estimates and preserve their sources.
• Test a transfer option against remaining life, route and receiving capacity before committing it.
• Replay a changed-demand or delayed-transfer case and verify that the network balances remain coherent.