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.
- SCM with Cycle Counting
- Features
- Stock position
Stock position
Read posted movements by item, lot and location and retain the lineage of corrections.
OverviewPosted Movements×
SCM with Cycle Counting · Stock position
New
Posted Movements
Stock movements
| Parent | Item | Location | Lot | Signed quantity | Occurred at | |
|---|---|---|---|---|---|---|
| SR-74741 | SI-4435 | SL-150 | SL-5657 | 590 | 07 Oct | |
| SR-31032 | SI-6200 | SL-140 | SL-4472 | 130 | 20 Oct | |
| SR-44591 | SI-3956 | SL-110 | SL-7570 | 410 | 18 Oct | |
| SR-87188 | SI-4645 | SL-120 | SL-4896 | 250 | 24 Oct | |
| SR-20295 | SI-9347 | SL-110 | SL-1935 | 270 | 12 Oct |
6 of 6 records
SEK-635Stock movements · SM-45274
ParentSR-74741
ItemSI-4435
LocationSL-150
LotSL-5657
Signed quantity590
What you can do
Read the ledger before acting
Posted stock movements are the source of on-hand quantity. Each movement connects a stock request to an item and location, with a signed quantity for the effect. A lot can be linked where the item is lot tracked. The movement’s occurrence time and source effect key help the team distinguish separate operations and check whether an action was already recorded.
Operations Overview shows on-hand and available stock from posted movements, plus pending review decisions and failed operations. When a location appears short, Program Manager can trace the position to its posted movements and the parent requests. Warehouse Operator should look at both the item and location before an issue or receipt. For a lot-tracked item, the lot’s release state and expiry date matter as well.
How the work is organized
- Ledger effect. Keep signed quantities in posted movements tied to their source request.
- Exact position. Inspect item, location and lot together when a lot applies.
- Correction lineage. Use the reversal reference to connect a compensating movement to the original.
A reservation changes available quantity without changing on hand. This distinction matters during a count: a physical observation is compared with the ledger’s on-hand position, while an issue decision also considers active claims. The team should not explain a physical shortage by subtracting reservations from the count.
What to agree during setup
Agree how the team identifies a posted effect and records its source effect key. Decide when a movement needs a lot reference and how the location is selected. For lot-tracked items, check expiry and release state before treating stock as eligible. Set a correction policy that preserves the original movement and records a separate compensating effect. The reviewer should be able to see the original and reversal side by side.
Agree who checks a movement after an approved count variance. The signed quantity should explain the change from the prior on-hand position to the reviewed result. If the operation receipt says the action completed, its effect references should identify the movement being counted. A mismatch belongs in the review queue.
Check the handoff on an actual case
Start with an approved count that differs from the movement-derived balance for one item and location. Ask Warehouse Operator to record the signed adjustment under the same stock request. Verify that the movement is posted and that its lot reference is present when required. Then simulate a correction: retain the first movement and create a compensating movement whose reversal reference points back to it. Check that Operations Overview reflects the posted effects and that the review evidence still explains both steps.
What your team sees
- Posted Movements — Posted ledger effects with item, location, quantity and reversal lineage.
- Released Lots — Lot records that can be considered during stock selection.
- Receipts Needing Review — Operations whose recorded effects need another check.
Follow the work through
See stock execution and reconciliation.
What it keeps track of
Data model- Stock movements
- Posted signed stock movements; the only source of on-hand balances.
- Stock requests
- Operational stock request that parents counts, movements and reviews.
- Stock items
- Stock keeping units with base unit and lot tracking policy.
- Stock lots
- Lot and expiry evidence for lot-tracked items.
- Storage locations
- Warehouses, zones and storage locations where stock is held.
- Operation receipts
- Idempotent execution receipts for each guarded operation.
Who uses it
Permissions- Warehouse Operator
- Records physical stock effects.
- Inventory Reviewer
- Checks the approved source and any correction.
- Program Manager
- Follows the on-hand position and exceptions.
Set up SCM with Cycle Counting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.