> For the complete documentation index, see [llms.txt](https://docs.novacura.com/marketplace-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/marketplace-documentation/applications/explore-apps/ifs/warehouse-management/documentation/ifs-application-10/handling-unit-management/create-handling-unit.md).

# Create Handling Unit

## Overview

This flow (app) can be used to create one or more handling units connected or not connected to a shipment.

![](/files/mIIFuKfK6zBLvmdeMzUO)

*The complete overview of the flow:*

{% file src="/files/MaIYhQZDKiRgXSJ0EoL0" %}

## Steps

### Enter Shipment ID

* Shipment ID is not mandatory. Any shipment in Status ‘Preliminary’ belonging to user default site can be entered
* Click on the **List** button to see a list of available shipments which satisfy the above condition

{% hint style="info" %}
**Pin Step:**

* Display the user default Site ID and its description
  {% endhint %}

| <img src="/files/BBGw1NU01AwTGWEAyroA" alt="" data-size="original"> | <img src="/files/A4haxihvvI8mwQGpvPcP" alt="" data-size="original"> |
| :-----------------------------------------------------------------: | :-----------------------------------------------------------------: |
|                             Flow Connect                            |                             Flow Classic                            |

### Enter Handling Unit Type

* Handling Unit Type is mandatory, and any Handling Unit Type can be entered
* Click on the **List** button to see a list of available Handling Unit Types

| <img src="/files/J2qUqz1Npey1M5ouqdke" alt="" data-size="original"> | <img src="/files/v5K62b4EMnsWfcJeHPCK" alt="" data-size="original"> |
| :-----------------------------------------------------------------: | :-----------------------------------------------------------------: |
|                             Flow Connect                            |                             Flow Classic                            |

### Enter Parent Handling Unit

* Parent Handling Unit is not mandatory. The handling units allowed to be connected as a Parent should satisfy two conditions
  * The site of the handling unit should be either empty or the same as the user default site
  * If the Shipment ID is entered in the previous step, handling unit Shipment ID should match the same
* Click on the **List** button to see the list of Handling Units that satisfy the above conditions

| <img src="/files/9Xl3pLau3nNP4N7vzZFB" alt="" data-size="original"> | <img src="/files/WSWYzjDgEqRnkaf18Pgv" alt="" data-size="original"> |
| :-----------------------------------------------------------------: | :-----------------------------------------------------------------: |
|                             Flow Connect                            |                             Flow Classic                            |

### Enter No of Units

* This will create several handling units with the given configuration

{% hint style="info" %}
Default is set to 1.
{% endhint %}

|     | <img src="/files/VrHwbASvNGZ2BGmKaZrl" alt="" data-size="original"> |
| :-: | :-----------------------------------------------------------------: |
|     |                             Flow Classic                            |

### Check Generate SSCC

* This step is shown only if the selected Handling Unit Type is SSCC generation enabled

{% hint style="info" %}
Check box selection is optional.
{% endhint %}

|     | <img src="/files/u1cCDygNZb8zfMhbji01" alt="" data-size="original"> |
| :-: | :-----------------------------------------------------------------: |
|     |                             Flow Classic                            |

### Enter Alt Handling Unit Label ID

{% hint style="info" %}
This step is optional.
{% endhint %}

|     | <img src="/files/JyBvXA4W1shsXHJu09KE" alt="" data-size="original"> |
| :-: | :-----------------------------------------------------------------: |
|     |                             Flow Classic                            |

### Print Handling Unit Label

{% hint style="info" %}
This step is optional.
{% endhint %}

|     | <img src="/files/LNx7Go6Jy0vzn2dhBiRF" alt="" data-size="original"> |
| :-: | :-----------------------------------------------------------------: |
|     |                             Flow Classic                            |

### Print Shipment Label

{% hint style="info" %}
This step is optional and only shown if a Shipment ID is entered in the first step.
{% endhint %}

|     | <img src="/files/yJAKWFLRd7pOFT4Eo3zt" alt="" data-size="original"> |
| :-: | :-----------------------------------------------------------------: |
|     |                             Flow Classic                            |

### Summary

* Summary of all the steps performed. Click on the **Save** button to create the Handling Unit

|     | <img src="/files/515RoQPFpdveWgTzdMxW" alt="" data-size="original"> |
| :-: | :-----------------------------------------------------------------: |
|     |                             Flow Classic                            |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.novacura.com/marketplace-documentation/applications/explore-apps/ifs/warehouse-management/documentation/ifs-application-10/handling-unit-management/create-handling-unit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.