Welcome to PanatrackerST. This step-by-step guide walks new organizations through initial setup.

Panatrack will provision your sandbox and production environments. The sandbox is set up first based on the following information you provide to the implementation team:

• Company name
• URL prefix: [prefix].panatracker.net
• System user(s) for configuration and training
• Facility location(s): IDs and names

System users are initially given the seeded organization role of SuperUser and team role of Admin. These can be changed later.

Item Setup

Item Templates

Start by creating item templates. Templates represent how items are categorized. An item category is a classification used to group similar items based on shared characteristics, purpose, or usage, such as tools, safety equipment, consumables, electronics, or spare parts. Item categories influence how items are tracked, valued, stored, and reported.

Templates define:

• Rules: How the item is tracked
• Attributes: What additional data is tracked

See the item template setup section for details on rules and attribute assignment logic.

Before creating templates, review these related settings:

• UOM Setup: There are seeded units of measure in the system. Review the available options and add more if needed.
• Attributes: As part of category planning, define the attributes you need for item masters or item units. Create them before setting up templates.

Item Masters

Once you've established item categories and created the associated templates, add your item masters. Item masters may represent a SKU, part number, model number, or a descriptive identifier. Examples:

Item master naming examples

The description for items added to the system is inherited from the item master. Keep this in mind, especially with general descriptions. Consider how someone will request the item:

• For quantity-tracked parts or supplies, check whether items already have a barcode label with the item number.
• For serial-tracked items, users select by unique ID and inherit both the item master code and description.

See Item Master Setup for details.

Unit Records

Once item masters are defined, add unit records. PanatrackerST uses a handle (a barcoded label identifier) to select items on transactions:

Quantity-Tracked Items

• Attribute data is defined on the item master. No unit-level attributes apply to quantity-tracked items.
• Transaction-level attributes can be captured and associated with the item based on transaction data.

Serial-Tracked Items

• Handle (ID) must be unique.
• Items are selected by the unique handle ID. Some transactions include a filter by item master.
• Unit-level attribute data can be set on individual units: for example, manufacturer serial number, unit cost, or warranty expiration date.
• Transaction-level attributes build historical data for the unit: for example, capturing condition at check-in.

Lot-Tracked Items

• The handle is the lot number (a separate lot number field is also populated).
• Unit-level attributes apply to the item-lot combination. For example, ITEM-A / LOT123 retains the same attribute data such as expiration date.

Locations and Areas

Before adding item units, define your locations.

Facilities

Facilities represent a building or department: for example, a warehouse, project site, or IT department.

See Facility Setup for details.

Areas

Areas are specific locations within facilities that make finding assets and inventory easier. Each facility must have at least one area. Area templates offer additional rules and logic.

Common area types:

• Staging areas: General receiving areas or locations where items are gathered for checkout or transfer.
• Stock areas: The home location for your items.

Start with a few areas and add more as you become familiar with the system. Ideally, define areas with barcoded location placards or shelf labels.

See Area Setup for details.

Transaction Setup Options

Under System Settings, find the Transaction Setup section. Define additional data to capture for transactions by creating attributes, and review the available rule options:

• Receive New Unit: Default current team as the "Receive For" team
• PO Receiving: Allow receiving items not on the purchase order
• Check Out: Enable moves of selected items to staging area; restrict assignee selection based on facility association
• Check In: Enable assignment of out-of-service at check-in; restrict available units based on team ownership
• Unit Return: Enable assignment of a new handle ID
• Deploy Unit: Enable project assignment
• Order Pick: Enable pick to movable containers