> 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/filter-sale-order-on-basis-of-sale-order-prefix.md).
# Filter Sale Order on basis of Sale Order Prefix
**YouTube:** [How to Filter Sales Orders by Sales Order Prefix in Packing Slips?](https://youtu.be/DqIUt6wfz-0)
## How to Filter Sales Orders by Sales Order Prefix in Packing Slips?
In this tutorial, we will learn how to filter **Sales Orders** based on their **Sales Order Prefix** while creating a Packing Slip in Logic ERP.
This feature allows users to select a specific Sales Order Prefix and view only the Sales Orders associated with that prefix during Sales Order selection.
***
### Enable Sales Order Prefix Filtering
* Open the **Packing Slip Configuration** window.
* Navigate to the **Other Options Four** section.
* Locate and enable the option labeled as:
> **"Filter Sale Order on basis of Sale Order Prefix"**
***
### Select Sales Order Prefixes
Now, let's define which Sales Order Prefixes should be available for filtering.
* Navigate to the **Other Options 3** section.
* Locate the available list of **Sales Order Prefixes**.
* Select the prefixes that you want to use for filtering Sales Orders.
* Once the required prefixes are selected, save the configuration changes.
***
### Filter Sales Orders by Prefix
Now, let's verify the functionality.
* Initiate a new **Packing Slip** entry.
* Select the required customer.
#### Sales Order Prefix
* As you can see, the **Sales Order Prefix** option is now available.
* The dropdown displays the prefixes selected in the configuration.
* Select the required prefix from the dropdown list.
* Click on **Sales Order Selection**.
#### System Behavior
* The Sales Order search list now displays only those Sales Orders that belong to the selected prefix.
* Sales Orders with other prefixes are excluded from the selection list.
***
### Filter Using Another Prefix
* Select another configured **Sales Order Prefix** from the dropdown.
* Click on **Sales Order Selection** again.
* The system updates the search list based on the newly selected prefix.
**Result**
The Sales Order list is filtered according to the selected prefix, allowing you to quickly locate and select the required Sales Order.
***
### Key Benefits
* Filters Sales Orders based on the selected prefix.
* Makes Sales Order selection faster and more organized.
* Prevents unrelated Sales Orders from appearing in the selection list.
* Allows multiple Sales Order Prefixes to be configured for filtering.
#### Final Outcome
By enabling **"Filter Sale Order on basis of Sale Order Prefix"** and selecting the required prefixes under **Other Options Three**, Logic ERP allows users to filter Sales Orders efficiently based on the selected **Sales Order Prefix** while creating a Packing Slip.
---
# 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/filter-sale-order-on-basis-of-sale-order-prefix.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.
