korber

Treat any inventory adjustment as a destructive write: it overwrites on-hand with no offsetting document and posts a loss or gain to the host. Size the adjustment, re-count the physical location first, get a named approver, and never split a large adjustment into smaller ones to bypass approval thresholds.

Available equals on-hand minus allocated minus everything in a non-available status such as hold, QA, or damage. Only available stock can be promised to orders, and the non-available status list is site-configurable, so treat unfamiliar statuses as unavailable until confirmed.

Cancelling a wave is reversible only while every work line is still in ready state. If any pick is confirmed or in progress, the cancellation becomes destructive because already-picked stock is stranded on staging LPNs and must be physically put away.

No. Manhattan Active WM and Blue Yonder WMS have their own skills. Blue Yonder uses MOCA commands, policies, and an ILPN/OLPN split, while Korber uses a single generic LPN and the Architect configuration layer, so the logic is not interchangeable.

Korber's Architect layer lets each site redefine business rules, workflow steps, validations, and auto-confirm behavior warehouse-wide. Always read the configured rule before classifying an operation, and default to the more dangerous risk class when the behavior cannot be established.

Re-read the inventory state first to check whether the original confirm already posted. Blindly retrying a pick confirm, receipt, or adjustment after a lock error can double-post the move and create phantom inventory or a duplicate goods movement to the host.