Scenario:
The user noticed that the “Quantity on PO” field under the Inventory subtab of an item record is showing a decimal value, even though the item is typically ordered in whole numbers (e.g., packs).
Upon investigation, the issue occurred because the warehouse received a partial quantity in “eaches”, while the original purchase unit was in “packs.” The warehouse team changed the unit of measure during receiving by switching from "packs" to "eaches" when scanning items using the handheld device (gun). The user wants to understand why this happens and if it can be prevented or corrected.
Solution:
This is standard behavior and occurs due to the use of mixed Units of Measure (UOM) between related transactions (e.g., Purchase Order and Item Receipt).
When the unit of measure used for receiving is different from the one used during purchasing, NetSuite converts the quantities based on the conversion rate set between those units. If the units don’t convert evenly (e.g., 1 pack = 3 eaches, and you receive only 1 each), it results in a floating point or decimal quantity being reflected on the PO metrics like “Quantity on PO.”
Suggested Solutions / Workarounds:
- Receive the Remaining Quantity in Full
If the order was partially received, completing the full receipt (in matching units) may cause the Quantity on PO value to round back to a whole number once the order is fully fulfilled. - Use Consistent Units of Measure
To prevent this issue:- Standardize the UOM across related transactions (e.g., always use packs for ordering and receiving).
- Avoid switching to “eaches” during scanning if the PO was created in packs.
- Train warehouse staff to receive in the same unit type used in the PO whenever possible.
- Review Unit Conversion Settings
- Go to the item record > Units Type, and ensure the conversion rates between units are properly defined.
- If you're using custom units, double-check their definitions to ensure no unintended fractional results.
Limitations:
- As long as different unit types are used across linked transactions, this behavior cannot be completely avoided. The system will always calculate quantity values based on conversion logic, which may lead to decimal results.
- If your process requires receiving in smaller units, you may need to adjust your reporting logic to account for decimal precision.
-----
If you find this information useful, let us know by reacting or commenting on this post!