> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/purchase/purchase-module/purchase-transactions/consolidated-po.md).
# Consolidated PO
A **Consolidated Purchase Order (PO)** is a single Purchase Order created by combining multiple purchase requisitions or item requests into one PO. This process helps organizations simplify procurement activities by reducing the number of individual Purchase Orders issued to vendors.
* The Consolidated PO feature is useful when multiple items or requests are being purchased from the same supplier.
## Steps to Create Consolidated PO
Step 1: Go to the **Purchase** main menu.
1. Click **Transaction**.
2. Select **Consolidated PO**.
* The Consolidated PO screen will appear.
Step 2: Click the **New** button.
1. Select the required **PO Type**.
2. Enter or select the **Vendor Details**.
Step 3: Click the **Add** button.
1. To select products, click the **Search Icon** available next to the item or product field.
* The product selection list will appear.
2. Choose the required items from the displayed product list.
* The selected products will be added to the Consolidated PO.
Step 4: Enter the required **Quantity** for each product.
1. Enter the applicable **Rate** or price.
* Verify the entered details carefully before saving.
Step 5: After entering all item details, click the **Save** button.
* The system will create the Consolidated Purchase Order successfully.
---
# 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://help.rbsgo.com/purchase/purchase-module/purchase-transactions/consolidated-po.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.
