How to Configure Unit of Measure in iDempiere for Retail

The Unit of Measure (UOM) window defines the measurement units used for products, inventory, purchasing, sales, and transactions. Unit of measure determines how products are quantified throughout the system.

Business Value – In retail, UOM configuration supports products sold individually, by weight, by volume, by packaging unit, or by length — ensuring accurate quantities across purchasing, warehousing, and sales.

Prerequisites

Before starting, ensure the following:

  • Initial Tenant Setup completed successfully
  • Product master data is available or planned

Business Rules

  • Never Inactivate System UOMs System-provided UOMs (Day, Week, Month, Year) must never be deactivated — they are referenced by other modules. Inactivating them breaks scheduling, service, and other dependent configurations.
  • Set Precision Based on UOM Type Whole-unit UOMs (EA, PCS, CASE) must use Standard Precision = 0. Weight, volume, and length UOMs (KG, LT, MTR) must use Standard Precision = 2 or 3. Wrong precision causes quantity and costing errors.
  • No Duplicate UOM Codes Every UOM must have a unique UOM Code. Always check existing system records before creating a new one. Duplicates cause conflicts in product assignment and reporting.
  • Conversions Are Configured Separately UOM conversion factors (e.g., 1 CASE = 24 PCS) are never set inside the UOM record. They must be configured in the dedicated UOM Conversion window.

Navigation

Open the Unit of Measure window:

Menu → Material Management → Material Management Pricing → Unit of Measure

Step-by-Step Configuration

Step 1: Open Unit of Measure Window

Navigate to the menu path above. The window displays all existing UOM records, including system-provided defaults.

Step 2: Create New Record

Click New Record (+) to open a blank form. Enter the required values.

Field Reference

  • UOM Code — Unique identifier for the unit (e.g., EA, KG, MTR)
  • Symbol — Short representation displayed in transactions (e.g., Ea, kg, m)
  • Name — Full display name of the unit
  • Description — Business purpose of the unit
  • Active — Makes the UOM available for use in transactions
  • Default — Marks as the system-wide default measurement unit
  • Standard Precision — Controls decimal places for quantity fields
  • Costing Precision — Controls decimal places for cost calculations

Step 3: Configure Standard Retail UOMs

Set up the following UOMs for retail operations:

EA — Each

FieldValue
UOM CodeEA
SymbolEa
NameEach
DescriptionIndividual item unit
Standard Precision0
Costing Precision2
ActiveYes

Used for: shirts, shoes, bags, electronics — any product counted as individual units.

PCS — Piece

FieldValue
UOM CodePCS
SymbolPc
NamePiece
DescriptionSingle product unit
Standard Precision0
Costing Precision2
ActiveYes

Used for: accessories and individually counted products.

CASE — Case

FieldValue
UOM CodeCASE
SymbolC
NameCase
DescriptionBulk packaging unit
Standard Precision0
Costing Precision2
ActiveYes

Used for: supplier packaging and warehouse stock handling. Example: 1 CASE = 24 PCS.

KG — Kilogram

FieldValue
UOM CodeKG
Symbolkg
NameKilogram
DescriptionWeight measurement unit
Standard Precision3
Costing Precision4
ActiveYes

Used for: fruits, vegetables, rice, and other weight-based products.

LT — Liter

FieldValue
UOM CodeLT
SymbolL
NameLiter
DescriptionLiquid measurement unit
Standard Precision3
Costing Precision4
ActiveYes

Used for: milk, juice, oil, and other liquid products.

MTR — Meter

FieldValue
UOM CodeMTR
Symbolm
NameMeter
DescriptionLength measurement unit
Standard Precision2
Costing Precision4
ActiveYes

Used for: fabric and cloth material.

Step 4: Save Record

Click Save after entering all values. The UOM is immediately available for product and transaction configuration.

Configuration Summary

UOM CodeSymbolNameUsage
EAEaEachIndividual items (clothing, electronics)
PCSPcPieceSingle count products and accessories
CASECCaseBulk / supplier packaging (1 CASE = 24 PCS)
KGkgKilogramWeight-based products (produce, grains)
LTLLiterLiquid products (beverages, oil)
MTRmMeterLength-based products (fabric, cloth)

Business Flow Overview

Product Setup (UOM assigned)

Purchase Order (order quantity in UOM)

Goods Receipt (received qty in UOM)

Warehouse / Inventory (stock tracked in UOM)

Sales Order (sell quantity in UOM)

Shipment &
Invoice

System UOM Guidance

iDempiere includes pre-configured UOMs such as EA (Each), HR (Hour), Day, Week, Month, and Year. These are used by other modules including scheduling and service management.

Important Reuse system-provided records where possible rather than creating duplicates. Do not inactivate system UOMs — they may be referenced by other modules. Only create new UOMs when no existing record meets the business requirement.

UOM Conversion

Conversion rules between units (e.g., 1 CASE = 24 PCS) are configured separately in the UOM Conversion window, not within the UOM record itself.

Common Issues

IssueResolution
UOM not available on product formEnsure the UOM record is marked Active
Duplicate UOM codesCheck existing system records before creating new ones
Incorrect quantity decimal placesReview Standard Precision and Costing Precision values
System UOM missing from transactionsDo not inactivate system-provided UOMs
Changes not reflected after saveRun Cache Reset and log in again

Best Practices

  • Use meaningful UOM codes that align with industry standards (EA, KG, LT, MTR)
  • Reuse existing system UOMs before creating new records
  • Set Standard Precision to 0 for whole-unit UOMs (Each, Piece, Case)
  • Set Standard Precision to 2 or 3 for weight, volume, and length UOMs
  • Document naming conventions and precision rules in a configuration register
  • Do not inactivate system-provided UOMs referenced by other modules

Next Steps

After completing Unit of Measure configuration, continue with:

  • UOM Conversion — define conversion factors between related units
  • Product Setup — assign UOMs to products
  • Price List — configure pricing per UOM

Leave a Reply

Your email address will not be published. Required fields are marked *