Movements

Use posted signed movements as the quantity record for apparel stock. Keep the related request, decision and stock evidence together as the case moves between people.

• Record the operating identity. A stock movement records the signed quantity, item, location, optional lot, occurrence time and parent request. Posted distinguishes a completed stock effect. The line number and revision keep multiple effects under one reviewed request readable. A reversal points to the movement it corrects.
• Keep the control visible. An operation receipt captures the attempted action, expected revision, outcome and effect references. Completed, Failed and needs review outcomes provide a trace when execution is interrupted or requires reconciliation. The receipt should be compared with posted movements rather than interpreted as a stock quantity by itself.
• Make the decision traceable. The coordinator should use the item’s base unit when checking the requested units against the signed effect. Unit cost is present on a movement for the cases where the team records it. A movement may also capture lot code and expiry, allowing the reviewer to compare the effect with the referenced lot.

Agree who posts the effect after approval and how the team handles an operation that needs review. Define the cutoff for daily movement reconciliation, and require a reversal reference when correcting an earlier posted entry.

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.

An approved request calls for units at a distribution location. The coordinator checks that the lot is released and in date, then records the effect. A completed receipt points back to the request revision and movement. If the resulting signed quantity differs from the request, the reviewer traces the line and reversal rather than changing a balance directly. The auditor can follow the same chain later.

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.

• Posted movements — Signed effects with item, location, lot and request references.
• Operations needing review — Attempts requiring a reasoned follow-up before closing the case.

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.

See the operating handoff and the implementation sequence. Use the data model when mapping existing identifiers and references.