Templates define rules and attributes (data to capture) for various parts of the system. Templates must be set up before creating the records that depend on them. Templates are required for:
Item templates are the first step before setting up item masters and receiving units into the system. Templates can also categorize items — for example, a tool-tracking system might have separate templates for ladders, drills, and saws.
To set up item templates, go to Settings (top menu bar) and select Item Setup.
Tip: Before defining templates, categorize and group your items based on shared rules and attributes.Item templates specify whether units are tracked by a unique ID (serialized) or by quantity. The available rules depend on which option is selected.
Under the Rule Assignment tab, define the rules for this template. Items can be configured as:
| Rule | Description |
| Track Place-In-Service | Units received are set to "Received" status. They can be moved and transferred but cannot be checked out or deployed until placed in service (status updates to "Available"). |
| Capture Unit Cost | Unit cost can be captured on Receive New Unit and Create transactions. Stored against the serialized item unit. |
| Can be Assigned to a Group | Groups support reporting multiple assets against a single ERP/Accounting Asset record. The Group ID represents the financial record. |
| Can be Checked Out | Available units can be checked out to assignees or customers. Already checked-out items can be transferred or checked in and re-checked out. Sub-rules include tracking an expected return date. |
| Can be Deployed | Similar to check out, but deployed units maintain a facility or customer address location. Typically used for stationary assets where the physical location is obvious. |
| Track Ownership by Team | Ownership is tracked by team (internal or customer). Visibility is based on both custody and ownership. If unchecked, no team ownership is assigned and visibility is available to all users based on custody. |
| Track Maintenance Activities | Units can be set up for scheduled maintenance or used to record unplanned maintenance activities. |
| Track as a Master Item for Build Unit | The asset is treated as a parent unit; components can be assigned. Components may be returnable or consumable. Unlimited nesting is supported. |
| Enable as a Component Item for Master Item | The asset can be selected as part of a unit build. Assets in a build retain "In Build" status until removed. |
| Track Retirement Date and Disposal | Assets can be assigned a retirement date. Disposed assets are no longer actively tracked. A grid view provides access to all disposed assets. |
| Enable Status Change on Update Unit | Enables status changes on the Update Unit transaction (e.g., changing from Available to Out-of-Service for maintenance). |
| Track as Rental TO Customers | Enables billing schedule assignment. Billing is calculated against assets checked out to a customer-associated project. |
| Track as Rental FROM Vendors | Enables billing schedule assignment. Billing is calculated against assets from a vendor. |
| Rule | Description |
| Capture Unit Cost | Unit cost can be captured on Receive New Unit and Create transactions. |
| Can be Checked Out | Available items can be checked out to assignees or customers. The unit is marked as consumed. Use the Unit Return transaction to record returns to stock. |
| Track Ownership by Team | Ownership tracked by team. Visibility based on custody and ownership. |
| Track as a Master Item for Build Unit | Asset treated as a parent unit with assignable components. Unlimited nesting supported. |
| Enable as a Component Item for Master Item | Can be selected as part of a unit build. Marked as consumed when added, but reviewable in logs and reports. |
| Enable Status Change on Update Unit | Enables status changes on the Update Unit transaction. |
| Track as Parts of Maintenance | Units can be selected as components to issue on unit maintenance. |
| Rule | Description |
| Capture Unit Cost | Unit cost can be captured on Receive New Unit and Create transactions. |
| Can be Checked Out | Available items can be checked out. Already checked-out items can be transferred or checked in and re-checked out. Sub-rules include tracking an expected return date. |
| Can be Deployed | Deployed units maintain a facility or customer address location. |
| Track Ownership by Team | Ownership tracked by team. Visibility based on custody and ownership. |
| Enable as a Component Item for Master Item | Can be selected as part of a unit build. Assets retain "In Build" status until removed. |
| Track as Rental TO Customers | Enables billing schedule for customer-associated projects. |
| Rule | Description |
| Capture Unit Cost | Unit cost can be captured on Receive New Unit and Create transactions. |
| Can be Checked Out | Available items can be checked out. Recorded as consumed. Use the Return transaction to record returns to stock. |
| Track Ownership by Team | Ownership tracked by team. Visibility based on custody and ownership. |
| Enable as a Component Item for Master Item | Can be selected as part of a unit build. Marked as consumed, reviewable in logs and reports. |
| Track as Parts for Maintenance | Available to select as a consumable for maintenance. Marked as consumed. Viewable in logs and reports. |
| Rule | Description |
| Capture Unit Cost | Unit cost can be captured on Receive New Unit and Create transactions. |
| Track Ownership by Team | Ownership tracked by team. Visibility based on custody and ownership. |
| Enable Capture of Expire Date | When enabled, the expire date field is available. If existing quantities share the same item + lot, the expire date inherits from the original entry. |
| Enable Capture of Manufacture Date | When enabled, the manufacture date field is available. If existing quantities share the same item + lot, the manufacture date inherits from the original entry. |
| Enable as a Component Item for Master Item | Can be selected as part of a unit build. Marked as consumed, reviewable in logs and reports. |
Under the Weights & Dimensions tab, define the default UOM and weight/dimension rules:
Under the Attributes tab, assign attributes. Create your attributes before setting up this section. Attributes can be set as optional or required.
Item attributes can be assigned at three levels:
Master — Captured when a new item master is created or imported. Master-level attributes are standard data related to the item code (e.g., manufacturer, model). All units with this item master inherit the master data, eliminating the need to capture these details for every unit.
Unit — Data specific to individual units. Typically presented when adding or receiving a new unit, though attributes can be configured to capture on alternate transactions. Unit attributes work best for serial-tracked items. For quantity-tracked items, they become filtering attributes — use caution. Unit attributes can be set to default for receiving transactions (e.g., manufacturer may be the same across 20 units received at once). They can also be enabled for: Build Unit, Update Unit, Check In, Maintenance, Allocate to Project, Transfer Site Location, and Transfer Ownership.
Transaction — Data associated with the unit on a specific transaction. Not stored as a unit attribute, but as historical data. For example, capturing a unit's condition at each check-in creates a historical report over the item's lifecycle.
Define movable containers (pallets, cartons, boxes) under Container Setup. Containers are tracked by a unique ID and support grouping items for movement or shipping.
| Rule | Description |
| Can Hold Hazardous Material | Allows the container to hold items marked as hazardous. |
| Can Combine Items with Different Attributes | When checked, allows a mix of items. When unchecked, restricts contents to the same item master and attributes (e.g., grouping same lot numbers). |
| Can Combine Items with Multiple Owners | Supports segregating container contents by ownership. Used for organizations managing customer-owned inventory. |
| Restrict Contents to a Single Item Master | Tracks items on a container level (e.g., a container holding 100 of WIDGET-A that can be picked as a single unit for orders). |
| Can Hold Other Movable Containers | Enables nesting containers. Typically checked for large containers used for shipping (pallets, crates). Unchecked for small containers (boxes, cartons) to restrict them to item units only. |
| Available as Pick-to Container for Pick Order | Makes this container available for packing during order pick activities. |
| Track Ownership by Team | Enables tracking the container's owner. Ideal when tracking customer-owned items. |
| Can be Directly Shipped | Container can be shipped outside of a shipment build. |
| Allow for Update Unit Transaction | Enables updating container data (weight, dimensions, attributes) after creation. |
| Enable Project Allocation | Allows assigning a project to the container. Only items allocated to the project (or unallocated) can be added. |
If tracking weights and dimensions, define the UOM and specify when data is captured:
Attributes can be assigned at three levels:
Transport setup defines container types or shipping methods for carriers. Different templates can capture different attributes (e.g., account numbers or third-party billing fields).
Access Transport Setup under the Settings icon on the top menu bar.
Required if using the shipping functionality. Templates define the data captured for each shipment (e.g., a Bill of Lading template might include BOL Number, Freight Charge Terms, and Freight Bill To attributes). Attributes can be marked as required for shipping. Planned Carrier and Expected Ship Date are inherited attributes for all shipment templates.
Access Shipment Setup under the Settings icon on the top menu bar.
Required if completing maintenance activities or setting up maintenance plans.
Required when setting up projects or jobs. Project templates define additional attributes to track. Standard project data (no attributes needed) includes:
Access Project Setup under the Settings icon on the top menu bar.
Required if using the Package Tracking functionality.
Templates are defined for three location types:
Facilities represent internal site locations (warehouse, plant, tool crib, stockroom). Access setup from the Settings icon under Location Setup — select the Facility tab.
Areas are locations within a facility (aisle, shelf, row, bin, floor area). Every facility requires at least one area. Access setup from the Settings icon under Location Setup — select the Area tab.
Area Template Rules:
| Rule | Description |
| Can Contain Hazardous Material | At least one area should have this enabled if tracking hazardous items. Hazardous items cannot be assigned to areas without this rule. |
| Mark Units as Consumed When Received from In-Transit Transfer | Units received from another internal facility are automatically marked as consumed. Supports recording receipt and consumption at an end-point destination. |
| Set as Stock Area for Picking | Only areas with this flag are available for order picks. Separates staged items from items available to pick. |
| Set as Staging Area | When enabled, the area is available for moving items during picking and reserving. |