> 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/billing/packing-slip/packing-slip-configuration/carry-forward-packs-sizes-item-wise-entry.md).
# Carry Forward Packs/Sizes (Item Wise Entry)
**YouTube:** [How to Configure Carry Forward of Packs/Sizes in Item-Wise Entry in Packing Slips?](https://youtu.be/UzntJAPlVO4)
## How to Configure Carry Forward of PacksSizes in Item Wise Entry in Packing Slips?
In this tutorial, we will learn how to enable the **Carry Forward Packs/Sizes (Item Wise Entry)** option in Packing Slip entry.
This option automatically carries forward the available pack sizes to the next row during item-wise entry, reducing repetitive manual data entry.
***
### Observe the Default Behavior
Let's first observe how the system works by default.
* Initiate a new **Packing Slip** entry.
* Select the required customer.
* Navigate to the **Item Details** section.
* Click on **Item Wise Entry**.
* Transact an item.
**Default Behavior**
* By default, the packs or sizes need to be entered manually for each new row.
* The user has to repeat the same pack or size details while entering subsequent rows.
***
### Let's Enable Carry Forward Packs/Sizes
To avoid repetitive manual entry, Logic ERP provides the **Carry Forward Packs/Sizes (Item Wise Entry)** option.
* Open the **Packing Slip Configuration** window.
* Navigate to the **Other Options Four** section.
* Locate and enable the option labeled as:
> **"Carry Forward Packs/Sizes (Item Wise Entry)"**
* Save the configuration changes.
***
### Verify the Carry Forward Functionality
Now, let's create a new Packing Slip entry and observe the result.
* Initiate a new **Packing Slip** entry.
* Select the required customer.
* Go to the **Item Details** section.
* Click on **Item Wise Entry**.
* Transact an item.
#### System Behavior
* As you enter the item, the available pack sizes for that item are displayed.
* When you move to the next row, the pack sizes are automatically carried forward.
* There is no need to manually enter each pack or size again.
**Result:** The system automatically carries forward the available packs and sizes to the next row, making item-wise Packing Slip entry faster and more convenient.
***
### Key Benefits
* Eliminates repetitive manual entry of packs and sizes.
* Saves time during item-wise Packing Slip entry.
* Reduces the possibility of manual entry errors.
* Provides a faster and more consistent data-entry process.
#### Final Outcome
By enabling **"Carry Forward Packs/Sizes (Item Wise Entry)"**, Logic ERP automatically carries forward the available packs and sizes to the next row during **Item Wise Entry** in Packing Slips.
---
# 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/billing/packing-slip/packing-slip-configuration/carry-forward-packs-sizes-item-wise-entry.md?ask=&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.
