> 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-apps/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. ![](https://3218748546-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MiW42YxFsGXIDjQJKNR%2Fuploads%2FTKPwKdWdX6BbSHQoTSsm%2FDelete%20Handling%20Unit_wf.png?alt=media\&token=3752d5e9-5c39-4acf-a350-e5f270eb3ffc) *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 %} | | | | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | | 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 | | | | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | | Flow Connect | Flow Classic | ### Summary * The confirmation screen before the delete shows a summary of the Handling Unit chosen to be deleted | | | | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | | 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 %} | | | | :-: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | | | 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.novacura.com/marketplace-documentation/applications/explore-apps/ifs/warehouse-management/documentation-apps/ifs-application-10/handling-unit-management/delete-handling-unit.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.