We are a new company to NS still in the process of transferring things to NS. We are very pleased thus far but running into the expected headaches and disappointments as to be expected with something new.
One particularly concerning issue we have run into is in regard to UoM. As it stands UoM on a product can't be changed once it is saved to that product. I would like to know why? In what real world situation would the UoM never change? Moreover why would one have to "delete" the item from NS in order to modify the UoM and basically start from scratch(as suggested by our Accelerated Implementation team)?
One of the good things about NS is that it is relatively flexible compared to our existing ERP. But this issue kind of breaks the bank. Let me outline the real world situation we have.
Company A(us) purchase widget1 from one vendorY. That vendor sells the widget as a single unit, in boxes of 10 units, with a pallet of 20 boxes. 200 units total on a pallet purchase.
VendorZ approaches our company as says we can do a better deal for you with a higher quality product for a better price. You as Company A look at this an realize you can not only have a better margin you can lower the price to your customers who will be very happy and buy more widgets. The thing is that VendorZ sells the item as a single unit, in boxes of 20 units, with a pallet of 20 boxes. 400 units total on a pallet purchase.
Granted, Company A is buying more units but the price with VendorZ is less than VendorY so much so it makes no sense in any rationality to continue with VendorY.
Now with NS we have to delete that item, losing all of the historical data associated with it, or(just as bad), create a new sku which confuses everyone and really pisses off customers, sales people and fulfillment staff alike even though it is the same unit.
Why in any normal universe would this be like this?
Some input from my more experienced NS users and the NS employees would be greatly appreciated.