> 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/delete-handling-unit.md).

# Delete Handling Unit

## Overview

This flow (app) can be used to delete a handling unit which either connected or not connected to a shipment provided the handling unit does not have any inventory connected.

![](/files/M37q7hwUPAa4fDtZZnJy)

*The complete overview of the flow:*

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

## Steps

### Enter Shipment ID

* Shipment ID is not mandatory. Any shipment belonging to the user default Site can be entered
* Click on the **List** button to see a list of shipments connected to the user default site

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

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

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

### Enter Handling Unit ID

* Enter the Handling Unit ID to be deleted
* If the Shipment ID is entered in the previous step, handling unit Shipment ID should match the same
* Entered Handling Unit ID should not have any stocks connected
* Click on the **List** button to see a list of Handling Units that satisfy the above conditions

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

### Summary

* The confirmation screen before the delete shows a summary of the Handling Unit chosen to be deleted

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

### Delete Child Handling Units

* If the handling unit has Child Handling Units in its structure, the user will be given the option to delete Child Handling Units as well
* The user can select either Yes or No

{% hint style="warning" %}
Deleting a handling unit can cause changes to the handling unit structure. Therefore, it is important to reprint documents and labels to ensure correct documents and labels that include information based on the changed structure.
{% endhint %}

{% hint style="info" %}
The example shown here (Flow Classic) Handling Unit ID 288 has a child node with ID 289
{% endhint %}

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


---

# 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/delete-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.
