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 Returns Management
- Features
- Stock movements
Stock movements
Tie each posted quantity change to its reviewed request, item, location and correction trail.
OverviewPosted movement ledger×
SCM with Returns Management · Stock movements
New
Posted movement ledger
Stock movements
| Parent | Item | Location | Lot | Signed quantity | Occurred at | |
|---|---|---|---|---|---|---|
| SR-51454 | SI-2704 | SL-120 | SL-5088 | 210 | 26 Oct | |
| SR-83677 | SI-7056 | SL-140 | SL-2443 | 810 | 08 Oct | |
| SR-13809 | SI-1459 | SL-120 | SL-7614 | 680 | 15 Oct | |
| SR-46260 | SI-4686 | SL-140 | SL-3062 | 430 | 03 Oct | |
| SR-88704 | SI-8426 | SL-110 | SL-3916 | 590 | 11 Oct |
6 of 6 records
SEK-930Stock movements · SM-45426
ParentSR-51454
ItemSI-2704
LocationSL-120
LotSL-5088
Signed quantity210
What you can do
Record the quantity that actually changed
A stock movement holds a signed quantity and a posted flag. It points to the parent request, item and storage location, with a lot reference when relevant. Its line number, revision, time and source effect key help the team distinguish one effect from another. The movement can also retain item code, lot code, base unit, expiry and unit cost in US dollars as recorded evidence.
Inventory Coordinator should treat the movement as the record of an actual quantity effect. The request describes the planned and reviewed work; the movement describes what was posted. Operations Overview uses posted movements to show on-hand quantity and subtracts active reservations to show available quantity. A draft or unposted movement must not be counted as stock already available.
How the work is organized
- Match. Confirm the item, location and optional lot against the approved request.
- Post. Record the signed quantity and source effect key for the completed action.
- Correct. Use the reversal link to connect a correcting movement to the original.
What to agree during setup
Set a rule for the sign of receipts and removals so every operator interprets positive and negative quantity consistently. Decide which physical event permits a movement to be marked posted. Make the source effect key traceable to the guarded operation attempt and check that the parent request revision is still the one reviewed. Agree who may create a reversal and what evidence explains the correction.
Item and location codes need to be stable enough for historical reporting. A lot-tracked item needs the correct lot selected when posting. The lot’s expiry date and release state matter to later eligibility decisions. If a movement is reversed, the original remains visible; the team should not erase the earlier event from the ledger.
Check the handoff on an actual case
Take an Approved request for a returned item at a receiving location. Confirm the expected base unit and the lot where required. Post a positive movement with the parent request and effect key. Open the posted movement ledger and compare the actual quantity with the requested units. Inventory Reviewer then checks that the related operation receipt and movement point to the same action.
Now enter a correction case. A quantity was posted to the wrong location. Record the linked reversing movement, then record the correct location effect through the reviewed path. Auditor should see the original and reversal side by side, with the source request still available for context. The net quantity in Operations Overview should reflect posted entries rather than an edited historical total.
What your team sees
- Posted movement ledger — Posted effects with item, location, lot, signed quantity and reversal link.
- Executed requests — Completed requests from which the movement trail can be opened.
- Operation exceptions — Attempts needing review before another effect is accepted.
Follow the work through
See stock execution and exception reconciliation.
What it keeps track of
Data model- Stock movements
- Posted signed quantity movements against approved stock requests
- Stock requests
- Return and stock movement requests raised against a storage location counterparty
- Stock items
- Returnable and refurbishable items with base unit and lot tracking rules
- Storage locations
- Warehouses, return docks and quarantine areas receiving inspected stock
- Stock lots
- Lot and expiry evidence for lot-tracked returned stock
- Operation receipts
- Idempotent receipts for every guarded operation attempt
Who uses it
Permissions- Inventory Coordinator
- Records the eligible action.
- Inventory Reviewer
- Reconciles it with the approved revision.
- Auditor
- Follows corrections and source effects; App Administrator maintains operating scope.
Set up SCM with Returns Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.