If we perform an inventory count with a positive deviation, the receiving inventory movement won't have an associated cost, leading to incorrect inventory valuation. Expected would be to consider defined product unit cost or product average cost. Also, when performing the inventory count in the tablet there is a misleading "Is Empty" button available when selecting the product. However, this just jumps the tablet selection and does not create inventory movements to zero out the inventory in the selected warehouse. Finally, it always asks the counted lot, even if we are not using this feature. Show More

It would be a really handy feature if we could add taxes directly to the Purchase Order price. That way, we’d have a more accurate view of the actual cost of the PO. It would help us better understand the real expenses upfront instead of having to calculate it separately or guess later. This small addition could make a big difference in tracking and planning costs more effectively Show More

Recently, you implemented Theoretical Inventory Valuation that is based on the Unit Cost field that is located within the product's Details page. This is a great feature that allows us to compare our inventory valuations against our all-time average unit cost against our most recent unit cost.   It would be awesome if, when saving a new purchase order, a window or message would pop up asking (yes or no) if we would like to update that product's Unit Cost Field to the unit cost used on that new purchase order.   Having the option is key, as there are times when you do not want a particular purchase order to change that information. This would make it very easy to accurately maintain a current theoretical valuation. Show More