> 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/inventory/physical-stock-verification-of-puv/physical-stock-verification-of-puv-configuration/do-not-allow-saving-if-physical-qty-scanning-_________-of-actual-qty-percent-is-less-than..md).
# Do Not Allow Saving if Physical Qty Scanning \_\_\_\_\_\_\_\_\_ Of Actual Qty Percent is less than.
**YouTube:** [How to Enforce a Minimum Physical Quantity Scan Percentage in Physical Stock Verification (PUV)?](https://www.youtube.com/watch?v=UkwjlWoGRBc)
## How to Enforce a Minimum Physical Quantity Scan Percentage in Physical Stock Verification (PUV)?
In this tutorial, we will learn how to set a minimum physical stock scanning percentage required before saving a Physical Stock Verification of a Purchase Voucher in Logic ERP.
***
### Objective of This Feature
* Define a minimum scanning percentage before saving.
* Ensure sufficient physical stock is verified.
* Prevent saving when the scanned quantity is below the defined threshold.
* Improve accuracy in physical stock verification.
***
### Access to the Physical Stock Verification Configuration
* Go to the **Physical Stock Verification of Purchase Voucher** module.
* Open the **Configuration** window.
* Locate the option labeled as:
> **"Do Not Allow Saving if Physical Qty Scanning \_\_\_\_\_\_\_\_\_ Of Actual Qty Percent is less than."**
This option allows you to define the minimum percentage of the total voucher quantity that must be physically scanned before the document can be saved.
**Example**
Let's set the minimum scanning percentage to **80%**.
* Voucher Quantity: **300 Units**
* Minimum Scanning Percentage: **80%**
* Minimum Required Scanned Quantity: **240 Units**
Therefore, the document can only be saved when at least **240 units** have been physically scanned.
***
### Select the Voucher Type
* Select the required **Voucher Type**.
* Choose **Purchase Voucher** for Physical Stock Verification.
* The system will display the total quantity from the selected Purchase Voucher.
***
### Observe the Validation
* Now, enter or scan quantities, the total is less than the required 240 units.
For example:
* Total Voucher Quantity: **300 Units**
* Scanned Quantity: **230 Units**
* Required Quantity: **240 Units**
Now, try to save the document.
**Result**
The software restricts the saving process and displays an information message indicating that a minimum of **80% of the physical stock must be scanned** before the document can be saved.
***
### Complete the Required Scanning
* Now, enter or scan additional quantities until the total physical quantity reaches at least **240 units**.
**Result**
Once the scanned quantity reaches the configured **80% threshold**, the system allows the document to be saved successfully.
***
### Key Benefits
* Ensures minimum physical stock verification before saving.
* Prevents incomplete stock verification.
* Improves inventory accuracy.
* Provides better control over physical stock audits.
* Helps ensure compliance with defined verification requirements.
***
### Final Outcome
The **minimum physical stock scanning percentage** feature ensures that a predefined percentage of the Purchase Voucher quantity is physically scanned before the Physical Stock Verification document can be saved. In this example, with an **80% requirement on 300 units**, at least **240 units** must be scanned before saving is allowed.
---
# 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/inventory/physical-stock-verification-of-puv/physical-stock-verification-of-puv-configuration/do-not-allow-saving-if-physical-qty-scanning-_________-of-actual-qty-percent-is-less-than..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.