A positive balance may answer the wrong question
Sales sees 10 units in the ERP and accepts a new order for five, but the warehouse cannot pick all five. A stock-count error is not the only possible explanation. The displayed figure may include stock committed to existing orders, stock at another location or expected future receipts. Before promising delivery, establish what the figure means, the date it represents and the location it covers.
Separate three layers before defining sales rules
Posted on-hand quantity reflects receipts and issues recorded in the system, so posting delays matter. Projected availability also considers future supply and demand. Actual pickable quantity further depends on reservations, stock status, location and bin. An aggregate balance alone cannot establish whether a particular order can ship from its required fulfillment point.
Microsoft Business Central documents Projected Available Balance as inventory plus scheduled receipts minus gross requirements, with views by event, period and location. This illustrates the principle, but field names and reservation rules vary between ERP products. Read the definitions for the actual system. In particular, a reservation already linked to a sales order should not be deducted again as an additional demand item.
An incoming receipt does not make stock available today
Hypothetical example: one warehouse has 10 usable units, eight reserved for an existing order shipping tomorrow, and six more due on a purchase order next week. A new customer requests five today. Assuming the existing reservation is honored and no alternative stock exists, only two units remain for the new order today, leaving a shortage of three. Next week’s receipt can support a later plan, but it cannot resolve today’s constraint.
Options include partial shipment, a delivery date tied to a verified receipt, or a transfer from another warehouse if stock and transit time permit. Reassigning stock from an existing customer to a new one needs an authorized decision with visible consequences. It should not happen through an undocumented reservation release merely to make the availability screen look sufficient.
Trace availability to transactions
Start with the same item code and unit of measure, the required location and the requested shipment date. Open the transactions behind receipts, demand and reservations. Check whether arrival dates are confirmed, canceled orders release reservations, and received goods are posted and placed in pickable bins. If quarantine or sales-block statuses exist, test that the sales-facing availability field actually excludes them.
Test the promise before enabling it for the team
Build tests in an environment that does not affect real orders: sufficient but reserved stock, stock at another warehouse, supply arriving after shipment day, and a delayed purchase order. Record the displayed balance, proposed date and pick-document result for each case. A passing result should be explainable from source transactions, not merely the ability to save a sales order. Where alerts leave gaps, require a temporary warehouse check before enabling automatic promises.
Give each team the view its decision requires
Sales needs the quantity and date it can promise, with conditions; the warehouse needs pickable stock by storage point; purchasing needs time-phased demand and receipts at risk of delay. An accounting and ERP implementation discussion with Chawinnix can begin with anonymized real-order examples. Agree on definitions and responsibilities before changing screens, so one figure is not used to answer incompatible questions.
