> 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-entry-without-box-number.md).
# Do Not Allow Entry Without Box Number
**YouTube:** [How to Make Box Number Entry Mandatory in Delivery Notes?](https://youtu.be/L8cIOsvMbaE)
## How to Make Box Number Entry Mandatory in Delivery Notes?
In this tutorial, we will learn how to restrict Delivery Note entries unless a **Packing Box Number** is assigned. This feature ensures that every scanned item is linked to a valid packing box, improving packing accuracy and shipment traceability.
***
### Objective of This Feature
* Make Packing Box Number mandatory during Delivery Note entry.
* Ensure every scanned item is assigned to a packing box.
* Improve packing accuracy and inventory tracking.
* Prevent incomplete packing transactions.
* Simplify shipment management and box-wise allocation.
***
### Let's enable the Configuration
* Open the **Delivery Note Configuration** window.
* Navigate to the **Other Settings** section.
* Locate and enable the option labeled as:
> **"Do Not Allow Entry Without Box Number"**
* Save the configuration.
***
### Create a New Delivery Note
* Initiate a **New Delivery Note**.
* Select the Supplier.
* Click **Next**.
* Search for and select the required Purchase Order.
* Click **Refresh** to retrieve the items.
**Result**
The **Box Number** field is now enabled and ready for entry.
***
### Observe the Restriction
* Skip the **Box Number** field.
* Try scanning an Item Code directly.
**Result**
The software immediately restricts the transaction and displays an error message indicating that the **Packing Box Number cannot be left blank**.
This ensures that every scanned item is linked to a valid packing box before processing.
***
### Assign Packing Box Numbers
* Enter or scan the **Packing Box Number**.
* Begin scanning the Item Codes.
**Result**
Each scanned item is automatically allocated to the specified packing box.
Repeat the same process for all remaining boxes:
* Scan the Packing Box Number.
* Scan the corresponding Item Codes.
* Continue until all items have been assigned to their respective packing boxes.
***
### Create and Manage Packing Boxes
To create new packing boxes:
* Go to the **Setup Module** from the Main Menu.
* Under **Set Other Item Details**, open **Setup Packing Box Master**.
**Define the following details:**
* Box Prefix
* Box Type
* Box Dimensions
**After entering the required information:**
* Click **Generate Boxes**.
* Select the required Box Name.
* Specify the number of boxes to generate.
* Click **Generate Boxes**.
Finally, click **Refresh** to view the newly generated Packing Boxes, which are now available for use during Delivery Note entry.
***
### Key Benefits
* Makes Packing Box Number mandatory.
* Ensures every item is assigned to a valid packing box.
* Improves packing accuracy and shipment tracking.
* Prevents incomplete packing records.
* Simplifies box-wise inventory management.
***
### Best Practice Tips
* Generate Packing Boxes before creating Delivery Notes.
* Always scan the Packing Box Number before scanning Item Codes.
* Verify box assignments before saving the document.
* Use meaningful box prefixes and dimensions for easier identification and warehouse management.
***
### Final Outcome
After enabling **Do Not Allow Entry Without Box Number**, Logic ERP requires a valid Packing Box Number before any item can be scanned during Delivery Note entry. This ensures accurate box-wise item allocation, improves shipment traceability, and streamlines the packing process.
---
# 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-entry-without-box-number.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.