These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Inventory Allocation Engine
- Features
- Reservation control
Reservation control
Hold eligible lot quantity for reviewed demand and release claims when authorized scope changes.
OverviewHeld Reservations×
Inventory Allocation Engine · Reservation control
New
Held Reservations
Stock reservations
| Reservation number | Request | Lot | Quantity | Expires at | Revision | |
|---|---|---|---|---|---|---|
| SR-56500 | SR-46742 | SL-9816 | 100 | 12 Oct | 300 | |
| SR-58478 | SR-44784 | SL-1751 | 750 | 10 Oct | 180 | |
| SR-64307 | SR-33634 | SL-7807 | 710 | 19 Oct | 320 | |
| SR-20366 | SR-25393 | SL-5681 | 310 | 12 Oct | 850 | |
| SR-13508 | SR-78727 | SL-6466 | 780 | 18 Oct | 170 |
6 of 6 records
SR-46742Stock reservations · SR-56500
HeldLotSL-9816
Quantity100
Expires at12 Oct
Revision300
What you can do
Keep a claim attached to its demand
Held Reservations connects each active reservation number to a request and lot. Quantity is the amount held. Open the reservation to follow its later Released, Consumed or Expired state. Expiry date and revision help the team inspect the claim’s current context. Inventory Clerk runs the reservation action while Inventory Supervisor resolves changes to the authorized demand.
The reservation workflow refuses a reservation larger than free eligible inventory. It subtracts active Held quantities from the selected lot’s quantity on hand and records an operation result. A successful claim writes a Recorded receipt; a rejected claim writes a Failed receipt with the shortfall. The stable request-and-lot key makes repeated input return its earlier result instead of creating another claim.
How the work is organized
Inspect the reviewed request and lot before creating the hold. The reservation is an operational commitment, so the clerk must be able to explain the request, lot and quantity together. A reservation record is not a posted physical stock movement. During the pilot, compare the approved receive-or-move action with its movement and receipt before explaining the resulting stock balance.
- Bounded quantity. Existing Held claims reduce the free quantity for competing requests, even when those requests belong to the same item and location.
- Failure follow-up. A Failed receipt explains the refused operation; the supervisor resolves its cause before retrying with the appropriate operation identity.
- Scope release. Authorized correction or cancellation releases held reservations through the workflow so available stock is restored with a traceable cause.
What to agree during setup
Agree how requested units map to reservation quantity and how the team identifies the eligible lot. Test a request with sufficient stock, a shortfall and a repeated successful command. Inspect the held quantity and operation result after each attempt. The clerk should be able to show that repeating an accepted request leaves the original claim unchanged.
Agree who follows up when a reservation reaches its expiry date. Use Reservation Expiry Review to identify the case and inspect its actual state before taking the next action. Inventory Supervisor also settles how safety-stock guidance affects authorized quantity. The clerk should be able to explain the amount held and the amount the supervisor intended to leave free.
Check the handoff on an actual case
A lot holds 100 units. A request already holds 35, leaving 65 free. Inventory Clerk attempts a second reservation for 70 and receives a failed operation result. The supervisor reviews the shortfall and corrects the second request’s authorized quantity. Before another attempt, inspect the earlier operation result and agree the next permitted action; keep the failed receipt available to Auditor.
Next, cancel the first request through the authorized correction workflow. Its Held claim becomes Released and the free quantity increases by the released amount. Confirm that canceling the request does not erase its earlier decisions or posted movement evidence. If a physical effect already occurred, inspect the compensating movement path separately. Finally, replay the earlier successful reservation with its stable key and confirm that the released history is not replaced by an unexplained new hold.
What your team sees
- Held Reservations — Active claims with the request, lot, quantity and expiry date together.
- Stock Requests Register — The clerk’s draft demand to prepare before supervisor review.
- Failed Operation Receipts — Refused reservations and other operations needing supervisor follow-up.
Follow the work through
Rehearse reservation, then correction and reversal. Use permissions to separate workflow execution from table visibility.
What it keeps track of
Data model- Stock reservations
- Held, released or consumed reservations against eligible stock lots.
- Stock lots
- Lot or serial level inventory held at a storage location.
- Stock requests
- Requests to receive, move, reserve or issue stock.
- Operation receipts
- Recorded, verified, failed or corrected operation evidence.
Who uses it
Permissions- Inventory Clerk
- , Inventory Supervisor, Auditor.
- Inventory Clerk
- Runs supported stock actions.
- Inventory Supervisor
- Owns correction and cancellation; Auditor checks the claim and receipt history.
Set up Inventory Allocation Engine your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.