> 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/show-sale-for-last-no-of-days.md).

# Show Sale for Last No of Days

**YouTube:** [How to Show Sales for the Last Defined Number of Days in Purchase Orders?](https://youtu.be/LOaJzviteR8)

## How to Show Sales for the Last Defined Number of Days in Purchase Orders?

This tutorial explains how to **display Sales Quantity for the last defined number of days** directly in the Purchase Order screen in Logic ERP. This feature helps users make **data-driven purchasing decisions** by showing recent sales trends during order creation.

***

### **Objective of This Feature**

* View **recent sales quantity** while creating Purchase Orders
* Improve **purchase planning based on demand**
* Reduce **overstocking and understocking**
* Enable **quick decision-making**

***

### Access to the Configuration

* Open **Configuration Window**
* Navigate to **General Options**
* Locate and enable the option labeled as:

> **“Show Sale for Last No. of Days”**

**Define Sale Days**

* Enter the number of days (e.g., **15 days**)

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FXb6PmUEvypJBBZ9BmQcj%2FCNF.png?alt=media&amp;token=d0e4ddb9-601d-4672-bc22-283831f3408a" alt=""><figcaption></figcaption></figure>

* This defines:
  * Sales data period to be displayed in Purchase Order
* Click **OK** to apply changes

***

### **Add Sales Quantity Column**

* Open **Purchase Order Window**
* Go to **Column Attributes**
* Select and enable:
  * **Sale Quantity (Packs)**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FFQFQRd6RWKrjKUo82XIP%2FColumn%20Lock.png?alt=media&amp;token=8916e6dd-3ff3-4276-91b7-b07d3f5f7dc2" alt=""><figcaption></figcaption></figure>

***

### **Implement Purchase Order**

* Start a **New Purchase Order**
* Enter item details

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FroM5UuxFdJu7e6QsyDMS%2FImplemented%20in%20PO.png?alt=media&amp;token=008fa2de-5098-4b59-ab43-827552439ba7" alt=""><figcaption></figcaption></figure>

**System Behavior**

* Displays **Sales Quantity** in the column
* Based on the **defined number of days**

***

### **Verify Sales Data**

* Navigate to **Reports/Queries → Sales Register (Detailed)**

**Apply Filters**

* Select:
  * Same Item
  * Same Date Range (e.g., last 15 days)

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FCT80Xz0g7JexQajW5snq%2FReport.png?alt=media&amp;token=5837a021-3be7-4136-bfe1-cec1259246c2" alt=""><figcaption></figcaption></figure>

**Validation**

* Compare:
  * Sales Report Quantity
  * Purchase Order displayed quantity

***

### **Key Benefits**

* Enables **smart purchasing decisions**
* Provides **real-time sales insights**
* Reduces dependency on manual report checking
* Improves **inventory planning accuracy**

***

### **Best Practice Tips**

* Use realistic **sales period (7 / 15 / 30 days)**
* Combine with **stock reports for better planning**
* Regularly verify sales data accuracy

***

### **Final Outcome**

* Sales quantity is **visible during Purchase Order entry**
* Purchase decisions become **data-driven**
* Inventory levels are **better optimized**
* Workflow becomes **faster and more efficient**


---

# 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/show-sale-for-last-no-of-days.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.
