520 On Hand, 40 Available
Cobalt Outfitters sells through two channels from a single NetSuite account: a 3PL warehouse in Reno and a retail store in Austin that also ships web orders. The item 'Trail Jacket' shows 520 on hand in Reno, but the item record's available quantity reads 40. There are 26 open sales orders against Reno, one of them for 300 units that has sat in Pending Fulfillment for nine days, and a transfer order from Reno to Austin for 150 units that was approved but never fulfilled. The 3PL also sends a nightly inventory CSV that has failed for two days. The controller asks why the item's average cost moved from $62.10 to $58.40 after a recent receipt, and whether the 300-unit order can simply be moved to Austin, where 180 units are on hand. The item has no serials or lots and is not drop-shipped.
1. Why does the item show 40 available when 520 are on hand, and how would you confirm the cause?
Read the worked answer
On hand is a stock fact; availability is a promise. NetSuite reduces availability by committed quantities, and commitment happens according to the Inventory Commitment preference - at order entry, at approval, or at fulfillment request - depending on how the account is configured. With 26 open orders against Reno, it is entirely plausible that roughly 480 units are committed, leaving 40 available. Confirm in this order: run a saved search by item and location showing on hand, committed and available; check the Inventory Commitment preference; check whether the 300-unit order is actually committed or merely entered; and check whether the failed 3PL feed left receipts unposted, which would understate on hand rather than overstate commitments. The order is not stuck because of a defect - it is stuck because the stock is already promised elsewhere. The fix is to release or re-date commitments, transfer stock, or split the order.
2. The client wants to move the 300-unit order to Austin. What do you check, and what options do you present?
Read the worked answer
Do not simply edit the location on the line and hope. First check what Austin's 180 on hand is already committed to, because moving a 300-unit line against 180 available units just relocates the shortfall. Present three options: (a) split the order - fulfill 180 from Austin now and 120 from Reno when stock is available; (b) raise or complete a transfer order from Reno to Austin for the balance and fulfill once the transfer is received; (c) edit the line location before any fulfillment exists, which is legitimate if nothing has shipped and Austin stock is genuinely free. Consider cost: average cost may differ by location, so fulfilling from Austin changes COGS on that order. Also remember the approved 150-unit transfer order is already inflating Reno's committed quantity - that is part of why Reno shows 40 available. Resolve that transfer before promising its stock to a customer.
3. Why did the average cost move from $62.10 to $58.40, and does it restate past COGS?
Read the worked answer
Average costing is a moving average, so every receipt recalculates the item's cost: new average = (quantity on hand x old average + receipt quantity x receipt cost) / (quantity on hand + receipt quantity). A drop to $58.40 means the receipt came in below the running average - a lower vendor price, a different landed cost treatment, or freight that was not applied. Verify the receipt unit cost and any landed cost lines. Then check sequencing: a receipt dated before existing transactions, or keyed out of order, can leave a cost history that looks wrong until cost recalculation runs. On restatement, average costing adjustments do not retroactively rewrite closed periods, so January margin typically stands even after you correct the record. If the item is genuinely cheaper now, that is a purchasing result rather than an error - document the calculation so the controller can see the arithmetic.