> 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/generate-new-sale-order-of-items-not-exists-in-selected-order.md).
# Generate New Sale Order of Items Not Exists in Selected Order
**YouTube:** [How to Scan Extra Items and Generate a New Sales Order in Packing Slips?](https://youtu.be/O_3PgO3aqZg)
## How to Scan Extra Items and Generate a New Sales Order in Packing Slips?
In this tutorial, we will learn how to allow the system to automatically generate a new **Sales Order** for items that are not included in the selected Sales Order while creating a **Packing Slip** entry.
This functionality allows users to add additional items during Packing Slip entry without being restricted by the items available in the selected Sales Order.
***
### Observe the Default Behavior
Let's first understand how the system works by default.
* Initiate a new **Packing Slip** entry.
* Select the required customer.
* Search for and select the **Sales Order** to be retrieved in the Packing Slip.
* Proceed to the **Item Details** section.
#### Default Behavior
* The selected Sales Order contains only one item.
* Now, scan an item that is not included in the selected Sales Order.
* As soon as you scan the item code, the system restricts the entry.
* An error message is displayed:
> Invalid Barcode.... Item does Not Exist In Sale Order.\
> Please check.
This occurs because the scanned item does not exist in the selected Sales Order.
***
### Enable New Sales Order Generation
To allow additional items to be entered, Logic ERP provides the **Generate New Sale Order of Items Not Exists in Selected Order** option.
* Open the **Packing Slip Configuration** window.
* Navigate to the **Other Options Four** section.
* Locate and enable the option labeled as:
> **"Generate New Sale Order of Items Not Exists in Selected Order"**
* Save the configuration changes.
***
### Add an Item Not Available in the Selected Sales Order
Now, let's verify the functionality.
* Initiate a new **Packing Slip** entry.
* Select the required customer.
* Select the required **Sales Order**.
* Proceed to the **Item Details** section.
* Scan the required quantity of the item included in the Sales Order.
* Now, scan another item that is **not included** in the selected Sales Order.
#### System Behavior
* The system now allows the additional item to be entered successfully.
* Instead of displaying an **Invalid Barcode** error, the system automatically handles the additional item by generating a new Sales Order.
***
### Verify the Newly Generated Sales Order
* Save the **Packing Slip** entry.
* Open the same Packing Slip in **Modify Mode**.
* Check the Sales Order details for the newly added item.
**Result**
As you can see, a new Sales Order, **SO79**, has been automatically generated for the item that was not available in the originally selected Sales Order.
***
### Key Benefits
* Allows additional items to be added during Packing Slip entry.
* Automatically generates a new Sales Order for items not available in the selected order.
* Eliminates the need to create a separate Sales Order manually.
* Provides greater flexibility during packing operations.
* Reduces interruptions caused by item validation restrictions.
#### Final Outcome
By enabling **"Generate New Sale Order of Items Not Exists in Selected Order"**, Logic ERP allows users to scan and add items that are not included in the selected Sales Order and automatically generates a new Sales Order for those additional items.
---
# 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/billing/packing-slip/packing-slip-configuration/generate-new-sale-order-of-items-not-exists-in-selected-order.md?ask=&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.
