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
- Stock execution
Stock execution
Post the authorized signed stock effect once and preserve the original when correcting it.
OverviewPosted Movements×
Inventory Allocation Engine · Stock execution
New
Posted Movements
Stock movements
| Record number | Parent | Item | Location | Lot | Quantity | |
|---|---|---|---|---|---|---|
| SM-70568 | SR-82827 | SI-1682 | SL-110 | SL-2107 | 280 | |
| SM-19977 | SR-43234 | SI-5201 | SL-110 | SL-3811 | 710 | |
| SM-48289 | SR-75769 | SI-2374 | SL-130 | SL-2715 | 220 | |
| SM-43484 | SR-80186 | SI-2647 | SL-140 | SL-7091 | 480 | |
| SM-78410 | SR-57105 | SI-3652 | SL-110 | SL-5912 | 160 |
6 of 6 records
SEK-291Stock movements · SM-70568
YesParentSR-82827
ItemSI-1682
LocationSL-110
LotSL-2107
Quantity280
What you can do
Connect the request to the stock effect
Posted Movements shows each posted effect with its source request, item, location, lot and signed quantity. The request reference explains which demand authorized the work. The movement date identifies when it happened, while the stable source effect key prevents duplicate execution. Check the posting state and operation result before using the movement in reconciliation.
The receive-or-move workflow executes an approved request, posts its signed movement and adds that effect to the lot balance. It marks the source request Executed and writes a Recorded operation receipt. Rehearse the action with the physical case the team will run, then ask the clerk to explain the beginning balance and the recorded effect.
How the work is organized
Inventory Clerk prepares the approved request and runs the stock action. Inventory Supervisor owns reversal and reconciliation when the original result needs attention. Each stock movement preserves both quantity and signed quantity, so establish their meaning in the pilot rather than summing unsigned amounts as though they necessarily describe net stock change.
- Effect identity. Source effect key derives from the request identity and lets an execution retry find the existing effect.
- Source trace. Source request connects the movement to authorized quantity; item, location and lot identify the stock it affected.
- Compensation trace. The original movement reference links a compensating movement to its original while the original posted evidence stays immutable.
What to agree during setup
Choose a receiving case and a movement case with known beginning balances. Verify which input supplies the signed quantity and which lot receives the effect. Check unit consistency against the item’s base unit. A location name is not sufficient evidence that the correct lot reference was used, particularly when similar goods sit in different storage locations.
Agree how the team records the reason and how a wrong effect is brought to Inventory Supervisor. Reversal is a stock operation with its own result. Directly editing quantity on hand, deleting a posted movement or changing its original quantity would bypass the documented history. Confirm that Inventory Clerk cannot run a reversal and that Inventory Supervisor can perform the authorized correction.
Check the handoff on an actual case
A lot begins at 80 units. An approved receive request posts a positive signed effect of 20 and the lot becomes 100. The operator loses the browser response and runs the same request again. Source effect key should return the existing result, leaving the lot at 100 and the original source request Executed.
The supervisor then discovers that the receive case was recorded against the wrong authorized scope. Run the supported reversal against the original movement and inspect the compensating record and corrected balance. Repeat that reversal. The existing compensation must be returned without another stock change. Retain the original effect, its compensation and their operation evidence so Auditor can explain both the first result and the correction.
What your team sees
- Posted Movements — Posted signed effects with request, lot and reversal references.
- Available Lots — Balances for stock still marked Available after execution.
- Operation Receipts Register — Operation evidence used to distinguish success, failure and verification.
Follow the work through
Use posting and verification for execution and correction and reversal for exceptions. Agree any external ledger handoff in integrations.
What it keeps track of
Data model- Stock movements
- Posted signed-quantity movements that change on-hand inventory.
- Stock requests
- Requests to receive, move, reserve or issue stock.
- Stock lots
- Lot or serial level inventory held at a storage location.
- Operation receipts
- Recorded, verified, failed or corrected operation evidence.
- Stock items
- Stock keeping units with base unit, tracking mode and reorder settings.
- Storage locations
- Warehouses, bins, yards and cold rooms where stock is held.
Who uses it
Permissions- Inventory Clerk
- , Inventory Supervisor, Auditor.
- Inventory Clerk
- Executes supported approved stock work.
- Inventory Supervisor
- Reverses and reconciles; Auditor traces the unchanged original and its compensation.
Set up Inventory Allocation Engine your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.