A practical explanation of why visible stock can still fail availability, ATP, allocation, or channel commitment checks.
Reviewed
Where this fits
This page sits between inventory reporting and customer commitment. It is useful when business users say stock is visible in one place, but an order, store channel, or online promise still cannot use it.
Common issues
Stock is in the wrong plant, storage location, channel, or stock type for the process being checked.
Stock is physically present but already committed, reserved, blocked, or not included in the relevant availability logic.
Retail, e-commerce, and distribution channels may apply allocation or promise rules that differ from simple unrestricted stock visibility.
Diagnostic questions
Which stock figure is the user looking at, and which process is trying to consume or promise it?
Is the stock unrestricted, relevant to the checked location, and available on the requested date?
Is another document, allocation rule, or protection rule already consuming the quantity?