> For the complete documentation index, see [llms.txt](https://help.tillit.cloud/tillit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tillit.cloud/tillit/knowledge-base/setting-up-tillit/asset-hierarchy/order-template/order-template-dependency.md).

# Order Template Dependency

An order dependency defines the relationship between operations in your production line. For instance, on a filling line, the Filler operation depends on the Depalletiser operation. This dependency allows the system to track an infeed counter, which is compared against the quantity produced by the target asset. The difference between these values represents the reject count.

The Order Template dependency must be created and AutoReject must be enabled for this feature to function. To ensure accurate counts, reject totals are only calculated once all dependent orders are completed, preventing timing discrepancies from affecting the results.

## Navigation

Navigate to Asset Hierarchy > Order Templates, select an Order Template, expand the Dependencies panel, and click Create.

<figure><img src="/files/f8SeiOpXP11Wt1HWL33M" alt="Modal titled &#x22;Created Order Template Dependency&#x22; with fields for Name, Infeed Order Template, and Order Template prefilled as &#x22;Warehouse&#x22;, plus an Auto Reject toggle."><figcaption></figcaption></figure>

| Name                  | Description                                                                         |
| --------------------- | ----------------------------------------------------------------------------------- |
| Name                  | Dependency name                                                                     |
| Infeed Order Template | The Order Template for orders that are to be finished before this Order Template    |
| Order Template        | Current Order Template, prefilled by the order template you are currently in.       |
| Auto Reject           | If enabled, then the reject totals will be calculated once all orders are completed |

## Examples

### No Route

Where assets just have a single order, hence no need to calculate dependent reject counts

<figure><img src="/files/kR7dO3rnjuRgRIJun637" alt="Diagram showing three independent asset boxes labeled Line 1, Line 2, and Lab vertically arranged with no connecting route arrows, with heading text stating &#x22;In this example, there is no routing. A single order.&#x22;" width="375"><figcaption></figcaption></figure>

### Simple Route

Where you only have 1 single line of production throughout the assets.

<figure><img src="/files/61cjBofAOa4lia1UWRUE" alt="Diagram showing production line routing patterns and tables for &#x27;Order Template&#x27; and &#x27;Order Template Dependency&#x27;. Line 1 and Line 2 flow through Depal, Filler, and Palletiser stages, with a standalone Lab asset excluded from the route."><figcaption></figcaption></figure>

### Multiple Infeeds

Since we do not know the proportions to assign to multiple assets in a segment, reject counts will be calculated once all orders are completed.

<figure><img src="/files/DD8m8ngr18EGzqLU8Du0" alt="Diagram showing a production line split where Depal 1 feeds into two separate fillers, Filler 1 and Filler 2. An annotation notes that reject count cannot be determined here without knowing the proportion assigned to each filler. Below are Order Template and Order Template dependency tables"><figcaption></figcaption></figure>
