UOM Mapping
Configure automatic EDI unit of measure translation and quantity conversion for inbound orders
How to configure Unit of Measure translation rules to convert EDI UOM codes into NetSuite-compatible units during inbound order processing.
Enabling UOM Mapping
UOM Mapping is disabled by default and must be enabled before use.
Navigation: Setup > Company > General Preferences > Custom Preferences
Set Enable UOM Mapping to Yes and save. Once enabled, the connector will apply your UOM Mapping rules during inbound order processing.
Overview
Trading partners often use EDI Unit of Measure codes (such as CA for Case or BX for Box) that don't directly match your NetSuite item UOM configuration. UOM Mapping lets you define translation rules that automatically convert EDI UOM codes into the correct NetSuite unit, with optional quantity conversion.
For example, if a trading partner sends 10 CA (cases) but your NetSuite item is configured in Each with 12 units per case, a UOM Mapping rule can translate CA → Each with a multiply factor of 12, resulting in a Sales Order line of 120 Each.
UOM Mapping Custom Record
UOM Mapping rules are managed through a custom record in NetSuite.
Navigation: Orderful EDI > Custom Mappings > UOM Mapping
Fields
| Field | Required | Description |
|---|---|---|
| Source UOM | Yes | The EDI Unit of Measure code to match (e.g., CA, EA, BX, LB). Case-insensitive. Max 20 characters. |
| Target UOM | Yes | The NetSuite UOM Type and Unit to map to. Displayed as a grouped dropdown organized by UOM Type (e.g., "Count - Each", "Weight - Pounds"). |
| Conversion Factor | No | A numeric multiplier or divisor applied to the EDI quantity. Defaults to 1 (no conversion). Minimum value: 0.0001. |
| Operation | No | How to apply the conversion factor: Multiply (default) or Divide. |
| Restrict to Items | No | Limit this rule to specific NetSuite items. If left blank, the rule applies to all items. Items must have the same UOM Type as the target unit. |
| Restrict to Customers | No | Limit this rule to specific customers. If left blank, the rule applies to all customers. |
Resolution Priority
When processing an inbound purchase order line, the connector resolves the EDI UOM code using the following priority order. The first match wins.
| Priority | Match Type | Description |
|---|---|---|
| 1 (Highest) | Item + Customer | A mapping rule restricted to both the specific item AND the specific customer |
| 2 | Item only | A mapping rule restricted to the specific item, with no customer restriction |
| 2 | Customer only | A mapping rule restricted to the specific customer, with no item restriction |
| 3 | Global | A mapping rule with no item or customer restrictions |
| 4 | Text match | No mapping rule found — falls back to matching the EDI code against NetSuite UOM names and abbreviations within the item's UOM Type |
| 5 (Lowest) | Item default | No match found — uses the item's default Sale Unit with no quantity conversion |
If multiple mapping rules match at the same priority level, the connector will return an error. Make sure your rules are specific enough to avoid ambiguity.
Quantity Conversion
When a mapping rule has a conversion factor other than 1, the connector adjusts the quantity on the Sales Order line:
- Multiply:
NetSuite Qty = EDI Qty × Factor - Divide:
NetSuite Qty = EDI Qty ÷ Factor
The original EDI quantity is preserved in the EDI Quantity column (custcol_orderful_edi_quantity) on the Sales Order line for auditing and outbound reverse mapping.
Examples
Basic unit translation (no conversion)
Your trading partner sends PC (Piece) but your NetSuite items use Each.
| Source UOM | Target UOM | Factor | Operation |
|---|---|---|---|
| PC | Each | 1 | Multiply |
Result: 50 PC → 50 Each
Case to Each conversion
Your trading partner orders in cases (CA), but you sell in individual units. Each case contains 12 items.
| Source UOM | Target UOM | Factor | Operation |
|---|---|---|---|
| CA | Each | 12 | Multiply |
Result: 10 CA → 120 Each (EDI Quantity column shows 10)
Customer-specific mapping
Two trading partners both send BX (Box), but one partner's box contains 6 units and the other contains 24.
| Source UOM | Target UOM | Factor | Operation | Restrict to Customer |
|---|---|---|---|---|
| BX | Each | 6 | Multiply | Partner A |
| BX | Each | 24 | Multiply | Partner B |
Weight conversion
A trading partner sends weight in kilograms but your items are tracked in pounds.
| Source UOM | Target UOM | Factor | Operation |
|---|---|---|---|
| KG | Pounds | 2.20462 | Multiply |
Validation
The UOM Mapping record enforces several validation rules when saving:
- Source UOM cannot be empty or contain leading/trailing spaces
- Conversion Factor must be greater than zero
- Restricted Items must have the same UOM Type as the selected target unit
- Duplicate rules at the same specificity level will cause processing errors — keep rules unambiguous
What's Next
Learn about other item configuration options:
Updated about 2 hours ago