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.
- Fashion/Apparel SCM
- Features
- Items and lots
Items and lots
Keep the apparel SKU and the physical lot separate so release and expiry remain visible.
OverviewPending lots×
Fashion/Apparel SCM · Items and lots
New
Pending lots
Approval conditions
| Id | Lot code | Release state | Expires at | Item | Owner reference | |
|---|---|---|---|---|---|---|
| IDD-696 | LC-500 | Pending | 04 Oct | SI-5409 | OR-856 | |
| IDD-557 | LC-527 | Pending | 14 Oct | SI-4812 | OR-824 | |
| IDD-377 | LC-966 | Pending | 05 Oct | SI-9219 | OR-927 | |
| IDD-369 | LC-550 | Pending | 25 Oct | SI-9315 | OR-550 | |
| IDD-584 | LC-797 | Pending | 09 Oct | SI-1217 | OR-106 |
6 of 6 records
IDD-696Stock lots · SL-62245
PendingLot codeLC-500
Expires at04 Oct
ItemSI-5409
Owner referenceOR-856
What you can do
At a glance
Keep the apparel SKU and the physical lot separate so release and expiry remain visible. Keep the related request, decision and stock evidence together as the case moves between people.
How the work is organized
- Record the operating identity. A stock item holds the SKU, name, base unit, organization, active flag and whether the item is lot tracked. A size-color style belongs in the item identity used by requests and movements. A stock lot then gives a lot-tracked item a lot code, owner reference, expiry and release state. The lot record carries release state and expiry for the eligibility check.
- Keep the control visible. Pending, Released, Quarantined and Blocked are distinct states. The Lot Release & Expiry Gate shows lots and reservations that require attention. A released label should be read together with the actual expiry date; an old release decision does not make expired goods eligible.
- Make the decision traceable. A movement can carry the exact item and lot, while a reservation can point to the same item, location and lot. This makes it possible to investigate a claim against restricted stock before a request is executed. The item’s base unit should remain consistent across the request and its movement.
What to agree during setup
Agree the SKU convention for size-color variants and the source of lot codes and expiry dates. Decide who maintains release state, how quarantine is resolved, and how owner references are reconciled when stock moves between sites.
Use a real size-color SKU and storage location to rehearse the first case. App Administrator should confirm the entity and site codes; Inventory Coordinator and Inventory Reviewer should agree which revision is ready for a decision. Keep that convention available to Auditor when the movement is reconciled.
Check the handoff on an actual case
A lot of a black medium style reaches its expiry window while an active reservation still points to it. The gate puts the lot and claim in the team’s daily review. The coordinator checks the request and location, and the reviewer examines the release context before any further effect. The team updates the lot state according to its operating decision and keeps the reservation and request evidence together.
At the handoff, compare the current request revision with the reviewer decision and any related lot, claim, receipt or posted movement. If a reference differs, give the case back to Inventory Coordinator with the mismatch named. Keep the earlier decision and effect visible to Auditor.
What your team sees
- Pending lots — Lot codes awaiting release attention, alongside their expiry.
- Restricted lots — Quarantined and blocked lots that must stay visible to reviewers.
Open the underlying record before making a decision that depends on revision, expiry, ownership or location. Inventory Reviewer should read the linked request and evidence before recording a reason; Auditor can follow the same references later.
Follow the work through
See the operating handoff and the implementation sequence. Use the data model when mapping existing identifiers and references.
What it keeps track of
Data model- Stock items
- Size/color style-level SK us tracked in their base unit.
- Stock lots
- Lot codes with release state and expiry for lot-tracked apparel SK us.
- Stock reservations
- Active, released and consumed claims against eligible free quantity.
- Stock movements
- Posted signed movements that are the only source of on-hand quantity.
- Stock requests
- Guarded stock operations requested by a coordinator for an exact SKU and location.
- Organizations
- Legal entities operating stock across the apparel supply chain.
Who uses it
Permissions- Inventory Coordinator
- Checks the item and lot.
- Inventory Reviewer
- Handles release exceptions.
- Auditor
- Reads the retained lot and movement trail.
Set up Fashion/Apparel SCM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.