> 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/order-processing/purchase-order/po-configuration/item-display-order.md).

# Item Display Order

**YouTube:** [How to Configure Item Display Order in Edit Mode in Purchase Orders?](https://youtu.be/aHk7FFANYUs)

## How to Configure Item Display Order in Edit Mode in Purchase Orders?

This tutorial explains how to configure the **Item Display Order** in Purchase Orders in Logic ERP. This feature allows you to control how items are arranged—alphabetically, company-wise, by code, or in entry sequence—making it easier to review and manage orders.

***

### **Objective of This Feature**

* Customize how items are displayed in Purchase Orders
* Improve readability and organization of item lists
* Enable sorting based on business preference
* Enhance efficiency during order review

***

#### **Access to the Purchase Order Configuration**

* Go to **Purchase Order Module**
* Open **Configuration Window**
* Navigate to **Other Settings**
* Locate the option labeled as:

> **“Item Display Order”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fnb2nNl9ZanwAgZWwvsVm%2FCNF.png?alt=media&amp;token=7354ee59-ef1b-4bb2-ad11-935211f9239a" alt=""><figcaption></figcaption></figure>

* Click **OK** to apply changes.

**Default Setting**

* **Item Name:** Items are displayed in **Alphabetical Order.**

***

### **Item Display Order as: Item Name (Default Behavior)**

* Create a **New Purchase Order**
* Enter **Supplier Name**
* Add items in **random order**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fju1ILPAgKr595y01tmC8%2FPO%20-%20Default%20Behavior.png?alt=media&amp;token=feb74e53-5b38-4030-9a42-09d5cf7e28fd" alt=""><figcaption></figcaption></figure>

* Save the Purchase Order

**Result**

* When reopened in **Modify Mode**,
  * Items are arranged **alphabetically by Item Name**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F7VeHR7qvdIwo88HPkueG%2FArranged.png?alt=media&amp;token=91e482ce-ca4c-4287-b809-3203bd523343" alt=""><figcaption></figcaption></figure>

***

### **Item Display Order as: Set Company + Item Name**

* Go back to the **Purchase Order Configuration.**
* Change option to: **Company + Item Name**
* Click **Save**

**Result**

* **Items are:**
  * Grouped **Company-Wise**
  * Then sorted **alphabetically within each Company**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FYTeo1OCoebN43QtHsCFi%2FCompany%20%2B%20Item%20Wise.png?alt=media&amp;token=05a21b40-5a16-4501-ad93-39f4d8e3e80f" alt=""><figcaption></figcaption></figure>

***

### **Item Display Order as: Set Item Code**

* Go back to the **Purchase Order Configuration.**
* Select: **Item Code**
* Click **Save**

**Result**

* Items are Sorted:
  * **Numerically** (for numeric codes)
  * **Alphabetically** (for alphanumeric codes)

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FHZ3NJLtnLPFTwNbh4LjR%2FItem%20Code.png?alt=media&amp;token=cda4cdb8-7945-4ad9-b30b-074c0de5e00d" alt=""><figcaption></figcaption></figure>

***

### **Item Display Order as: Set Serial Number**

* Go back to the **Purchase Order Configuration.**
* Select: **Serial Number**
* Click **Save**

**Result**

* Items are displayed in the **exact order of entry**
* Maintains original transaction sequence

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F9VD3fwwlpXIRiFPOLhfl%2FSerial%20No.png?alt=media&amp;token=99b80c3f-129a-4e69-9656-8d6afcc9d710" alt=""><figcaption></figcaption></figure>

***

### **Key Benefits**

* Flexible item sorting options
* Better visibility and organization
* Easier review and verification
* Improved user experience

***

### **Best Practice Tips**

* Use **Item Name** for simple alphabetical sorting
* Use **Company + Item Name** for multi-brand businesses
* Use **Serial Number** to maintain entry sequence
* Choose based on operational requirements

***

### **Final Outcome**

* Items are displayed as per selected configuration
* Purchase Orders become more structured and readable
* Users can customize sorting as per business needs
* Overall efficiency and clarity are improved


---

# 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/order-processing/purchase-order/po-configuration/item-display-order.md?ask=<question>&goal=<user_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.
