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
- Reservations
Reservations
Trace each claim to a request, item and location before stock is consumed.
OverviewActive reservations×
Fashion/Apparel SCM · Reservations
New
Active reservations
Stock reservations
| Id | State | Quantity | Expires at | Request | Item | |
|---|---|---|---|---|---|---|
| IDD-434 | Active | 510 | 03 Oct | SR-25245 | SI-4892 | |
| IDD-620 | Active | 860 | 22 Oct | SR-89696 | SI-6894 | |
| IDD-547 | Active | 90 | 23 Oct | SR-83741 | SI-8994 | |
| IDD-883 | Active | 960 | 14 Oct | SR-92402 | SI-8355 | |
| IDD-180 | Active | 390 | 14 Oct | SR-68063 | SI-4646 |
6 of 6 records
IDD-434Stock reservations · SR-45965
ActiveQuantity510
Expires at03 Oct
RequestSR-25245
ItemSI-4892
LocationSL-110
What you can do
At a glance
Trace each claim to a request, item and location before stock is consumed. 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 reservation gives a claim a quantity, expiry and state, with references to the request, item and storage location. A lot reference can identify the exact lot for controlled stock. The claim is separate from on-hand quantity: a reservation does not itself post a movement.
- Keep the control visible. Active, Released and Consumed describe the claim’s life. An active reservation needs a current request and eligible stock. The expiry date helps teams review claims that should no longer hold supply. The Lot Release & Expiry Gate also highlights reservations sitting on non-released or expired lots.
- Make the decision traceable. When a request is executed, the coordinator reconciles the claim with the posted movement and records whether it was consumed or released. A correction should preserve the link to the original request instead of creating an unexplained free quantity.
What to agree during setup
Agree when coordinators create reservations, how long claims remain active, and who resolves conflicts over the same lot. Establish a daily review for expired claims and claims attached to restricted lots.
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 request for a size-color SKU reserves units at a distribution location. Before the team records a movement, its lot is quarantined. The gate shows the active claim against a non-released lot. The coordinator returns to the request, finds another eligible lot if the operation still makes sense, and releases or changes the claim through the team’s normal review. The posted effect is reconciled only after the claim and lot agree.
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
- Active reservations — Open claims with quantity, expiry, request and optional lot.
- Restricted lots — Lot restrictions relevant to active claims.
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 reservations
- Active, released and consumed claims against eligible free quantity.
- Stock requests
- Guarded stock operations requested by a coordinator for an exact SKU and location.
- 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.
- Storage locations
- Warehouses, DCs and 3PL sites holding apparel stock.
- Stock movements
- Posted signed movements that are the only source of on-hand quantity.
Who uses it
Permissions- Inventory Coordinator
- Manages the claim.
- Inventory Reviewer
- Investigates conflicts.
- Auditor
- Follows the request 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.