Serialized UoM : Multi-Level UOM Serial Handling (USN Type 1 & 2)

Serialized UoM : Multi-Level UOM Serial Handling (USN Type 1 & 2)

Software Plan: Growth & Enterprise
Account Type: Seller Account
Inventory Type: Serialized

Overview

This feature enables handling of serial numbers across multiple Units of Measurement (UOM) levels for a SKU. Instead of managing serial numbers only at unit level, the system supports serial tracking at different UOM levels such as higher-level UOMs and their corresponding lower-level units.
All serials are stored and maintained in a parent-child hierarchy across UOM levels and are used across warehouse operations.

When to Use This Feature

Use this when you want to:
  1. Manage serial numbers across multiple UOM levels
  2. Maintain hierarchy between UOM levels (parent → child)
  3. Track serial movement across operations such as GRN, Letdown, Picking, and Returns

Operational Context

  1. Before this feature  
Serials were managed only at unit/item/eaches level  
  1. After this feature  
Serials are managed across multiple UOM levels with hierarchy

How Serial Structure Works

Inventory is handled in a hierarchical structure:
Higher-level UOM
 ├── Intermediate UOM
 │     ├── Lower-level units
Example:
  • 1 Higher-level UOM → Multiple lower-level units

Prerequisites

  • Serialized inventory must be enabled at account level
  • Correct USN type (Type 1 or Type 2) must be configured
  • multi_level_uom_serial setting must be enabled
Inventory → Purchase Order → GRN
(Also applicable in: Letdown, Picking, Packing, Returns, Bin Transfer)

Process Overview

1. Inventory is inwarded with UOM-level serial data
2. System captures serials across UOM levels
3. Serial hierarchy is created and stored
4. Inventory becomes available for further operations

Web Step-by-Step Process

Step 1: Create / Open Purchase Order

(Click here to learn more on USN)
  • PO is created as per USN type configuration
  • For Type 1: serials may be predefined (as per system rules)

Step 2: Start GRN

Go to:
Inventory → Purchase Order → View Details → GRN


Step 3: Capture UoM Serials

Serial data is captured for the SKU across UOM levels.

System behavior:
  1. Identifies UOM structure
  2. System captures serials based on the configured UOM hierarchy.
  3. Maintains parent-child hierarchy


Step 4: Validate and Save

  • System validates serials (based on USN type)
  • Saves full hierarchy
  • GRN is completed

Step-by-Step Process (Android – Device Based)

Step 1: Open GRN on Mobile App

  • Open Easyecom mobile app
  • Click on Start Inwarding Items (GRN)

Step 2: Select Purchase Order

  • Search or select the relevant PO

  • Open GRN for that PO

Step 3: Capture Serial data using device input




Important:

  • Serial data is handled as per configured UOM hierarchy
  • Manual entry is not applicable in this flow

Step 4: System Auto Capture

Quantity is automatically updated based on the constituent quantity mapped to the scanned UOM serial wheras user can select Select Good/Bad


Step 5: Complete GRN

  • Verify details
  • Save / Submit GRN

System Behavior

1. Serial Capture

  • Extracts serial hierarchy across UOM levels
  • Parent-child relationship is maintained

2. Input Restriction

  • Manual serial entry is not used
  • Parent-child relationship is maintained

3. USN Type Behavior

USN Type 1

  • Unit-level serials validated against PO
  • Higher-level serials (case/pack) are accepted as provided

USN Type 2

  • No PO validation
  • All serials accepted and stored

Letdown (Inventory Breakdown)

Letdown allows breaking inventory into smaller units. (Click here to learn more on UoM Letdown Process)

Scenario: Received: Serial handling follows configured UOM hierarchy

After Letdown

  • Higher-level UOM serial becomes inactive
  • Lower-level UOM serials become active

Key Rule

  • Once a parent level is broken:
    • That serial is no longer usable
    • Only child-level serials remain active

Operational Rules

  • Serial hierarchy must be valid
  • Parent serial cannot be reused after breakdown
  • The feature works only when the required UOM serial settings are enabled for the account.
  • Applicable only for USN Type 1 & 2
  • Case → Each (without Inner Pack) is not supported.

Outcome

  • Serial tracking across multiple UOM level
  • Maintained hierarchy between UOM levels
  • Controlled inventory breakdown using letdown
  • Improved traceability across operations

QR Code Structure

Info

When encoding JSON into a QR code, you are generally limited to 2,953 characters.

If your JSON exceeds this, QR cannot be generated. but there is a solution. You can minify the JSON which will remove unwanted characters from the JSON and then you will be able to use the minified JSON to create the QR. 

Minification doesn't increases the character limit but it just removes unwanted characters to reduce the no. of characters.

Use a simple product example to understand how serials are structured.

Case = 10 units → 2 Inner Packs × 5 Each

Case → Inner Pack → Each

{
  "UOM": "Case",
  "QTY": 10,
  "UOMSERIAL": "CASE_001",
  "SERIAL_BREAKUPS": [
    {
      "UOM": "Inner Pack",
      "BOX_QTY": 2,
      "SERIAL_BREAKUPS": [
        {
          "SERIAL": "IP_001",
          "units": ["E_001", "E_002", "E_003", "E_004", "E_005"]
        },
        {
          "SERIAL": "IP_002",
          "units": ["E_006", "E_007", "E_008", "E_009", "E_010"]
        }
      ]
    }
  ]
}

Inner Pack → Each

{
  "UOM": "Inner Pack",
  "QTY": 5,
  "UOMSERIAL": "IP_001",
  "SERIAL_BREAKUPS": [
    {
      "SERIAL": "IP_001",
      "units": ["E_001", "E_002", "E_003", "E_004", "E_005"]
    }
  ]
}

FAQs

Q1. Are serials managed only at unit level?
No. Serials are managed across multiple UOM levels with hierarchy.
Q2. Can I manually enter serials?
No. UOM input is system-driven based on configuration.
Q3. What happens to case serial after breaking inventory?
It becomes inactive and cannot be used further.
Q4. Does this change actual inventory quantity?
No. It only changes how serials are captured and tracked.
Q5. Is this feature related to item-level serialization?
No. Item-level serialization already exists. This feature extends serialization to multiple UOM levels and manages hierarchy across them.

    • Related Articles

    • Unique Serial Numbers (USN) – Serialized Inventory Handling

      Software Plan: Growth & Enterprise Account Type: Seller Account / 3PL Inventory Type: Serialized Inventory USN configurations are enabled at the account level by the Easyecom team. Overview Unique Serial Numbers (USN) is a configuration used to ...

    • USN : Detailed document with Printing serialized barcodes

      When you use serialized inventory and want to validate the correct serial at the GRN step where the serial no. barcode would have been generated before GRN, then use the USN feature to make your process more efficient. USN Types Type 1: Sellers who ...

    • HHT- How to return the UoM items?

      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 ...

    • B2B Order Processing (New)

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

    • Scanning of Tagloops- B2C

      Scanning of Tagloops On New Orders Page This video demonstrates the process of scanning Tagloops on the New Orders page under the Ready to Confirm tab if you don't wish to scan the tagloops at the packing station. It highlights how sellers can ...