Business automation needs a safe trigger and recovery path
Trigger: the ordinary stock user validates six against ten demanded. Decision: retain the outstanding quantity. Result: a four-unit backorder and the sales line updating to six delivered. This is native stock behaviour, not a universal automation service.
A partial delivery creates a linked follow-up
Trigger: the ordinary stock user validates six against ten demanded. Decision: retain the outstanding quantity. Result: a four-unit backorder and the sales line updating to six delivered. This is native stock behaviour, not a universal automation service.
3 · The owner chooses the exception
The ordinary capture user validates six and chooses Create Backorder in the native dialog. The system does not silently treat the remaining four as delivered. Cancellation is a different decision and was not selected.
6 · Four waiting, zero available
Dat/OUT/00005 is Waiting with demand four and quantity zero. It links to Dat/OUT/00004 and S00002. Do not promise delivery until stock and the customer date are confirmed.
The same sales line carries the delivered quantity
S00002 keeps Demo Cedar Workshop and its address. Its line automatically shows 10 ordered, 6 delivered, 0 invoiced and two Delivery links. The stock part code is the same as P00002; the supplier and customer are separate contacts.
