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 Lot Tracking
- Features
- Stock catalog
Stock catalog
Keep item identity, lot expiry and release state together before stock work begins.
OverviewReleased lots×
SCM with Lot Tracking · Stock catalog
New
Released lots
Stock lots
| Lot code | Item | Expires at | Release state | Owner reference | |
|---|---|---|---|---|---|
| LC-920 | SI-3891 | 19 Oct | Released | OR-689 | |
| LC-426 | SI-8880 | 12 Oct | Released | OR-716 | |
| LC-706 | SI-5096 | 10 Oct | Released | OR-564 | |
| LC-354 | SI-3801 | 12 Oct | Released | OR-898 | |
| LC-154 | SI-7844 | 05 Oct | Released | OR-545 |
6 of 6 records
LC-920Stock lots · SL-11736
ReleasedItemSI-3891
Expires at19 Oct
Owner referenceOR-689
What you can do
Identify the stock before it moves
A lot only means something when it belongs to the correct item. App Administrator sets up each stock item with its SKU, name, base unit, organization and lot tracking choice. Inventory Coordinator then uses that item identity on a stock request. Stock Lots carry the lot code, expiry, release state and owner reference. Keeping these details close helps a reviewer distinguish a usable lot from one that needs attention before a request is approved.
Start with one item that has both released and restricted lots. Walk through the choice a coordinator would make for a receive or move request. The request identifies the item and location; the movement can retain the lot alongside the item. A lot code typed into a request is useful context, while the referenced lot record is the stable place to check expiry and release state. A short code should never be treated as a substitute for the item and organization around it.
How the work is organized
- Item identity. The SKU and base unit provide a consistent way to describe quantity across requests and movements.
- Lot identity. The lot code, expiry, release state and owner reference give the team the operating context for that item.
- Review context. The reviewer checks the requested item against the selected location, lot details and any current restrictions.
What to agree during setup
Agree how the team assigns SK us and lot codes, which organization owns each item, and which base unit is used for quantities. Decide who maintains release state and how the team records a quarantine or block. App Administrator maintains the item setup; Inventory Reviewer makes independent decisions on stock requests. Those responsibilities should remain separate even when a small team has several duties.
A useful pilot includes a released lot, an expiring lot and a blocked lot for the same item. Compare them in the lot register and in a request for a specific location. The review discussion should identify the exact lot and quantity rather than relying on a free-text description of the item. Expiry is a date on the lot; it should be checked at the time of the stock decision.
Check the handoff on an actual case
Suppose a warehouse receives an item with two lot codes and different expiry dates. App Administrator confirms the item and base unit, and Inventory Coordinator checks both lot records before preparing the request. Inventory Reviewer checks the request revision and decision reason. When a movement is recorded, its item and lot references should lead back to the same identity the team reviewed. If a lot becomes blocked, the team can find its movements and reservations without merging it with another lot of the same item.
What your team sees
- Released lots — The lot code, item, expiry and owner reference for stock marked Released.
- Restricted lots — Quarantined and Blocked lots that require attention before use.
- Lot expiry review — Lots whose expiry date needs a current decision.
Follow the work through
Continue to stock request review and lot recall handling.
What it keeps track of
Data model- Stock items
- Stock item master with base unit and lot tracking flag.
- Stock lots
- Lot and batch records with expiry and release state.
- Stock requests
- Stock receive, move, reserve and recall requests with lifecycle and revision.
- Stock movements
- Posted signed stock movements produced by guarded workflows.
- Stock reservations
- Active, released and consumed reservations against eligible stock.
Who uses it
Permissions- App Administrator
- Maintains item setup.
- Inventory Coordinator
- Prepares stock work.
- Inventory Reviewer
- Inspects the requested revision and its lot context.
- Auditor
- Reads the authorized history.
Set up SCM with Lot Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.