Reservation connects a specific kitchen request to an eligible lot. Its purpose is to prevent the team from promising stock already held for another task. Keep the reservation result separate from the physical lot balance and the later signed execution effect, so the team can explain both commitment and use.
Inventory Clerk identifies the stock request and intended lot. Check item, storage location, on-hand quantity and lot status before asking the workflow to create a hold. An Available label does not replace eligibility checks.
The reservation action evaluates lot quantity on hand minus active Held stock reservations. Inventory Clerk inspects the result. A larger requested hold is refused with a Failed operation receipt result explaining the shortfall; the rejection must not leave an extra reservation.
A successful action records the reservation's reserved units, lot and request with status Held, plus a Recorded receipt. Inventory Clerk preserves the request-and-lot operation identity; its replay must not create a second hold.
Inventory Clerk follows the permitted stock action for approved demand. Compare its posted signed quantity with the lot balance, then inspect the remaining held quantity. Use the movement and its operation result to explain the inventory change; a reservation label alone cannot establish a deduction.
Inventory Supervisor corrects authorized request quantity or cancels the request through the published action. Held reservations become Released so free inventory is restored. Reconcile already posted stock separately; releasing a hold does not reverse a movement.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.