> 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/skip-un-approved-po-from-barcode-printing.md).
# Skip Un-Approved PO From Barcode Printing
**YouTube:** [How to Skip Unapproved Purchase Orders in Barcode Label Printing?](https://youtu.be/jE-DpEQtwlc)
## How to Skip Unapproved Purchase Orders in Barcode Label Printing?
In this tutorial, we will learn how to **skip un-approved Purchase Orders from barcode printing** in Logic ERP. This feature ensures that barcode labels can only be printed for Purchase Orders that have been approved.
***
### Configure Barcode Printing
* Navigate to the **Barcode Label Printing** module.
* Open the **Configuration** section.
* Locate and enable the option labeled as:
> **"Skip Un-Approved PO From Barcode Printing"**
* Save the configuration changes.
***
### Check the Purchase Order Approval Status
* Navigate to **My Messages**.
* Locate the required Purchase Order.
* In this example, **Purchase Order No. 93** is currently **pending for approval**.
**Status**
The Purchase Order has not yet been approved, so let's verify whether it is available for barcode printing.
***
### Verify Barcode Printing for an Un-Approved PO
* Return to the **Barcode Label Printing** module.
* Select **Purchase Order** as the document type.
* Search for or select **Purchase Order No. 93**.
**Result**
* Since **Purchase Order No. 93 is still pending for approval**, it does **not appear in the Purchase Order list**.
* This prevents users from generating barcode labels for an un-approved Purchase Order.
***
### Approve the Purchase Order
* Return to the Purchase Order.
* Approve **Purchase Order No. 93**.
* Once approved, return to the **Barcode Label Printing** module.
* Select **Purchase Order** and check the list again.
**Result**
After the Purchase Order is approved, **Purchase Order No. 93 is now displayed in the list**, and you can proceed with printing its barcode labels.
***
### Key Benefits
* **Approval-Based Printing:** Prevents barcode printing for un-approved Purchase Orders.
* **Better Process Control:** Ensures only approved orders proceed for barcode generation.
* **Reduced Errors:** Avoids printing labels for orders that may still require changes.
* **Improved Workflow:** Aligns barcode printing with the Purchase Order approval process.
#### Final Outcome
After enabling **"Skip Un-Approved PO From Barcode Printing"**, Logic ERP automatically excludes pending Purchase Orders from the barcode printing list. Once a Purchase Order is approved, it becomes available for barcode label printing.
---
# 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/skip-un-approved-po-from-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.
