Allocate scarce released stock with an explainable policy

Scarcity needs a decision rule

An order-management team has 800 eligible units against 1,000 committed units. The earliest order gets supplied first, until a senior salesperson asks for a different customer to be prioritised. Another team has already reserved some of the same stock. The warehouse receives changing pick instructions while nobody can explain the final distribution consistently.

Pharma shortage allocation should turn that conflict into a controlled decision. First determine which stock can serve which orders. Then apply a documented, authorised commercial policy to the remaining eligible demand. Preserve the reason for each allocation and the demand that remains unfulfilled.

This is an operating and commercial workflow. It does not decide which individual patient should receive treatment, and a software priority score should not imply clinical authority. Where a product or supply situation is subject to specific legal, contractual or authorised public-health directions, responsible specialists must establish how those directions constrain the policy.

Determine eligibility before priority

A stock quantity can be physically present yet unavailable for a particular order. Check authorised status, product identity, market and pack suitability, remaining shelf-life requirements, existing reservations and any relevant distribution restrictions. Do not pool quantities merely because their product descriptions look similar.

Order eligibility also needs definition. Confirm the customer, delivery location, required date, permitted product and commercial status. Remove cancelled or duplicate demand from the allocation run through controlled reconciliation, while preserving the transaction history. An unverified order should not acquire priority by entering the queue repeatedly.

WHO's distribution guidance addresses controls over medical-product storage and distribution. It supports the importance of controlled stock handling, but does not prescribe the customer-ranking method proposed here. WHO good storage and distribution practices.

Keep the stock-selection rule separate from customer priority. First-expiry-first-out allocation helps select suitable lots within eligibility rules. It does not, by itself, decide how a shortage should be divided among customers.

Write a policy that can survive an exception

Define the order groups, priority basis, allocation method within each group and tie-breaker. The policy may protect documented commitments, distribute proportionally within a defined group or use another approved approach. The right rule depends on the actual obligations and business context; there is no universal sequence suitable for every pharmaceutical product.

Record who approved the policy and when it takes effect. If an exception is allowed, identify the decision authority, required reason and the evidence that must be retained. A broad “manager override” button is too vague when several managers represent competing interests.

The policy should explain partial fulfilment and rounding. A customer may accept split deliveries, require complete packs or have a minimum shipment quantity. These conditions can leave a small residual quantity after a proportional calculation. Decide how that residual is assigned without creating an undocumented preference.

Worked example of 800 units against 1,000 units

Consider an illustrative allocation with 800 released, eligible units and no previous reservations. Customer A has a protected commitment of 400 units under the assumed approved policy. Customers B and C each have 300 eligible units of demand in the same remaining priority group. Assume all units are interchangeable for these orders and single-unit allocation is permitted.

The policy first assigns 400 units to A. The remaining 400 units are divided proportionally between B and C, whose combined demand is 600. Each receives 400 × 300 ÷ 600 = 200 units. Total allocation is 400 + 200 + 200 = 800; unmet demand is 100 units each for B and C.

This example illustrates the arithmetic of one assumed policy, not a recommended preference for Customer A. The protected commitment must have a valid basis. Without that basis, the system should not invent the priority from customer size, salesperson influence or historical revenue.

Now suppose 100 of the original 800 units become restricted before picking. The eligible pool is 700, so the allocation needs reassessment. Under the same simplified policy, A receives 400 and B and C receive 150 each. The application should preserve the earlier allocation and show why it changed, then obtain any required approval before replacing pick instructions.

Preserve the difference between allocation and shipment

An allocation is a reservation decision, not proof that the customer received product. Track subsequent picking, dispatch and delivery separately. If a pick fails because a pack is damaged or the stock count differs, the unmet quantity should return to the shortage workflow with the relevant reason.

Likewise, a partial shipment should not close the remaining order accidentally. Keep the open quantity and its revised promise visible to customer service. If the customer cancels the remainder, record that as a distinct action rather than treating the original demand as fully supplied.

Customer communication needs a controlled handoff. The workflow can prepare the affected quantity, revised date and approved explanation, but the responsible team should use its authorised communication process. Avoid automatic promises based on a tentative future production date or an unreviewed allocation scenario.

Reconcile competing reservations

The allocation run needs a consistent view of stock already committed through other channels. If a distributor order, institutional order and transfer request reserve the same quantity independently, each local screen can appear correct while the total exceeds supply.

Use a defined reservation authority and transaction mechanism that prevents double commitment. When an allocation is accepted, record the relevant version of stock and demand. If either changes before the reservation is saved, require recalculation or a controlled conflict response rather than accepting an obsolete result.

Test retries carefully. A repeated request after a connection timeout must not reserve the quantity twice. Preserve a unique operation identifier and reconcile the result with the reservation system. Technical reliability is part of the commercial promise because duplicate reservations directly affect what other customers can receive.

Explain the shortage without distorting the forecast

Keep actual shipments, open demand and estimated lost demand separate. A customer receiving only 200 of 300 requested units should not automatically appear to have demanded just 200 in the next forecasting cycle. Equally, repeated speculative orders should not inflate underlying demand indefinitely.

The demand-forecasting guide explains how constrained sales and channel stock affect interpretation. Bring recurring shortages into sales and operations planning, where capacity, inventory and customer commitments can be reconsidered together.

Analyse allocation outcomes by policy group and reason. Look for recurring manual exceptions, customers repeatedly left with residual shortages and a high volume of orders created just before a cut-off. These patterns deserve review; they do not by themselves prove misconduct or justify changing the rule without approval.

Pilot the policy with difficult cases

Replay a real shortage using the historical stock and orders available at the time. Ask two authorised reviewers to explain the result independently from the saved policy and inputs. If they reach different answers, clarify the rule before automating it.

Include complete-pack rounding, a customer that declines partial delivery, a quality hold after allocation and a cancelled order. Test two users allocating simultaneously and a retry after a timeout. Verify that every accepted result conserves quantity and retains the unmet demand.

NextEdge Labs can build the allocation and exception workflow around the existing order and inventory systems. A sound first milestone is an allocation result that can be reproduced, approved and traced through dispatch without losing the reason for the decision.

Summary and next actions

An explainable shortage process starts with eligible stock and demand, applies an authorised policy and preserves the unfulfilled balance. Clear ownership and reliable reservations matter as much as the allocation formula.

• Identify the stock restrictions and order conditions that determine eligibility for one constrained product.
• Approve the priority groups, allocation method, rounding rule and exception authority.
• Replay a shortage and verify that allocations plus remaining stock reconcile to eligible supply.
• Test status changes and concurrent reservations, then establish the handoff for revised customer commitments.