> 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/carry-forward-sizes.md).

# Carry Forward Sizes

**YouTube:** [How to Enable Carry Forward of Packs / Sizes in Purchase Orders](https://www.youtube.com/watch?v=BWp2sj3LViY)?

## How to Enable Carry Forward of Packs / Sizes in Purchase Orders?

This tutorial explains how to **automatically carry forward pack sizes in Purchase Orders** in Logic ERP. It demonstrates how enabling this feature eliminates repetitive size selection, making the purchase process faster and more efficient.

***

### **Objective of This Feature**

* Automate **pack/size selection in Purchase Orders**
* Reduce **manual effort and repetitive tasks**
* Improve **data entry speed and accuracy**
* Enhance overall **workflow efficiency**

***

### **Understanding Default Behavior (Feature Disabled)**

* While creating a **Purchase Order**
* For each item:
  * Sizes/Packs must be **selected manually every time**

**Limitation**

* Repetitive process
* Time-consuming for bulk entries

***

### **Enabling Carry Forward Sizes**

* Open **Purchase Order** **Configuration** Window.
* Navigate to **General Options Section**
* Locate and enable the option labeled as:
  * **“Carry Forward Sizes”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FWshNWUJJL3A2NCPlJO3r%2FCNF.png?alt=media&amp;token=666f5b58-c25c-44fe-bc48-a7e9e3bd1748" alt=""><figcaption></figcaption></figure>

* Click **Ok.**

***

### Implement **After Enabling Feature**

* Initiate a **New Purchase Order**
* Ensures updated configuration is applied
* Add an item with multiple Sizes/Packs

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fu5ZEJRuEEkkTqhZhIaLM%2FCarry%20Farward%20Sizes.png?alt=media&amp;token=fa39619d-c6be-4a51-9915-50d80d8937cc" alt=""><figcaption></figcaption></figure>

**System Behavior**

* Sizes/Packs are **automatically carried forward**
* No need to reselect sizes for each entry

***

### **Key Benefits**

* Saves **time during bulk order entry**
* Eliminates **repetitive manual selection**
* Improves **data consistency**
* Enhances **user productivity**

***

### **Best Practice Tips**

* Use this feature when:
  * Same sizes are repeatedly used
* Disable if:
  * Size selection varies frequently

***

### **Final Outcome**

* Pack/Sizes are **auto filled in Purchase Orders**
* Order creation becomes **faster and smoother**
* Manual effort is **significantly reduced**
* Process becomes **efficient and error-free**


---

# 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/carry-forward-sizes.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.
