> 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/smart-purchase-order-planner.md).

# Smart Purchase Order Planner

## Plan purchase orders for many branches in one go

The **Smart Purchase Order Planner** works out what each branch needs to order, recommends the best **supplier** for every item from your purchase history and supplier quotations, and creates **one purchase order per branch and supplier**. You can review every line, change quantities and suppliers, see the orders exactly as they will be saved, and choose which ones to create.

***

### **Step 1: Open the planner**

* Navigate to **Order Processing** and open **Smart Purchase Order Planner**.
* Pick a saved configuration in the list at the top. The configuration decides how quantities are worked out and how suppliers are ranked.
* To create or change a configuration, click **Configuration** (to the left of the list). You need rights to change configurations. Every setting is explained in [**Smart Purchase Order Planner - Configuration**](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/smart-purchase-order-planner/smart-purchase-order-planner-configuration.md).

***

### **Step 2: Choose what to plan**

* **Branches...** picks the branches to plan for. It is available when the configuration allows any branch; otherwise the planner works for the branch you are logged in to.
* **Groups...** and **Companies...** limit the items to some item groups or companies. Leave them empty for all items.
* **Supplier...** limits the plan to the items one supplier can be ordered for.
* The line under the buttons shows what is chosen, for example *Branches: CHD BRANCH | Groups: All | Companies: All | Supplier: All | As on: 15/10/2026*.

***

### **Step 3: Click Suggest**

* The upper grid lists one line per **branch and item**: stock, levels, what is already on order, sales, the **Suggested Qty**, the **Order Qty** and the recommended **Supplier** with its **Rate** and **Margin %**.
* The lower grid lists the **suppliers** of the selected line, best first, with their rate, where the rate comes from, last purchase, number of purchases, lead days and margin.
* The status line at the bottom shows the number of lines, how many will be ordered, their value and how many are flagged.

**Line colours**

* **Green** - will be ordered from the recommended supplier.
* **Orange** - will be ordered from another supplier you chose.
* **Light red** - selected with a quantity, but cannot be ordered (no supplier or no rate).
* **White** - not selected, or no quantity.
* **Light yellow** Override Reason - you changed the supplier and have not typed a reason yet.
* **Flags** in red are warnings, for example **LOW MARGIN**, **LOW MARGIN, NONE RECOMMENDED**, **NO SELLING PRICE**, **RATE UP 12%** (the rate is more than the set percentage - 10% unless changed - above this branch's last purchase rate of the item), **NO SALE**, **NO RATE** or **NO SUPPLIER**.
* On the desktop, the legend between the two grids explains the colours.

***

### **Step 4: Review the lines**

* **Select** - Yes or No decides whether the line is ordered.
* **Order Qty** - type a different quantity if needed. Typing a quantity sets Select to Yes; typing 0 sets it to No.
* **Filter** - type part of an item code, item name, pack, branch, the line's chosen supplier or a flag to see only the matching lines. On the web, press Enter to apply it.
* **Show** - **All lines**, or only the lines **To order**, **Flagged**, **Cannot order**, **Other supplier chosen** or **Reason needed**. **Clear** shows all lines again.
* **Select All** / **Unselect All** - set Select on every line the filter shows, for example *Show: Flagged* and then *Unselect All*.
* The filter is only for viewing - **Generate POs** always uses every selected line, shown or not.

***

### **Step 5: Choose another supplier**

* Select a line, then in the suppliers grid press **Enter** or double-click a supplier (double tap on a phone). A supplier with no rate cannot be chosen.
* The line takes that supplier and rate. When it is not the recommended supplier, the line turns orange - type the reason in **Override Reason**. The reason is kept with the order run; it is not compulsory.
* With **Sales cover**, the suggested quantity may change, because it depends on the supplier's delivery time. A quantity you typed yourself is kept.

> **Example - changing a supplier**
>
> CHD BRANCH needs 10 of PRICE LIST ITEM 2. The planner recommends Supplier A at ₹46 (lowest rate). Supplier B at ₹52 delivers in 2 days instead of 4, so Ravi double-clicks Supplier B. The line turns orange and Ravi types "urgent - faster delivery" as the reason. The order for Supplier B now includes this item at ₹52. With order levels the quantity stays 10; with sales cover it is worked out again for Supplier B's shorter delivery time.

***

### **Step 6: Generate the purchase orders**

* Choose the [**PO Configuration**](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/purchase-order/po-configuration.md) at the bottom, next to **Generate POs**. It starts on the configuration set in the planner's settings, or is left empty if you may not use that one.
* Click **Generate POs**. The **Purchase Order Preview** opens: one row per order (branch, supplier, provisional order number, delivery date, items, amounts, each tax and charge, order total) and, below it, the items of the selected order.
* Selected lines with no supplier or rate are left out of the preview; the status line says how many.
* Nothing is saved yet. Set **CREATE** to No (or press Space on the row) for any order you do not want now. **Select All** and **Unselect All** set it on every order that can be created. **Close** or Esc cancels.
* Orders set to Yes are **green**; orders set to No are white with no order number; orders that cannot be created are **light red** with the reason in **Note**. **Below minimum order value** in Note is a warning only.
* Order numbers are counted only for the orders set to Yes, branch by branch, so leaving one out moves up the later orders of the same branch. The final number is taken when the order is saved.
* Click **Create POs** (available once at least one order is set to Yes). Each order is saved on its own. The result list shows each order created and its number, and any order that could not be created with the reason. Lines that went into an order leave the planner; the other lines stay, ready for later.

***

### **Step 7: Let branches use only their own configurations**

* Users allowed to change the planner's configuration can click **Config Branches...** and tick the branches that may use the selected configuration. Untick every branch to let all branches use it. Click **OK** to save; a message confirms which branches can now use it.
* Users at a branch then see only the configurations allowed for their login branch. Users with rights to all branches see every configuration.
* A configuration limited to some branches shows them on the line under the buttons, for example *Config for: CHD BRANCH, DELHI BRANCH*, and **Branches...** offers only those branches. If your login branch is not one of them, the planner starts on the first allowed branch.

***

### **On the web and on a phone**

* **Hide header** (top right) folds away the buttons and filters so the grids get more room; **Show header** brings them back. The browser remembers the choice.
* **Hide suppliers** gives the lines the full height on a wide screen; **Show suppliers** brings the suppliers grid back.
* On a phone, switch between **Lines** and **Suppliers** with the two buttons above the grid.

***

### **Messages you may see**

* **No configuration is allowed for this branch - ask your administrator.** - every configuration is limited to other branches.
* **Purchase orders have been entered for these items since Suggest. Click Suggest again before creating orders.** - someone ordered the same items after you clicked Suggest. It is checked only when the configuration deducts pending purchase orders, and lists each branch and item with the quantity on order then and now.
* **No line is ready to order. A line needs Select = Yes, an order quantity and a supplier with a rate.**
* **Nothing to order - click Suggest first.**
* **Select the PO Configuration (next to Generate POs) first.**
* **Create a configuration first (Configuration).**
* **You do not have rights to change the settings.**
* **This supplier has no rate, so it cannot be ordered from here.**
* **Tick at least one order to create.** - in the preview.
* **The Purchase Order Configuration chosen does not exist any more - choose another one.**

**Available on:** Desktop · Web


---

# 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/smart-purchase-order-planner.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.
