> 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/reports-queries/item-report/barcode-labels-printing/barcode-labels-printing-configuration/un-assigned-delivery-order-only-for-barcode-printing.md).
# Un-Assigned Delivery Order Only For Barcode Printing
**YouTube:** [How to Allow Unassigned Delivery Orders in Barcode Label Printing?](https://youtu.be/rLs1h_pr38c)
## How to Allow Unassigned Delivery Orders in Barcode Label Printing?
In this tutorial, we will learn how to configure Logic ERP to **print barcode labels specifically for un-assigned Delivery Orders**. This feature allows users to identify and print barcode labels for Delivery Orders that still contain un-assigned quantities.
***
### Review the Default Behavior
* Navigate to the **Barcode Label Printing** module.
* Open the **Configuration** section.
* Locate the option labeled as:
> **"Un-Assigned Delivery Order Only For Barcode Printing"**
* Keep this option **disabled** for now.
***
### Check the Assigned and Un-Assigned Quantities
* Navigate to the **Reserve Stock Against Sale Orders** module.
* Open the relevant **Sales Order**.
**Current Status**
* Stock has already been reserved against the Sales Order.
* The **Small** and **Medium** pack sizes have assigned quantities.
* The **Large** pack size remains **un-assigned/pending**.
***
### Generate the Delivery Order
* Generate a **Delivery Order** against the relevant Sales Order.
* Select the required **Sales Order**.
* Select the **Party Name**.
* Generate the Delivery Order.
* In this example, the generated Delivery Order number is **7.**
* Double-click the Delivery Order field to select the generated Delivery Order.
* Save the document.
***
### Verify Barcode Printing with the Option Disabled
* Return to the **Barcode Label Printing** window.
* Select **Delivery Order** as the document type.
* Check the available Delivery Orders.
**Result**
Since **"Un-Assigned Delivery Order Only For Barcode Printing"** is disabled, the system displays only Delivery Orders with **fully assigned quantities**.
Therefore, **Delivery Order No. 7**, which contains an un-assigned quantity, is **not displayed** in the list.
***
### Enable Un-Assigned Delivery Order Printing
* Return to the **Barcode Label Printing Configuration** window.
* Enable **"Un-Assigned Delivery Order Only For Barcode Printing"**.
* Save the configuration changes.
***
### Verify the Updated Behavior
* Return to the **Barcode Label Printing** window.
* Select **Delivery Order**.
* Check the available Delivery Orders.
**Result**
After enabling the option, the system displays **only Delivery Orders containing un-assigned quantities**.
As a result, **Delivery Order No. 7** is now displayed in the list.
* Select the required Delivery Order.
* Proceed with printing the barcode labels.
***
### Key Benefits
* **Focused Printing:** Displays only Delivery Orders with un-assigned quantities.
* **Better Visibility:** Makes pending quantities easier to identify.
* **Efficient Processing:** Helps users quickly process un-assigned Delivery Orders.
* **Improved Workflow:** Simplifies barcode printing for partially assigned orders.
#### Final Outcome
After enabling **"Un-Assigned Delivery Order Only For Barcode Printing"**, Logic ERP displays only Delivery Orders containing **un-assigned quantities** in the Barcode Label Printing window, allowing users to select and print their barcode labels efficiently.
---
# 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/reports-queries/item-report/barcode-labels-printing/barcode-labels-printing-configuration/un-assigned-delivery-order-only-for-barcode-printing.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.
