> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/assign-stock-to-delivery-orders/assign-stock-to-delivery-orders-configuration/allow-saving-only-if-do-is-completely-scanned.md).

# Allow Saving only if DO is completely scanned

**YouTube:** [How to Allow Saving Delivery Orders Only After Complete Scanning?](https://youtu.be/TJOrIVLlp6c)

## How to Allow Saving Delivery Orders Only After Complete Scanning?

In this tutorial, we’ll learn how to use the **“Allow Saving only if DO is completely scanned”** feature in the **Assigned Stock to Delivery Order** window of Logic ERP. This feature prevents users from saving a voucher until all items in the selected delivery order have been scanned, helping ensure that the scanning process is completed before saving.

**Let’s get started!**

***

### Access to the Configuration

* Navigate to the **Order Processing** module.
* Open the **Assigned Stock to Delivery Order** window.
* Click to open the configuration window.
* Under **Other Options** locate and enable the option labeled as:

> **“Allow Saving only if DO is completely scanned”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F5qXb6UOgHxfSS5mprFPG%2FCNF.png?alt=media&amp;token=946e761e-ca30-4591-8cdf-969a6dc8ff20" alt=""><figcaption></figcaption></figure>

* Save the changes.

**The configuration is now enabled. Let’s verify how it works during delivery order scanning.**

***

### Select the Delivery Order and Start Scanning

* Return to the **Assigned Stock to Delivery Order** window.
* Search for and select the required delivery order.
* Enter the packing box number.
* Start scanning the item codes associated with the delivery order.
* Leave some items unscanned to test whether the system allows the voucher to be saved.

**Now, let’s try saving the voucher before scanning all the items.**

***

### Verify Saving When Items Are Still Unscanned

* Click **Save** while some items in the delivery order remain unscanned.
* The system prevents the voucher from being saved.
* An error message appears:&#x20;

> **“Delivery order should be completely scanned. There is some Quantaty Pending. Cannot allow saving.**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FPbbDgunZZqNRiz8SlHpz%2FPrompt.png?alt=media&amp;token=901439b4-6e45-49e4-a95e-484b5280ccd4" alt=""><figcaption></figcaption></figure>

* This restriction ensures that the voucher cannot be saved until all items in the delivery order have been scanned.

**This confirms that the system blocks saving whenever any items remain unscanned.**

***

### Complete Scanning and Save the Voucher

* Continue scanning the remaining item codes.
* Ensure that all items in the selected delivery order have been scanned.
* Click **Save** again.
* The system now allows the voucher to be saved successfully.

**This confirms that the voucher can be saved once the entire delivery order has been scanned.**

***

### Conclusion / Result

* **Feature Enabled:** The system prevents saving if any items in the delivery order remain unscanned.
* **Incomplete Scanning:** An error message appears, and the voucher cannot be saved.
* **Complete Scanning:** Once all items have been scanned, the system allows the voucher to be saved successfully.
* **Key Benefit:** This feature helps ensure that all items in a delivery order are scanned before the voucher is saved, reducing the risk of incomplete scanning.

**By enabling this feature, users can ensure that delivery order scanning is completed before saving the voucher in Logic ERP.**


---

# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/assign-stock-to-delivery-orders/assign-stock-to-delivery-orders-configuration/allow-saving-only-if-do-is-completely-scanned.md?ask=<question>&goal=<user_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.
