> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/warehouse/carton-break-rule/creating-carton-break-rule.md).

# Creating Carton Break Rule

The **Carton Break Rule** module in XoroERP allows users to define how items are grouped and packed into cartons based on specific criteria, enhancing efficiency, order accuracy, and warehouse organization.&#x20;

Creating a Carton Break Rule involves defining the carton break rule attributes, configuring the task assignment behavior, and specifying the rule type and sequence that determine how inventory is grouped into cartons and how picking tasks are generated during wave processing.

{% hint style="info" %}
To create a carton break rule, go to **Menu > Admin > Warehouse > Carton Break Rule**
{% endhint %}

### Entering Carton Break Rule Attributes

To create a carton break rule, you will begin by defining the basic attributes of the rule, which include the following:

* **Name:** Enter a descriptive name for your Carton Break Rule.
* **Unit Limit:** Specify the unit limit for items that can be packed into each carton.
* **Case Limit:** Specify the units of items for a sealed case.
* **Task Assignment Behavior:** This field allows users to define how warehouse tasks are assigned when waves are created using the carton break rule. Available options include standard task assignment behavior and **Combine Replen and Each Pick Lines**, which combines replenishment and each-pick tasks into a single task assignment.

<figure><img src="/files/T0c9NtfY5ZQuK82EuxjL" alt=""><figcaption></figcaption></figure>

### Defining the Rule Type & Sequence

After defining the key attributes, you will define the specific criteria that will determine how cartons are broken down, selecting criteria from the available options and setting their sequence. This allows you to stack multiple rules and define the order in which they should be applied.

1. **Select Rule Type**: From the dropdown menu, choose the first rule type you want to apply. XoroERP provides multiple options:

   * **Order Number:** Breaks the carton by sales order and groups items belonging to the same order number into a single carton (or multiple cartons if the order exceeds the defined unit or case limits).
   * **Zone:** Groups items from the same warehouse zone together.
   * **Base Part Number:** Groups items sharing the same base part number. This is useful when dealing with variations of a single product.
   * **Item Number:** Groups items with the same item number. This ensures that identical items are packed together.
   * **Quality:** Groups items based on their assigned quality grade.

   <figure><img src="/files/pAkmxPgHft9EbP6mAtht" alt=""><figcaption></figcaption></figure>
2. **Add Rule**: Click "**Add Type"** to add the rule to the sequence. The selected rule will appear in the list below, showing the order in which it will be applied.

   <figure><img src="/files/08AqVIoXO7xMmLAJthkw" alt=""><figcaption></figcaption></figure>
3. **Stack Multiple Rules**: If you wish to apply additional rules, select another option from the dropdown and click "Add Type" again. You can stack multiple rules, enabling a comprehensive approach to cartonization.<br>

   <figure><img src="/files/SN26X1glcxeFaCKnLznU" alt=""><figcaption></figcaption></figure>

### Setting the Rule Sequence

The sequence of rules determines the order in which the rules are applied when packing items into cartons. The order in which rules are added determines their execution priority. Rules are processed sequentially; the first rule is applied, then the second, and so on. . For instance, if you set the first rule as **Order Number**, the system will group items by order. If you then add a secondary rule based on **Zone**, the system will first pack items by order, then subdivide these items by warehouse zone. This allows items within the same order and zone to be packed together, reducing handling errors and optimizing organization. Click and hold the 9-dot icon and drag the rule up and down to rearrange the sequence.&#x20;

<figure><img src="/files/NywbJBstKlodAIy45d7a" alt=""><figcaption></figcaption></figure>

After defining the carton break rule, click "Save" to create the carton break rule.

<figure><img src="/files/BQdG0NrVxZkmgUR8hFZr" alt=""><figcaption></figcaption></figure>

### Configuring Task Assignment Behavior

The **Task Assignment Behavior** setting determines how picking tasks are generated when a wave is created using the carton break rule.

**1. Combine Replen and Each Pick Lines**

When **Combine Replen and Each Pick Lines** is selected, the system combines lines that are immediately available for picking and lines that are waiting for replenishment into a single task assignment.

**Workflow:**

**Step 1:** Create a sales order containing an item available in an Active location and ready for picking. Take another item stored in a Reserve location that requires replenishment before picking.

**Step 2:** When a wave is created using a carton break rule configured with **Combine Replen and Each Pick Lines**, the system generates a single task assignment for both lines.

**Step 3:** During Wave Line Allocation, the **replenishment line** has a **separate task ID**, while the **waiting-for-replenishment** and **each-pick lines** share a **single task ID**.

This allows warehouse operators to manage replenishment and picking activities through a single consolidated task rather than multiple independent tasks.

{% hint style="info" %}
This behavior will apply only when both the **each-pick** and **waiting-for-replenishment lines** belong to the same order, and neither line is configured as a **case pick**.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xorosoft.com/xoroerp-1/admin/warehouse/carton-break-rule/creating-carton-break-rule.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
