Hi all,
I'm looking to roll out NetSuite's Supply Allocation feature to my production instance. My goal is to resolve reserved demand on POs - what is reserved vs. what is still open - and let my business team open an SO and see exactly which POs its lines are allocated to. We already do this today, but in a much more manual way outside of NetSuite.
I've been sandbox testing, and the core use case of allocating future inventory from specific POs at specific locations is genuinely helpful. I've been testing with Expected Receipt Date and Supply Required By Date, and for the most part everything makes sense using a future strategy with a Reserved allocation type. I also have the real-time preference enabled (Perform Supply Allocation After Transaction Entry, Update or Delete).
A few questions from my testing:
- Is there a quick way to bulk-reallocate supply to a new priority set of orders or to a priority customer? Ideally, I could open an order, click something like "reallocate to this order," and the system would pull from other orders holding the same PO supply based on the strategy + update all of that order's line items so that it is fully allocated. So far, the only native option I've found is the Reallocate Order Item recommendation, which is line-by-line and order-by-order — very manual at volume. The workaround I've landed on is flipping the lower-priority donor orders' line-level strategy to -Do Not Allocate-, which releases the allocation immediately and the real-time recalc flows it to the next orders that need it, then flipping the donors back to the future strategy afterward. It works, but it also takes forever, and I don't find it very scalable. Is there a better supported bulk approach I'm missing?
- Reserved vs. Firm allocation — Reserved is behaving much more "firm" than I expected. Even when I move a later order's Supply Required By Date earlier than the orders currently holding the supply, the allocation never moves. New orders with earlier Supply Required By Dates also get zero allocation while earlier-entered orders keep everything. I expected Reserved to mean the system could displace the allocation when priorities change, but every recalculation trigger I've tested (date edits, new order entry, the Allocate Orders page) seems to only distribute unallocated supply and never takes from an existing order. Am I doing something wrong, or is first-come-first-served-and-sticky just how the system works, with the Reallocate recommendation as the only displacement mechanism?
- Related to #1 — do any of the batch Allocation Processing Options on the Allocate Orders page (Fill Rate Optimization, Revenue Optimization, Gross Profit Optimization) actually displace existing reserved allocations among the selected orders? Or do those also only optimize the distribution of unallocated supply? I ran the page with donors and priority orders selected together, sorted by Supply Required By Date, using "Using Sorting Options Only," and nothing moved.
- One more sanity check — some AI-generated guidance pointed me to the Reallocate Items page, but my read of the docs is that page belongs to the classic item commitment engine and doesn't apply once Supply Allocation is enabled. Can anyone confirm?
Beyond these, if you have any Supply Allocation tips, tricks, or lessons learned from production rollouts - especially around bulk operations, saved searches for allocation visibility, or gotchas with the strategy-flip workaround — I'd really appreciate it.
Thanks!
-T