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 Barcode/RFID
- Features
- Items, lots and locations
Items, lots and locations
Keep item identity, lot state and storage address clear before stock work begins.
OverviewLots awaiting release×
SCM with Barcode/RFID · Items, lots and locations
New
Lots awaiting release
Approval conditions
| Lot code | Item | Expires at | Release state | Owner reference | |
|---|---|---|---|---|---|
| LC-912 | SI-9050 | 16 Oct | Pending | OR-785 | |
| LC-434 | SI-4735 | 10 Oct | Pending | OR-646 | |
| LC-196 | SI-4969 | 22 Oct | Pending | OR-941 | |
| LC-983 | SI-2349 | 17 Oct | Pending | OR-295 | |
| LC-680 | SI-8828 | 07 Oct | Pending | OR-295 |
6 of 6 records
LC-912Stock lots · SL-61172
PendingItemSI-9050
Expires at16 Oct
Owner referenceOR-785
What you can do
Establish the stock being handled
Stock items carry a SKU, name, base unit, lot tracking choice and active flag. The organization reference places each item with its operating company or site. Storage locations carry a code, name, address, contact and eligibility note. A request, reservation or movement points to these records so the team can tell which material and physical place a quantity concerns.
A lot gives a tracked batch its code, expiry date, release state and owner reference. Pending, Released, Quarantined and Blocked are distinct states for review. The expiry date matters when a coordinator selects stock for a dated request. The location’s eligibility note gives the team local handling context; it is not a substitute for checking the actual lot.
How the work is organized
- Maintain the catalog. App Administrator keeps organizations, items and storage locations identifiable and active where they should be used.
- Review the lot. Inventory Reviewer examines expiry and release state before a lot is selected for a stock action.
- Select exact context. Inventory Coordinator relates the request or reservation to the intended item, location and lot.
The base unit is important across the entire chain. Requested units, scanned units, reservation quantity and signed movement quantity need a common interpretation for comparison. If labels or handheld devices use packs, the operating team must agree on the conversion before any quantity is posted.
What to agree during setup
Set a consistent SKU convention, location code scheme and lot code policy. Decide whether a lot code is unique within an item or across an organization. Define who can change release state, and how a quarantine or block decision is documented. Confirm whether a storage location represents a bin, room, dock or external site; the address and eligibility note should help a worker find and assess it.
Agree on when inactive items and locations stop being selectable for new work while remaining visible on historical requests. Decide who owns the master list at each organization. A member’s role name and linked user should match the real person making decisions, especially when reviewers work across shifts.
Check the handoff on an actual case
An incoming batch has an expiry date and a lot code, and a request is due next week. The coordinator checks that the item is active, the selected location is suitable and the lot is Released. The reviewer can see the same lot identity on the reservation and eventual movement. If the lot is Quarantined, the team investigates before setting it aside for the request.
Later, an auditor can start from the lot and follow the movement history to see which requests used it. The item, location and lot references are stronger than a free-text description of the material. A movement’s recorded item code, lot code and base unit can add the snapshot used at the time of posting.
What your team sees
- Lots awaiting release — Pending lots with item and expiry details for review.
- Active reservations — Stock claims by item, location and lot.
- Posted stock movements — Recorded quantity effects at the location where they occurred.
Follow the work through
Follow stock preparation before a request and scan to movement when a physical read is recorded.
What it keeps track of
Data model- Organizations
- Represents a company or site using the system, letting teams keep separate operations apart.
- Stock items
- Defines a product or material teams stock and track across locations and lots.
- Stock lots
- Tracks a batch of stock sharing an expiry and origin, letting teams follow it through storage.
- Storage locations
- Represents a physical place where stock is kept, so teams know where items are stored.
- Stock requests
- Represents a request for stock that teams create, approve, and fulfill from start to finish.
- Stock reservations
- Holds inventory set aside for a specific request so staff know what's already spoken for.
- Stock movements
- Logs a change in stock quantity, giving teams a running history of what moved and when.
- Team members
- Represents a person working within an organization, used to assign roles and track activity.
Who uses it
Permissions- App Administrator
- Maintains organization and catalog records.
- Inventory Reviewer
- Examines lot eligibility.
- Inventory Coordinator
- Selects the correct stock context.
- Auditor
- Reads the later trace.
Set up SCM with Barcode/RFID your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.