> 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/setups/setup-items/setup-items-multiple-pack-sizes/configuration-multiple-packs-sizes/configuration-options-1/default-pur-c.f-sale-c.f-and-rate-c.f..md).

# Default Pur C.F, Sale C.F & Rate C.F.

**YouTube:** [How to Set Default Conversion Factors (C.F) When Creating a New Item?](https://www.youtube.com/watch?v=95V82YPUzz8)

## How to Set Default Conversion Factors (C.F) When Creating a New Item?

In this tutorial, we’ll learn how to set up **default Conversion Factor (CF) options** while creating a new item in Logic ERP.

***

### **Accessing the Option**

* **Navigate to:** Setups/Setup Items and then click on **"Setup Items Multiple Packs/Sizes".**
* In this section, you will find the option labeled as:
* Here, you will find three CF options:
  * **Pur CF**
  * **Sale CF**
  * **Rate CF**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FH3GvZakLZwgUGnpQNvyt%2FSetup%20Item%20Default%20CF.png?alt=media&amp;token=c7702cf0-535c-4b01-9ab6-3a327ea0255e" alt=""><figcaption></figcaption></figure>

* By default, all three are set to **zero**.

***

### Configure Default CF Values

* Open the **Configuration Settings**.
* Select **Set Default CF**.
* Define default values as per your requirements.
  * Example:
    * **Purchase CF = 1**
    * **Sales CF = 3**
    * **Rate CF = 3**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F7fTuOPxWQvrtlDGnZ3KL%2FSet%20Default%20Configuration.png?alt=media&amp;token=b35651ea-fc0a-4c06-a89c-3a844b061565" alt=""><figcaption></figcaption></figure>

* Save the changes.

***

### Verify During Item Creation

* Create a **new item**.
* You will see that the **Purchase CF, Sales CF, and Rate CF** are now prefilled based on your default configuration.
* Enter the item’s **conversion factor** (e.g., 1 case = 100 units of Item).

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FFY5kalyX0NRddSvdbvez%2FDefault%20Setup.png?alt=media&amp;token=54f89b7d-3b87-41a9-bf8b-e465485076b2" alt=""><figcaption></figcaption></figure>

***

### Functionality in Transactions

#### Purchase Transaction

* Create a **purchase entry**.
* Press **F5** in the **PACKS column**.
* The system will automatically pick the **case quantity** by default.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FZAXZ6EmH97Ce7ewWsbpU%2FPurchase%20CF%20New.png?alt=media&amp;token=8fe82e95-ca60-49f6-88ea-6899d52b82ec" alt=""><figcaption></figcaption></figure>

* Enter the **item rate** and save the voucher.

#### Sales Transaction

* Move to the **billing screen**.
* Add the same item to the sales transaction.
* The system will automatically pick the **single unit** as per the **Sales CF**.
* The **rate** is calculated **per piece**, based on the defined conversion factor.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FfcQ4cAbDDgOtQYLJPW10%2FSale%20Default.png?alt=media&amp;token=afc97224-83f3-4481-84c5-25807a01035f" alt=""><figcaption></figcaption></figure>

***

That’s it! You’ve successfully set up and tested the **default CF options** in Logic ERP. This ensures faster and more accurate entries during both purchase and sales transactions.


---

# 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/setups/setup-items/setup-items-multiple-pack-sizes/configuration-multiple-packs-sizes/configuration-options-1/default-pur-c.f-sale-c.f-and-rate-c.f..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.
