Greetings all, we're in the middle of an implementation with NetSuite but ran into a blocking issue. We are a dye lot driven company. When creating a sales order, items are automatically committed to the sales order based on available quantity. We need to not do that, but instead only commit specific dye lot items selected under the Inventory Detail screen of the line item. (ie, if order is for 50 items, we have 100 on hand, but only 30 from the same dye lot, then the SO should only commit 30 items from that line item with 20 shown as back order) Does anyone know how to make this happen.?

this would probably take some pretty intense customization

Dye-Lot is the lot of items that were dyed together, so they appear the same color. This is pretty important for the garment/fabric industry because a color like "green" will look different on different days because its not an exact science. So if you had items that were dyed together, like a pillowcase/duvet-cover/fitted-sheet, they should all come from the same-dye-lot. Or if this was raw fabric, the rolls of fabric should be the same, otherwise, if you send a mixed set, its unusable for the purposes of manufacturing really, and its bad form for the customers perspective. Not sure how this would work in NS land, but thats what I know of Dye-Lot generally.

Makes sense - in that case - wouldn't you want it to not commit any to that order instead?

Setup > Accounting > Accounting Preferences > Order Management > PERFORM ITEM COMMITMENT AFTER TRANSACTION ENTRY

thanks for the replies everyone. I didn't have notifications on for this Slack tenant so missed all your informative replies. @Israel has the important TL;DR. Because of the dye lot driving, we cant' necessarily automatically commit items since they may jump dye lots if a customer is ordering more than whatever the first or last dye lot has in stock within a given dye lot sequence.

Rick, in my other platform we ended up having another process or step to identify dye-lots that were suitable and then committed it. I think you are on the right path, just that you need to improve setting the 100+ lot numbers on entry a bit faster. I have a couple of ideas on how to do this, but not exactly sure how to do it within native NS (just yet). I know from other projects we would just query inventory, find the inventory number suitable, and supply that to the API all in one shot. Now how to do that in a easy to consume step/workflow/customization I'm not entirely sure. I think standard NS is going to need a customization.

yea, we're looking at customizations as well, just trying to balance the cost involved in the customization with our priorities