Scenario
A company implementing case packs in NetSuite needs to change an item’s Purchase Unit from: "Each" to "Case"
Before making the update, the team wants to understand the operational and accounting impact, including:
- inventory valuation
- item costing
- purchase order behavior
- saved searches and scripts
- warehouse implications
Solution
Changing the Purchase Unit primarily affects procurement behavior and transaction defaults, not historical inventory valuation.
What Changes
After updating the Purchase Unit to Case:
- New Purchase Orders default to the Case unit
- Buyers enter quantities in cases instead of eaches
- Vendor pricing should align with the new case quantity
- Lead times and purchasing workflows may need review
For example:
Before | After |
|---|
Purchase Unit = Each | Purchase Unit = Case |
PO Quantity = 100 Each | PO Quantity = 10 Cases |
What Does NOT Change
Testing showed that changing the Purchase Unit:
- does not affect historical transactions
- does not recalculate item cost
- does not change inventory value
This is because NetSuite inventory valuation is based on the Stock Unit, not the Purchase Unit.
In other words:
Unit Type | Purpose |
|---|
Stock Unit | Inventory valuation and quantity tracking |
Purchase Unit | Procurement entry and vendor purchasing |
Many companies keep:
- Stock Unit = Each
- Purchase Unit = Case
to maintain granular warehouse tracking while purchasing in bulk.
Notes
Before making the change, review the following:
- Saved Searches using unit cost calculations
- SuiteScripts referencing units or conversion rates
- Vendor price lists
- Reporting logic involving quantity or unit pricing
Note that custom logic may need updates to avoid “unit vs case” pricing discrepancies in reporting.
It is also important to note that:
- users can still manually change the Unit field on Purchase Orders after the default is applied
- testing in a sandbox is strongly recommended before bulk item updates
-----
If you find this information useful, let us know by reacting or commenting on this post!