> 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/billing/packing-slip/packing-slip-configuration/do-not-allow-entry-w-o-sales-order.md).
# Do Not Allow Entry W/O Sales Order
**YouTube:** [How to Prevent Packing Slip Entry Without a Sales Order?](https://youtu.be/l9MTajDy2uw)
## How to Prevent Packing Slip Entry Without a Sales Order?
In this tutorial, we will learn how to use the **"Do Not Allow Entry W/O Sales Order"** option in Logic ERP to ensure that a Packing Slip cannot be created without selecting a Sales Order.
***
### Objective of This Feature
* Make Sales Order selection mandatory
* Prevent Packing Slip entry without a Sales Order
* Ensure proper order-based delivery processing
* Avoid manual item allocation without an order
* Improve transaction control and accuracy
***
### Observe the Default Behavior
* Initiate a **New Packing Slip** entry.
* Select the required customer.
* Do not select any Sales Order.
* Proceed to the **Item Details** section.
* Manually scan the required items.
**Result**
By default, the software allows you to complete and save the Packing Slip **without selecting a Sales Order**.
***
### Access to the Packing Slip Configuration
* Open the **Packing Slip Configuration** window.
* Navigate to the **Other Options 2** section.
* Locate and enable the option labeled as:
> **"Do Not Allow Entry W/O Sales Order"**
* Save the configuration changes.
***
### Implement the Restriction
* Initiate a **New Packing Slip** entry.
* Select the required customer.
* Do not select a Sales Order.
* Try to proceed with the entry.
**Result**
* The software restricts the transaction and displays the message:
> **"Please select sales order to continue."**
This means the Packing Slip cannot be processed until a Sales Order is selected.
***
### Select the Required Sales Order
* Go to the **Header Details** section.
* Select the required **Sales Order**.
* Proceed with the Packing Slip entry.
* Complete the required item details.
**Result**
Once the Sales Order is selected, the software allows you to continue with the Packing Slip entry successfully.
***
### Key Benefits
* **Mandatory Order Reference:** Ensures every Packing Slip is linked to a Sales Order.
* **Better Control:** Prevents unauthorized delivery processing.
* **Improved Accuracy:** Reduces the possibility of creating deliveries without an order.
* **Order Traceability:** Makes it easier to track deliveries against Sales Orders.
* **Streamlined Processing:** Ensures proper order-based packing and delivery.
***
### Important Note
When **"Do Not Allow Entry W/O Sales Order"** is enabled, selecting a Sales Order becomes mandatory before continuing with the Packing Slip entry.
***
### Final Outcome
After enabling **"Do Not Allow Entry W/O Sales Order"**, Logic ERP prevents users from creating a Packing Slip without a Sales Order. Once the required Sales Order is selected, the user can proceed with the transaction successfully.
---
# 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/billing/packing-slip/packing-slip-configuration/do-not-allow-entry-w-o-sales-order.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.
