> 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/reports-queries/customer-+-item-sale-analysis/abc-sale-analysis-stock-norm-and-production-plan.md).

# ABC Sale Analysis, Stock Norm & Production Plan

**YouTube:** [How to Configure & Generate the ABC Sales Analysis, Stock Norm & Production Plan?](https://www.youtube.com/watch?v=XjrLfEbHt8A)

## How to Configure & Generate the ABC Sales Analysis, Stock Norm & Production Plan?

In this tutorial, we will learn how to configure and generate the **ABC Sale Analysis, Stock Norm and Production Plan** report in Logic ERP.

This report helps businesses plan production based on **actual sales performance, available stock, reserved stock, and defined stock coverage policies**. It classifies items into ABC categories and suggests the quantity that needs to be produced.

***

### Access to the ABC Sale Analysis Report

* Navigate to the **Reports/Queries** section from the main menu.
* Under **Customer + Item Sales Analysis**, open the **ABC Sale Analysis, Stock Norm and Production Plan** report.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FbjCCBRchC1Y0wqLIBKGZ%2FDefault.png?alt=media&#x26;token=8dccf85e-dbbf-47a7-ad47-27375a66abe2" alt=""><figcaption></figcaption></figure>

Before generating the report, let's configure the required planning parameters.

***

### Configure the Sale Period

Open the **Configuration** window.

Under the **Sales Period** section:

* Set **Sale Period Months** to the number of months to be considered for sales analysis (1 to 8; a new configuration starts at 3).
* For this example, we are selecting **3 months**, which is approximately **90 days**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F6Rux67DRDh7b38eCmMGd%2FSale%20Period%20Months.png?alt=media&#x26;token=a73da91d-0689-4dc9-9649-4e2e49286e82" alt=""><figcaption></figcaption></figure>

#### Important Point

The sale period should be defined according to the business's planning requirements. The selected period directly affects the sales analysis and production calculation. The period counts back from the report's **To** date.

***

### Configure Sale Value Definitions

Under **Sale Value Definition**, configure the required options. Both options below are already ticked in a new configuration.

**Net Off Sale Returns**

* Enable **Net Off Sale Returns**.
* This ensures that returned quantities are deducted from the sales figures.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FjMGOKdedM1kMJsM3dH08%2FNet%20Off%20Sale%20Return.png?alt=media&#x26;token=260e58c8-06d9-4705-b462-c170c86d0574" alt=""><figcaption></figcaption></figure>

**Exclude Inter Branch Transfers**

* Enable **Exclude Inter Branch Transfers**.
* This prevents stock transferred between branches of the same business from being treated as actual sales.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FbSXPQc77R7RHnd7TEsE5%2FExclude%20Inter%20Branch%20Transfer.png?alt=media&#x26;token=77bccdc6-983f-4ad2-a213-c5fbb381e8b9" alt=""><figcaption></figcaption></figure>

#### Objective

These settings ensure that the report is based on **actual sales performance** rather than returns or internal stock movements.

***

### Configure ABC Classification

Under **ABC Classification**, open **ABC Bands**.

For example, we can define the classification as follows:

| Category | Share of Products | Buffer Days |
| -------- | ----------------- | ----------- |
| **A**    | Top 10%           | 10 Days     |
| **B**    | Next 40%          | 20 Days     |
| **C**    | Remaining 50%     | 30 Days     |

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FQirRFKo7KwYYUyzCphf2%2FABC%20Band.png?alt=media&#x26;token=83ae1b5f-230c-4271-a612-346b6377b9fc" alt=""><figcaption></figcaption></figure>

#### Classification Logic

The category boundaries are entered as **running totals**, so the final category reaches **100%**. With the default **Classification Method** (Percent Of Item Count) they are shares of the ranked list of products; with **Cumulative Value Share** they are shares of sales value.

For example:

* A = 10%
* A + B = 50%
* A + B + C = 100%

The classification is not restricted to three categories. If required, you can also add additional categories such as **D, E**, and so on, according to your business planning policy.

***

### Configure Stock Availability

Next, configure the stock-related options.

* Tick **Select HO Branches** and choose the head office branches whose stock should count. If none are selected, stock from every branch is counted.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FOjQnhG8Xo3ksETUQJaLr%2FSelect%20HO%20Branch.png?alt=media&#x26;token=1f94964b-2a67-4c24-acbd-a3e5417441d6" alt=""><figcaption></figcaption></figure>

* Enable **Less Reserved Stock** to take off stock reserved against sale orders.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FLTFoIbI2aeW4Xp9wpNhd%2FLess%20Reserved%20Stock.png?alt=media&#x26;token=0c6ed66c-2bca-4413-955b-78e972a76dff" alt=""><figcaption></figcaption></figure>

* **Less Stock Allocated Against SO** takes off the **same** reserved stock. Tick only one of the two — ticking both deducts it twice.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FBwLkP1g8SzTeY1O50Mxc%2FLess%20Stock%20Allocated%20Against%20SO.png?alt=media&#x26;token=905af7d8-f560-4d96-ac5c-7bec43317430" alt=""><figcaption></figcaption></figure>

**Why These Options Matter**

* Stock that is already reserved or allocated against a Sales Order should not be treated as freely available stock for new production planning.

These settings help the report calculate the **actual stock available for planning**.

**Save the Configuration**

Once all the required settings have been defined:

* Save the configuration changes.
* Set the report **To** date. The sales period counts back from it; the **From** date is used only when **Sale Period Basis** is **Report Date Range**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FGzXU2Shfzu1g4SMgCMDO%2FDate%20Range.png?alt=media&#x26;token=240ca1fa-12c9-41be-9232-ef08287dbf7c" alt=""><figcaption></figcaption></figure>

For this example, since we selected a **3-month sales period**, the report looks at the three months up to the **To** date.

***

### Generate the Report

* Now, Run the Report.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FtSMZpLWc0RRZ8shyo7BC%2FReport%20View.png?alt=media&#x26;token=ddf16584-05a5-442e-8b74-ea03666f7f4b" alt=""><figcaption></figcaption></figure>

#### System Behavior

* As you can see, the system classifies the products according to the ABC classification criteria defined in the configuration.
* The classification is based on the **sales performance of the products during the selected period**.

**Generally**:

* **Category A** contains the highest-selling products.
* **Category B** contains the next level of products.
* **Category C** contains products with comparatively lower sales.

***

### Understand the Production Calculation

Let's take an example of a **Category A** product.

**Suppose:**

* Sales during the last 3 months = **1,200 units**
* Sales period = **90 days**
* Average daily sale = **1,200 ÷ 90 ≈ 13.33 units** (by default the report divides by the actual days in the period)
* Category A buffer days = **10 days**

#### Required Stock

* **13.33 units × 10 days = approximately 133 units**
* Suppose the available stock is **40 units**.
* The report will calculate:
  * **Required Stock – Available Stock**
  * **133 – 40 = about 93 units**

Therefore, the report suggests producing approximately **93 units** — or 94 with **Round Production To** set to **Whole Number**, because rounding is always up.

#### What This Means

The report helps identify:

* **What needs to be produced**
* **How much needs to be produced**
* **Which products require priority**
* **How sales performance affects production planning**

***

### Analyze the Report

As you can see, **Category A products appear at the top** because they have the highest sales contribution.

Category C products may have a higher stock coverage period, but because their sales are generally lower, their production requirement may also be comparatively lower.

This allows the business to prioritize production based on actual demand.

***

### Troubleshooting: If the Figures Do Not Match

If the report figures do not appear as expected, review the configuration settings, particularly:

* **Sale Period**
* **Net Off Sale Returns**
* **Exclude Inter Branch Transfers**
* **ABC Classification**
* **Less Reserved Stock**
* **Less Stock Allocated Against SO** (tick only one of the two reserved options)
* **Select HO Branches**

These settings directly affect the sales analysis, available stock, stock norms, and suggested production quantity.

***

### Key Benefits

* **Demand-Based Planning:** Production is calculated using actual sales performance.
* **ABC Classification:** Helps prioritize high-performing products.
* **Accurate Stock Planning:** Considers available and committed stock.
* **Reduced Overstocking:** Helps avoid unnecessary production.
* **Better Production Decisions:** Clearly indicates the quantity that needs to be produced.

### Final Outcome

The **ABC Sale Analysis, Stock Norm and Production Plan** report helps businesses convert actual sales data into a practical production plan. By configuring the sales period, ABC categories, stock coverage, and available stock correctly, Logic ERP can suggest **which products need to be produced and the approximate quantity required**.

***

### User Guide

For a full explanation of every setting, column and common question, see the [ABC Sale Analysis, Stock Norm & Production Plan - User Guide](/logic-erp-learning-hub-tutorials-and-best-practices/reports-queries/customer-+-item-sale-analysis/abc-sale-analysis-stock-norm-and-production-plan/abc-sale-analysis-stock-norm-and-production-plan-user-guide.md) and the [ABC Sale Analysis, Stock Norm & Production Plan - Configuration](/logic-erp-learning-hub-tutorials-and-best-practices/reports-queries/customer-+-item-sale-analysis/abc-sale-analysis-stock-norm-and-production-plan/abc-sale-analysis-stock-norm-and-production-plan-configuration.md).


---

# 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/reports-queries/customer-+-item-sale-analysis/abc-sale-analysis-stock-norm-and-production-plan.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.
