> 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/track-and-trace/movement-types-field.md).

# Movement Types Field

### Overview

Movement type fields are the data elements that are used in activity templates to record and manage material movement and inventory transactions. These fields provide a structured framework for accurately capturing important details about each transaction, such as the quantity of material being moved, the specific material being moved, and any additional attributes or key attributes that may be associated with the material or transaction.

* **Quantity**: The quantity field captures the amount of material being moved in a given transaction, enabling accurate tracking of inventory levels.
* **Material**: The material field captures the specific material being moved in a given transaction, enabling accurate tracking of inventory levels. A material is referenced by either the external id or a barcode reference.
* Inventory Key: The inventory key field is the unique identifier that will be used to track the lot/batch/pallet of a material. The combination of material id and inventory key makes it unique, meaning a different material could use the same inventory key without conflict.
* **Key Attributes**: Key attributes are attributes that are essential for accurately tracking and tracing specific properties across different inventory keys, such as a material's serial number or expiration date. *These attributes are searchable but limited to 3 per movement type.*
* **Attributes**: Additional attributes that are not required to be searched/filtered on.
* **Asset**: Define the asset for which the movement will apply for
* **From Asset**: For Transfer movement types. Define the asset for which the from/issue of material should be from
* **To Asset**: For Transfer movement types. Define the asset for which the to/receipt of material should be to.

{% hint style="info" %}
When creating fields for a Movement Type that utilizes an **automated consumption strategy** (FIFO or LIFO), deliberately do **not** add an **Inventory Key** field to the configuration.

Leaving this field out ensures the operator is not prompted to pick or scan a batch on the execution interface, allowing the system to autonomously resolve and deduct the appropriate stock in the background.
{% endhint %}

### Creating a Movement Type Field

Go to **Settings > Configuration > Movement Types**

Select the relevant **Movement Type.** Go to **Movement Type Field** **> Create**

<figure><img src="/files/bACHJWlH3iYjx707j4xC" alt="" width="563"><figcaption></figcaption></figure>

Enter the relevant fields.

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

### Fields

| Name                | Description                                                           |
| ------------------- | --------------------------------------------------------------------- |
| **ID**              | This is generated by TilliT and cannot be changed.                    |
| **Name \***         | Name of the item, usually refers to the specific data being captured. |
| **Movement Type\*** | The movement type this field is for.                                  |
| **Active**          | Enabled/Disabled.                                                     |
| **Field \***        | Defines the logic behind the movement type field.                     |
| **Is required**     | Makes item mandatory.                                                 |