Configuring UoM (Units of Measurement)

Configuring UoM (Units of Measurement)

Software Plan: Growth & Enterprise
Account Type: Seller Account & 3PL Aggregator

Inventory Type: Serialized & Non-Serialized


Feature Description

A unit of measure (UOM) is the unit into which any given item can be packaged. For example, you can package drinks in a single can, a two-liter bottle, or a pack of 6 cans, etc.


UoM or Unit of measurement in EasyEcom is defined as Pallet, Case, Pack, and Each(SKU).

Multiple items for a SKU make an inner pack. Multiple inner packs make a case. Multiple cases make a pallet-





How and where can this be used?

You can define how many items constitute a case or how many items constitute an inner pack. 


Suppose, the user has to pick 500 items of this SKU as a part of a bulk order, while getting the items from the shelf, he will only have to pick/scan 5 cases of that SKU. 


This feature saves time and helps warehouse workers to pick up or scan the items quickly.


Once you configure UoM in EasyEcom, you can use this during GRN inwarding or picking the items during picklist generation.

Constraints

  • There will be no restriction of mapping items to bin or in bin put-away. A single bin can have multiple UOM items. Ie. The same bin can have eaches as well and cartons as well. The system will not restrict this. If it's required then OPS will have to manage this.

  • Inventory exposure via API to Outer world will always be in eaches quantity.

  • Orders will come via API OR CSV will always be in eaches qty.

  • A Virtual SKU cannot be marked as UOM and vice-versa.

  • The maximum allowed value for nextBreakableSkuQty is 200, i.e a maximum 200 units of the next breakable SKU can be present in a UOM unit.

  • UOM SKUs will not be supported in kitting workflow.

  • Perishable UOMs cannot be defined with Non-Perishable each SKU and vice-versa.

  • UOM and NextBreakableSKU cannot be uploaded in single UOM definition creation CSV.

  • Once the UOM definition is uploaded, it cannot be modified again.


How to configure UoM in EasyEcom?


Step 1: Go to the Hamburger menu > Master > UoM




Step 2: Click on “Configure Uom”




NOTE: You can configure UoM one by one OR you can do Bulk upload as well.




The below process is for individual configuration (UI Interface). The bulk process is explained later in the document.


Step 3: Enter the details:


a) Choose UoM type


UoM can be configured in two types: Case and Inner pack




b) Enter UoM EAN. This is the number that you will scan/enter in the future while inwarding GRN or picking the items during the packing process.


c) Enter the SKU which you want to club into cases or inner pack


Only 1 type of SKU can be configured per UoM. 


d) Enter the number of SKUs that constitute a case or an inner pack. Example: 30 SKUs in an inner pack or 300 SKUs in a case.


Step 4: Click on create

Once you have entered all the necessary details, click “Create”. 




Bulk Upload: 


Step 1: Click on “Bulk Entry”




Step 2: Download the template and enter details in the Excel file


Click on Download template. An excel file will be downloaded. Enter the details in the excel sheet and save it.




Asterisk (*) marked columns are mandatory.

Step 3: Upload the file 




Step 4: Click on “Complete”




UoM (Unit of Measurement) Inwarding & Letdown Process

Inwarding of UoM

  • UoM can be inwarded into the system via:

    • Web portal

    • Android app

Order Assignment with UoM

  • When an order is placed (e.g., 1000 qty), the system checks for available UoM configurations.

  • For example, if 1 UoM = 500 qty, then:

    • The system will assign 2 UoM to the order (i.e., 2 x 500 = 1000 qty).

  • If the order qty is 1100:

    • The system will assign:

      • 2 UoM (500 qty each) = 1000 qty

      • The remaining 100 qty will be fulfilled from eaches (loose inventory)

If Eaches Are Not Available

  • If required eaches are not available, system will not be able to fulfill the entire order.

  • In such cases, user must perform a UoM Letdown to break the UoM into eaches.

UoM Letdown Process
  • The Letdown process allows users to break UoM inventory into individual units (eaches).

  • Once the letdown is done:

    • The system will be able to pick the remaining quantity from eaches and complete the order assignment.

In android : Go to Android > Picklist.


Suppose- we have to scan 1030 items and we have configured UoM that has 500 items in 1 case. Now if we scan that particular UoM number, 500 items will be scanned in one go.


If you scanned UoM 2 times, 1000 items will be scanned. 30 items will be remaining out of 1030. Now you can scan those 30 items individually for the remaining part.


FAQs

1. What is a Unit of Measure (UoM) in the context of warehouse operations?
A Unit of Measure (UoM) represents how inventory is stored and managed—such as by piece, case, or pallet. Defining UoMs helps standardize inventory processes, allowing for faster and more accurate inbounding, picking, and dispatch.
2. What is the role of the Letdown process in warehouse efficiency?
Letdown is the practice of converting bulk inventory into smaller units (e.g., breaking a case into inner packs or individual pieces). This ensures that pick zones are regularly replenished and prevents last-minute delays during order fulfillment.
3. At which stages in warehouse operations can UoM be applied?
UoM logic can be implemented across inwarding, putaway, storage, picking, packing, and dispatch. It brings structure to how stock is managed across all these processes.
4. Is it possible to implement UoM and letdown processes without using a WMS?
While it’s technically possible to manage UoM manually, it becomes error-prone and inefficient at scale. A Warehouse Management System is highly recommended to automate, track, and maintain consistency in UoM operations.
5. How should I decide which products should follow a defined UoM structure?
Start by identifying SKUs that are high in volume or frequently ordered in bulk. Analyze order patterns to determine logical pack sizes. Align with your distribution partners before rollout to ensure operational alignment.
7. Can multiple UoMs be configured for the same product?
Absolutely. For example, you might define 1 case = 12 units and 1 inner pack = 6 units for the same SKU. This flexibility helps meet diverse customer needs without duplicating SKUs.
8. Can an order include both UoM stock and loose items?
Yes, a single order can contain both full-case (UoM) and piece-level items. The system will split the pick tasks accordingly and source items from the appropriate zones.
9. How are returns handled when the product was dispatched as a UoM?
During returns, UoM items are broken down during quality checks. If they pass QC, they’re either repacked into UoMs or reclassified as eaches based on the item’s condition.

  1. How to return the UoM items in HHT Android
  2. UoM Letdown Process
  3. QR Code Scanning on GRN page







    • Related Articles

    • How to return the UoM items in HHT Android

      Software Plan: Growth & Enterprise Account Type: Seller Account, 3PL- aggregator account Inventory Type: Non- Serialized Feature Description This feature simplifies the returns process for business-to-business (B2B) transactions and items sold in ...

    • UoM Letdown Process

      Software Plan: Growth Account Type: Seller Account Inventory Type: Non-Serialized Feature description Letdown is the process of breaking a UoM type into its constituent UoM type. For eg. A case can be letdown(break down) into inner packs or an inner ...

    • QR Code Scanning on GRN page

      Software Plan: Growth & Enterprise Account Type: Seller Account & Aggregator 3PL Inventory Type: Non-Serialized Feature Description Easyecom now features QR code scanning on the GRN (Goods Receiving Note) page as well as in HHT. This new feature ...

    • B2B Order Processing (New)

      Software Plan : Growth & Enterprise Account Type : Seller Account Inventory Type : Serialized & Non-Serialized Feature description Easyecom announces a significant upgrade to its B2B order processing platform, prioritizing enhanced efficiency, ...

    • HHT - Putaway - GRN Putaway

      Software Plan : Growth & Enterprise Account Type : Seller Account & Aggregator 3PL Inventory Type : Serialized & Non-Serialized Feature Description The GRN PutAway feature marks the final stage in the inbound inventory process, where received goods ...