> 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/allow-packing-slip-against-reserved-lot-counts.md).

# Allow Packing Slip Against Reserved Lot Counts

**YouTube:** [How to Enforce Party-Item-Wise Lot Count Limits in Packing Slips?](https://youtu.be/GFSOTTdbwDg)

## How to Enforce Party- Item- Wise Lot Count Limits in Packing Slips?

In this tutorial, we will learn how to configure Logic ERP to allow Packing Slip entries only against the **reserved lot count** for a particular item.

This option ensures that the number of lots used in a Packing Slip does not exceed the number of lots reserved for the selected party and item.

***

### Reserve Lot Counts for the Item

Before enabling the Packing Slip restriction, let's first configure the lot count reservation.

* Open **Reserve Party + Item Wise Lot Count**.
* Select the required **Party** and **Item**.
* Click **Refresh**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FN9m4ssCa88PxjaYvt16k%2FDefault.png?alt=media&amp;token=2d346ea7-ac68-4945-8705-848d60597845" alt=""><figcaption></figcaption></figure>

#### Current Lot Count

* As you can see, the total lot count available for the selected item is **3**.
* Now, reserve **2 lots** for this item.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FqstxXxGezcYhR9JRpcM4%2FDefault%202.png?alt=media&amp;token=b77fe669-5d56-4b57-a570-a00c0493f644" alt=""><figcaption></figcaption></figure>

This means that the Packing Slip will be allowed to use a maximum of two lots when the reservation restriction is enabled.

***

### Enable Reserved Lot Count Validation

Now, let's configure the Packing Slip to validate the reserved lot count.

* Open the **Packing Slip Configuration** window.
* Navigate to the **Other Options Two** section.
* Locate and enable the option labeled as:

> **"Allow Packing Slip Against Reserved Lot Counts"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FPK04dpE5iGLWu4JWXxKM%2FCNF.png?alt=media&amp;token=3c5a823e-5504-48d3-87dd-886f536d0791" alt=""><figcaption></figcaption></figure>

* Save the configuration changes.

#### System Behavior

When this option is enabled, the system allows the Packing Slip to use only the number of lots reserved for the selected item.

In our example:

* **Total lots available:** 3
* **Reserved lots:** 2
* **Maximum lots allowed in Packing Slip:** 2

***

### Create a Packing Slip

Now, let's create a new Packing Slip and test the configuration.

* Initiate a new **Packing Slip** entry.
* Select the required customer.
* Proceed to the **Item Details** section.
* Scan the required item code.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FbDZbUIb6GXkaD5jWG3Yq%2FBehavior.png?alt=media&amp;token=45c9e7bc-dfb8-46d5-a589-6f309b27f40b" alt=""><figcaption></figcaption></figure>

#### Stock Allocation

* The current stock for the item is **28 units**.
* Let's allocate a quantity of **25 units**.
* In the **Lot Details** section, the required quantity is allocated from **three different lots**.

***

### Verify the Reserved Lot Count Validation

Now, let's try to save the Packing Slip.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FyCbWtzGYaVMVapAcIjH9%2FMesage%20Prmot.png?alt=media&amp;token=65ba899c-a032-46ff-b580-3865283a448b" alt=""><figcaption></figcaption></figure>

#### System Behavior

* When you attempt to save the entry, the system displays an error indicating that the **reserved lot count has been exceeded** for the selected item.
* This occurs because only **2 lots** were reserved, while the allocated quantity is currently being picked from **3 lots**.

Therefore, the system does not allow the Packing Slip to be saved.

***

### Adjust the Lot Allocation

To bring the entry within the reserved lot count:

* Delete one of the lot rows.
* The allocated quantity is now reduced to **20 units**.
* The stock is now allocated from only **2 lots**.

#### System Behavior

* The number of lots used is now within the reserved limit.
* The system allows the Packing Slip entry to be saved successfully.

***

### Key Benefits

* Controls the number of lots used during Packing Slip entry.
* Ensures Packing Slips follow the reserved lot count.
* Prevents users from exceeding party- and item-wise lot reservations.
* Provides automatic validation before saving the transaction.
* Improves control over lot-wise stock allocation.

#### Final Outcome

By enabling **"Allow Packing Slip Against Reserved Lot Counts"**, Logic ERP ensures that the number of lots used in a Packing Slip does not exceed the reserved lot count for the selected party and item.


---

# 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/allow-packing-slip-against-reserved-lot-counts.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.