Said It Here

Why do orders allocate to incoming shipments instead of available stock?

Inventory systems automatically assign sales and work orders to incoming supply transactions rather than committing physical stock on hand. This causes fulfillment to fail because pick recommendations grab already-committed lots and trigger errors that inventory numbers are unavailable.

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

  1. 1
    Building custom scripting for lot-aware pin-and-firm passes, pin-before-wave gates, and true available calculations
  2. 2
    Turning off the Order Allocation Schedule
  3. 3
    Using firm commitment statuses as a brake

In their words

Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.

r/Netsuite2 people · September 2026

“Instead of allocating to available Inventory (and therefore committing the stock on hand, which allows fulfilment etc), the SO becomes allocated to the shipment (or to the Purchase Order, or Transfer Order - any supply transaction).”source ↗

“Curious to hear if any others are experiencing the same situation, and how you have got around it.”source ↗

OK-Candidate1388 · r/Netsuite · 6 upvotes

“The wave's FEFO pick recommendation grabs a lot that's already fully committed to another order, and fulfilment fails with Inventory numbers are not available”source ↗

“Drop a bad lot assignment and NetSuite re-commits the same lot.”source ↗

“Work-order components and sales orders fight over the same lots, and RF builds fail with You only have N available”source ↗

CommittedNotAvailabl · r/Netsuite · 4 upvotes

Where this came up

People with this problem also raised