> 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-library-wms/delivery-confirmation-of-customer-order.md).
# Delivery Confirmation of Customer Order
## Steps
### Select Delivery Note
* Delivery Note No is mandatory and validated with the connected Customer Order(s).
### Select Customer Order
{% hint style="info" %}
Only visible if the delivery note entered in the previous step is connected to multiple customer orders.
{% endhint %}
### Sign the Confirmation
* Signature is required
* Click on the **Save** button to confirm the delivery. This will also make sure that the Signature entered is attached as a media item to the *DeliveryNote* Logical Unit
* Once saved, the corresponding entries in the Delivery Confirmation of Customer Orders screen in IFS Cloud should be removed.
* You can view this signature as an attachment in the Customer Order Delivery Note Analysis screen in IFS Cloud.
### Companion Application
To test the functionality, run the Manual Test of Delivery Confirmation of Customer Order Cloud companion application. A site must be selected from the dropdown list. Optionally, you can enter a Delivery Note Number and Order Number before clicking Start.
## Pre-Validation Checks
* The Confirm Deliveries flag needs to be set to true under the Delivery Confirmation header in the Order Details tab of a customer order.
* A customer order that is initially in the Planned state must be released, reserved, have its pick list created and reported, and reach the Delivered state before this component can be used.
* The Delivery Confirmation of Customer Orders screen should show a line(s) that are connected to their Customer Order(s).
---
# 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-library-wms/delivery-confirmation-of-customer-order.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.
