> ## Documentation Index
> Fetch the complete documentation index at: https://help.kwentra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create One Purchase Order from Multiple Purchase Requests

> Select several purchase requests on the list and generate purchase orders from their combined line items in one action, grouped by vendor.

Select several purchase requests on the list and generate purchase orders from their combined items in one action, grouped by vendor.

<video autoPlay muted playsInline controls className="w-full rounded-md" src="https://mintcdn.com/kwentra/aUoEl3saIwG2e0F2/images/back-office/purchasing/create-po-from-multiple-purchase-requests/create-po-from-multiple-purchase-requests-walkthrough.mp4?fit=max&auto=format&n=aUoEl3saIwG2e0F2&q=85&s=a0c8b9ced013e0d801d82902c8c8e981" data-path="images/back-office/purchasing/create-po-from-multiple-purchase-requests/create-po-from-multiple-purchase-requests-walkthrough.mp4" />

### **Business Value**

* Combine line items from several purchase requests into one order per vendor.
* Speeds up buying by ordering across requests in a single action.
* Reduces duplicate purchase orders for the same vendor.
* Adjust price and quantity per line before the orders are created.
* Restricts the bulk action to users with the create-purchase-order permission.

### **Use Cases**

* Buyer selects two requests that share a vendor and creates one combined purchase order.
* Purchasing manager pools the week's requests and orders each vendor's items together.
* Cost controller reviews the source request of each line before confirming the orders.

### **How It Works**

| **Where:** Back Office → Purchasing → Purchase Requests |
| ------------------------------------------------------- |

Previously a purchase order could be built from only one purchase request at a time. You can now select several requests from the list and create purchase orders from their combined line items — producing one order per vendor.

1. On the Purchase Requests list, tick the checkbox next to each request you want to order from.
2. Open **Bulk Actions** and choose **Create PO**. This action is available to users with the create-purchase-order permission.
3. A popup opens showing the orderable lines from **all** selected requests, pooled and grouped under **vendor headers**. Each line shows Item, Store, Unit, Unit price, Qty, and a **Request** column showing which purchase request it came from.
4. Tick the lines you want to order and adjust the **price** or **quantity** per line as needed.
5. Click confirm. The system creates **one purchase order per vendor**. If the selected lines come from different vendors, the system automatically creates a separate purchase order for each vendor.
6. The created purchase orders are shown on success. Each order's description lists its source requests — for example, "From purchase requests no. 12, 15, 18".

The status of every source purchase request is updated to reflect how much of it has been ordered (partially or fully).

#### **What You Can Combine**

Requests are grouped on two levels, and every request you select must match on both:

* **Same usage department** — all selected requests must belong to the same [usage department](/back-office/purchasing/usage-department-field-in-purchase-orders). You cannot create one purchase order across different usage departments.
* **Same market list setting** — you cannot mix [market list](/back-office/purchasing/purchasing-market-list) requests and non–market list requests in the same action.

If the selected requests do not match on both levels, the action is blocked and this message appears:

| Selected purchase requests have different usage department or market list and can't be combined into one purchase order. |
| ------------------------------------------------------------------------------------------------------------------------ |

#### **Which Lines Appear**

A line appears in the popup only when it is **approved**, **not rejected**, has a **vendor assigned**, and still has **remaining quantity** to order. Lines that do not meet these conditions are hidden automatically.

Each request must have at least **one approved item** to be ordered from. A request that is still in **Draft** — or that has no orderable items — cannot be used. Selecting one shows this message with the request number:

| Purchase request(s) have no items available to order: 54. Remove them from the selection to continue. |
| ----------------------------------------------------------------------------------------------------- |

#### **Direct Receiving and Stocked Items**

If a request mixes [direct receiving](/back-office/purchasing/direct-receiving) items with regular stocked items, the system separates them so each type is ordered and handled correctly.