> ## Documentation Index
> Fetch the complete documentation index at: https://mintlify.com/lopiv2/invenicum/llms.txt
> Use this file to discover all available pages before exploring further.

# Asset Types

> Define categories and custom fields for your inventory items

## Overview

Asset Types are templates that define what information you collect for each category of items. Think of them as customizable forms - you create one asset type for "Laptops" with fields like Serial Number and RAM, another for "Office Supplies" with fields like Brand and Quantity per Pack.

## Creating an Asset Type

<Steps>
  <Step title="Navigate to Asset Types">
    From your container, click on **Asset Types** in the navigation.
  </Step>

  <Step title="Click Create New">
    Click the **New Asset Type** button.
  </Step>

  <Step title="Upload an Image">
    In the image section, upload a representative icon or photo for this type (optional but recommended).
  </Step>

  <Step title="Enter Basic Info">
    In the General Configuration section:

    * **Name** (required): The category name (e.g., "Laptops", "Furniture", "Books")
    * **Serialized Toggle**:
      * Turn ON for unique items (each item = 1 quantity)
      * Turn OFF for bulk items where you track quantities
  </Step>

  <Step title="Add Custom Fields">
    In the Specifications section, click **Add Field** to define what data to collect. See [Custom Fields](#custom-fields) below.
  </Step>

  <Step title="Save the Asset Type">
    Click **Create Asset Type** to finish.
  </Step>
</Steps>

<Tip>
  **Choose Serialized Carefully**: This setting affects how quantities work. Laptops should be serialized (each one is unique). Pens should be non-serialized (you track them in bulk).
</Tip>

## Custom Fields

Custom fields let you capture specific information unique to each asset type.

### Field Types

#### Text

Free-form text entry for names, descriptions, notes, etc.

**Example uses**:

* Model name
* Notes
* Part number

#### Number

Numeric values without currency formatting.

**Example uses**:

* RAM (GB)
* Screen size (inches)
* Year manufactured

#### Price

Monetary values with currency conversion support.

**Example uses**:

* Purchase price
* Market value
* Replacement cost

<Note>
  Price fields are automatically converted between your display currency and the base currency for storage.
</Note>

#### Date

Date picker for time-based information.

**Example uses**:

* Purchase date
* Warranty expiration
* Last maintenance

#### Boolean (Yes/No)

Toggle for true/false properties.

**Example uses**:

* Under warranty
* Available for loan
* Needs repair

#### Dropdown (List)

Select from predefined options linked to a Data List.

**Example uses**:

* Manufacturer (from a list of approved vendors)
* Condition (New, Good, Fair, Poor)
* Department (HR, IT, Finance)

<Tip>
  Dropdowns enforce consistency. Instead of typing "Dell" and "DELL" as separate entries, users select from one standardized list.
</Tip>

### Adding a Custom Field

<Steps>
  <Step title="Click Add Field">
    In the Specifications section, click the **Add Field** button.
  </Step>

  <Step title="Enter Field Name">
    Give the field a clear, descriptive name (e.g., "Serial Number", "RAM (GB)").
  </Step>

  <Step title="Select Field Type">
    Choose from: Text, Number, Price, Date, Boolean, or Dropdown.
  </Step>

  <Step title="Configure Options">
    * **Required**: Toggle on to make this field mandatory
    * **Countable**: Toggle on to enable counting items by this field's value
    * **Summable**: (Numbers/Prices only) Toggle on to show sum totals
    * **Data List**: (Dropdowns only) Select which list provides the options
  </Step>

  <Step title="Reorder if Needed">
    Drag fields to reorder how they appear in the item form.
  </Step>
</Steps>

### Field Properties

#### Required

Mark a field as required to ensure data completeness. Users cannot save items without filling in required fields.

#### Countable

Countable fields can be used with the counter feature to group and count items by specific values.

**Example**: Mark "Department" as countable, then use the counter to see:

* 12 items assigned to IT
* 8 items assigned to HR
* 5 items assigned to Finance

#### Summable

For number and price fields, enabling summable shows totals in the asset list.

**Example**: A summable "Purchase Price" field will show the total value of all items at the bottom of the list.

#### Data Lists

Dropdown fields must be linked to a Data List, which is a reusable collection of options. Data Lists are managed at the container level and can be shared across multiple asset types.

See [Working with Data Lists](#working-with-data-lists) below.

## Editing Asset Types

<Steps>
  <Step title="Navigate to Asset Types">
    From your container, go to Asset Types and find the one you want to modify.
  </Step>

  <Step title="Click the Type Card">
    Click on the asset type card to view its details.
  </Step>

  <Step title="Click Edit">
    Click the edit icon in the type detail view.
  </Step>

  <Step title="Make Changes">
    Modify the name, image, serialized setting, or custom fields.
  </Step>

  <Step title="Save Changes">
    Click **Save** to apply your updates.
  </Step>
</Steps>

<Note>
  **Impact on Existing Items**:

  * Adding fields: New fields appear empty on existing items
  * Removing fields: Data is retained in the database but no longer displayed
  * Changing the serialized setting: Does not affect existing items' quantities
</Note>

## Working with Data Lists

Data Lists provide dropdown options and are managed separately from asset types.

### Creating a Data List

<Steps>
  <Step title="Go to Container Settings">
    Navigate to your container's data lists section (usually in container management).
  </Step>

  <Step title="Create New List">
    Click **New Data List** and give it a name (e.g., "Computer Manufacturers").
  </Step>

  <Step title="Add Items">
    Add individual options to the list:

    * Dell
    * HP
    * Lenovo
    * Apple
  </Step>

  <Step title="Save the List">
    Save the data list so it's available for dropdown fields.
  </Step>
</Steps>

### Using Data Lists in Fields

When creating or editing a dropdown field:

1. Select **Dropdown** as the field type
2. In the **Data List** selector, choose an existing list
3. The field will now show those options when creating items

<Tip>
  Create data lists before you build asset types with dropdown fields. This makes the setup process smoother.
</Tip>

## Asset Type Images

Adding an image to your asset type helps with visual identification:

* **Accepted formats**: JPG, PNG, GIF
* **Display locations**: Asset type grid, navigation, item creation
* **Size**: Images are automatically resized for optimal performance

### Adding/Replacing Images

1. Click **Add Image** in the image section
2. Select an image file from your device
3. The image uploads as base64 data
4. To replace, click **Remove Image** then add a new one

## Serialized vs. Non-Serialized

This is a key distinction that affects how you track quantities:

### Serialized Items

* Each item is unique (quantity always = 1)
* Examples: Laptops, monitors, vehicles, furniture
* Creating 10 laptops means 10 separate item entries
* Best for assets you need to track individually

### Non-Serialized Items

* Items are interchangeable (quantity can be > 1)
* Examples: Pens, paper, cables, screws
* Creating one item entry can represent 100 units
* Best for supplies you track in bulk

<Tip>
  **When in doubt, choose serialized**. It's easier to track individual items separately than to split a bulk entry later.
</Tip>

## Templates

Asset Types act as templates for creating items. When you click "Create Item" for a specific type, the form automatically includes:

* All custom fields you defined
* Appropriate input controls (text boxes, dropdowns, date pickers)
* Required field validation
* Field ordering as you configured

## Categories

While Invenicum doesn't have a separate "category" system, you can organize asset types using:

* **Naming conventions**: Group related types with prefixes (e.g., "IT - Laptops", "IT - Monitors")
* **Custom fields**: Add a "Category" dropdown field to items
* **Multiple types**: Create separate types for each category

## Best Practices

<Tip>
  **Start Simple**: Begin with a few basic fields. You can always add more later as you learn what information you actually need.
</Tip>

<Tip>
  **Use Descriptive Names**: Name fields clearly ("RAM (GB)" instead of just "RAM"). This helps anyone using the system.
</Tip>

<Tip>
  **Leverage Dropdowns**: Use dropdowns instead of text fields when you want consistent, standardized data (manufacturers, conditions, departments).
</Tip>

<Tip>
  **Mark Key Fields as Required**: Make essential identification fields (like Serial Number) required to ensure data quality.
</Tip>

<Tip>
  **Plan Your Data Lists First**: Create all your data lists before building asset types. This makes the process much smoother.
</Tip>

<Tip>
  **Consider Future Needs**: Think about what reports you might want to generate later. Add fields that support those use cases.
</Tip>

## Common Questions

### How many custom fields can I add?

There's no hard limit in the UI, but for practical purposes, keep it under 20 fields per type. Too many fields make item creation cumbersome.

### Can I share custom fields across asset types?

No, custom fields are specific to each asset type. However, you can use the same data lists across multiple types, ensuring consistency.

### What happens if I delete a custom field?

The data is preserved in the database but no longer displayed. If you recreate a field with the same name, existing data won't automatically reappear (it's stored by field ID, not name).

### Can I make a field required after items already exist?

Yes, but be aware that existing items may not have that field filled in. You'll need to edit those items to complete the required field before you can save changes to them.

### How do I change dropdown options after creating items?

Edit the data list to add or remove options. Existing items will keep their selected values even if you remove an option from the list.

## Related Topics

* [Managing Items](/guides/managing-items) - Create items using your asset types
* [Reports](/guides/reports) - Generate reports organized by asset type