The shop ordered 48 booster boxes. The distributor confirmed the order, but only 36 arrive. Twenty customers have confirmed preorders, eight boxes are reserved for two release events, another location expects four, and the owner planned to put sixteen on the shelf.
The problem is not simply "we are short 12." The shop has 48 promises competing for 36 physical boxes.
Keep six quantities separate
A release record should not use one quantity field for every stage.
| Quantity | Example |
|---|---|
| Ordered | 48 |
| Vendor confirmed | 48 |
| Shipped | 48 |
| Physically received sellable | 36 |
| Damaged or wrong | 0 |
| Still backordered or disputed | 12 |
Until receiving is complete, do not treat confirmed or shipped quantity as available stock.
List commitments before allocating the shortage
Build the commitment list from actual records:
| Commitment | Quantity | Evidence |
|---|---|---|
| Confirmed customer preorders | 20 | Customer and quantity list |
| Release events | 8 | Four boxes per event |
| Transfer to North location | 4 | Approved transfer request |
| Planned walk-in shelf stock | 16 | Internal plan, no customer promise |
| Total | 48 |
In this example, shelf stock is a plan rather than a customer commitment. That distinction helps the owner decide where the shortage can be absorbed.
Use a written allocation decision
The shop's policy may prioritize paid preorders, confirmed pickups, events, locations, or another category. The important part is to make the choice consistent and visible.
Example allocation of 36 received boxes:
- 20 to confirmed preorders;
- 8 to the two events;
- 4 to the approved location transfer;
- 4 to walk-in shelf stock;
- 0 of the remaining planned 12 shelf boxes until the shortage is resolved.
Record the manager who made the decision, the time, and the affected records. Do not let each shift create a different rule at the counter.
Separate event product from sellable shelf stock
If eight boxes support scheduled events, physically stage and label them for those events. A shelf count of 12 does not mean 12 are available if eight are already committed.
For each event, confirm:
- event name and start time;
- registration capacity;
- required product or kit count;
- prize support or other reserved product;
- employee owner;
- physical staging location;
- unused-product disposition after the event.
Do not depend on the event organizer remembering which case is reserved.
Contact affected customers with specific facts
If customer commitments cannot all be met, use a list tied to the allocation decision.
A useful communication record contains:
- customer;
- promised product and quantity;
- what is available now;
- options offered under shop policy;
- employee who contacted them;
- channel and time;
- customer response;
- remaining follow-up.
"Posted on Facebook" is not proof that a customer with a confirmed preorder received the update.
Receive by exception
Suppose the 36 boxes include one crushed box and one incorrect SKU. Receiving should show:
- 34 sellable received;
- 1 damaged and held for vendor claim;
- 1 wrong product and held for return;
- 12 not received;
- photos or vendor case reference when the shop uses them.
That changes the allocation again. Make the sellable count authoritative before customers arrive.
Build a release timeline
Seven days before
- confirm vendor quantity and expected arrival;
- audit preorder names, quantities, and payment status;
- confirm event schedule and capacity;
- assign receiving and customer-contact owners.
On delivery
- count by SKU before shelving;
- separate damage, wrong items, and shortages;
- update received quantity;
- apply the allocation rule;
- stage preorder, event, transfer, and walk-in stock separately.
Day before release
- verify every staged quantity physically;
- contact affected customers;
- confirm staffing and event setup;
- review pickup rules with the opening shift.
After release
- reconcile pickups and unclaimed commitments;
- receive late or replacement product;
- close vendor issues;
- return unused event allocations according to shop policy;
- record what should change next time.
Use this short-allocation worksheet
- Product and release date:
- Ordered / confirmed / shipped:
- Sellable received:
- Damaged / wrong / missing:
- Confirmed preorder commitment:
- Event commitment:
- Location-transfer commitment:
- Walk-in plan:
- Allocation priority:
- Manager decision and time:
- Customers requiring contact:
- Physical staging locations:
- Vendor case and next follow-up:
A release-day plan becomes useful when the truck does not match the purchase order. The record should tell the team which 36 boxes exist, who they are for, and what happened to the missing 12.