> 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/delivery-note-against-purchase-orders/dn-against-po-configuration/do-not-allow-saving-if-the-scanned-quantity-is-below-the-defined-percentage..md).
# Do Not Allow Saving if the Scanned Quantity Is Below the Defined Percentage.
**YouTube:** [How to Restrict Quantity Scanning Below the Defined Percentage in Delivery Notes?](https://youtu.be/DA-qOAQ0DvA)
## How to Restrict Quantity Scanning Below the Defined Percentage in Delivery Notes?
In this tutorial, we will learn how to configure the **minimum quantity percentage** required to save a Delivery Note in Logic ERP. This validation ensures that the entered delivery quantity does not fall below a user-defined percentage of the actual Purchase Order quantity.
***
### Objective of This Feature
* Enforce a minimum delivery quantity.
* Prevent partial deliveries below the defined limit.
* Improve delivery accuracy.
* Ensure compliance with business delivery policies.
* Reduce incomplete or insufficient deliveries.
***
### Open Delivery Note Configuration
* Open the **Delivery Note Configuration** window.
* Navigate to the **Other Settings** section.
* Locate the option labeled as:
> **"Do Not Allow Saving if Qty Percentage is less than \_\_\_\_\_\_\_\_\_ Of Actual Quantity."**
* Enter the required minimum quantity percentage.
* For this demonstration, set the value to **50%**.
* Save the configuration.
***
### Create a New Delivery Note
* Initiate a **New Delivery Note** entry.
* Select the **Supplier**.
* Enter the required header details.
* Click **Next**.
**Retrieve the Purchase Order**
* Select the **Purchase Order** option.
* Search for and select the required Purchase Order.
* Retrieve the items.
* Click **Refresh**.
**Validate the Minimum Quantity**
* Enter or scan a quantity that is **less than 50%** of the actual Purchase Order quantity.
* Click **Save**.
**Result**
* The software restricts the transaction and displays an error message indicating that the Delivery Note quantity cannot be less than **50%** of the actual Purchase Order quantity.
***
### Meet the Minimum Quantity Requirement
* Increase the scanned quantity so that it meets or exceeds the configured **50%** minimum.
* Click **Save** again.
**Result**
The validation is successfully fulfilled, and the software allows the Delivery Note to be saved.
***
### Key Benefits
* Enforces minimum delivery quantity policies.
* Prevents incomplete deliveries below the defined threshold.
* Improves delivery accuracy.
* Reduces manual verification.
* Ensures consistency in delivery processing.
***
### Best Practice Tips
* Configure the minimum percentage according to your organization's delivery policy.
* Use this feature to avoid creating Delivery Notes with insignificant quantities.
* Verify retrieved Purchase Order quantities before processing deliveries.
* Review the configured percentage periodically to align with operational requirements.
***
### Final Outcome
The **Minimum Quantity Percentage** validation ensures that a Delivery Note can only be saved when the entered quantity meets or exceeds the user-defined percentage of the actual Purchase Order quantity. This helps maintain delivery standards, improves operational efficiency, and ensures accurate fulfillment of Purchase Orders.
---
# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/delivery-note-against-purchase-orders/dn-against-po-configuration/do-not-allow-saving-if-the-scanned-quantity-is-below-the-defined-percentage..md?ask=&goal=
```
`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.