1. SCM with Multi-warehouse
  2. Features
  3. Stock position
Feature · Stock position

Stock position

Stock items, lots and locations provide the context for reading signed stock movements. The Inventory Coordinator can compare posted quantity for the same item and location with the request that caused it.

OverviewPosted stock movements
SCM with Multi-warehouse · Stock position

Posted stock movements

Stock movements

New
Record numberParentItemLocationLotSigned quantity
SM-87661SR-12760SI-18711SL-12496SL-61047670
SM-86415SR-86474SI-27290SL-35332SL-14653840
SM-61523SR-26238SI-20856SL-19657SL-61907740
SM-99782SR-18445SI-89907SL-99467SL-51446670
SM-74689SR-23616SI-39739SL-94345SL-52106630
6 of 6 records
SR-12760Stock movements · SM-87661
ItemSI-18711
LocationSL-12496
LotSL-61047
Signed quantity670
Occurred at03 Oct
Example screen with sample data

What you can do

Follow the operating record

Stock items carry a SKU, base unit and lot tracking policy. Lots carry their own lot code, expiry and release state. Locations identify the operating sites where stock is held. These records provide the reference context for each movement.

A stock movement records signed quantity against a parent request, item and location. It can also reference a lot and a movement that it reverses. The posted flag distinguishes a posted row from a row still being prepared; reversal history remains linked to the original movement.

The movement row, rather than the request status, carries the signed quantity effect. A compensating row can point back to an earlier posted movement; that link preserves the original history for the Inventory Reviewer and Auditor.

How the work is organized

  • Identify. App Administrator maintains item, lot and location references used in stock work.
  • Post. Inventory Coordinator records the signed effect against the approved parent request, item and location.
  • Correct. Inventory Reviewer checks any compensating row and the original movement it reverses.

What to agree during setup

Agree item codes and base units before importing operational records. Decide who maintains lot release states, and reconcile location codes across organizations. Check how your team investigates a quantity discrepancy while preserving the original posted evidence.

Check the handoff on an actual case

For a lot-tracked item moving from one warehouse to another, the coordinator checks the item and lot before recording the signed effects at the relevant locations. The reviewer can follow the parent request, inspect the posted rows and see whether a correction points back to an earlier movement. This is more useful than looking only at a request marked executed.

Check the movement’s posted flag and signed quantity rather than inferring a stock change from request status. If a correction is needed, add a compensating movement linked to the original and inspect both rows. Use the receipt to investigate an uncertain outcome.

A movement can carry its own occurrence date, item code, lot code and unit cost in addition to references. Use those details to investigate an apparent discrepancy, but compare the linked item and location records first. The Auditor can read a correction in context because both rows remain associated with the request.

What your team sees

  • Posted stock movements — Shows signed effects by parent request, item, location and occurrence date.
  • Lots needing release — Shows pending lots with expiry and owner reference for eligibility checks.

Follow the work through

See the related process and the data model for the connected records.

What it keeps track of

Data model
Stock items
Stock keeping units with their base unit of measure and lot tracking policy.
Stock lots
Lot and expiry evidence for lot-tracked stock items.
Stock movements
Posted signed-quantity ledger rows per item, location, lot and base unit.
Storage locations
Warehouses, yards and staging sites where stock is held.
Stock requests
Requests to receive, move, reserve or transfer stock across the warehouse network.

Who uses it

Permissions
Inventory Coordinator
Prepares the work and follows its outcome.
Inventory Reviewer
Makes the independent decision and checks uncertain results.
App Administrator
Maintains reference data.
Auditor
Reads authorized history.

Set up SCM with Multi-warehouse your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started