Movable containers are tracked in the system as serialized units with a unique Handle ID. Uses for movable containers include:

• Grouping quantity-tracked items to treat them as a single serialized unit.
• Grouping units for shipping and transfers.
• Grouping units for projects to move as a single unit.

Container Templates

Container templates are defined under the settings area.

• Template ID: The general ID for the container (e.g., box, carton, pallet).
• Display Name: How the container template appears when creating new containers. Can be the same as the Template ID.
• Description: Optional field for additional details about the container.

Container Rules

The following rules control how containers are tracked in the system.

Can hold hazardous material: When checked, item units marked as hazardous can be added. If unchecked, hazardous items cannot be added to this container type.

Can combine items with different attributes: Check this to allow item units with different attributes in the same container. Designed for lot-tracked items to support isolating the same item code and lot to a container. In most cases, this should be checked.

Can combine items with multiple owners: Designed to support isolating items owned by different customers when managing customer-owned inventory. If not managing customer-owned inventory, this is typically checked.

Restrict contents to a single item master: Designed for managing quantity-tracked items received and stocked in a box or carton on the shelf. Enables selecting a container that holds a specific item. Containers for stocking may have this checked; containers for staging, shipping, or transfers typically do not.

Can hold other movable containers: Often checked for larger containers (pallets, crates) that support nesting smaller containers. When unchecked, these containers will not be available for selection when moving or adding containers to shipments or transfers.

Available as a Pick To container for Pick Order: When completing a pack as part of an order pick, only existing containers with this rule are available. When creating a new container on the fly, only templates with this rule enabled can be selected.

For internally owned units, track ownership by team versus organization: For customer-owned items received to a container, the container inherits customer team ownership. For internally tracked items owned by a team, this rule matches container ownership to its items' ownership. Container-level ownership restricts additions to units with matching ownership. If unchecked, no ownership logic is applied at the container level.

Can be directly shipped: When a shipment includes multiple containers, a Shipment ID is required. The shipping transaction supports shipping a single container directly, and that container must have this rule checked.

Allow for Update Unit transaction: When checked, the container is available in the Update Unit transaction. Most commonly used to set weight and dimension data, which is often unknown during container build and recorded as a final step before shipping.

Enable project allocation: When enabled, users can assign a project to the container. Only items allocated to that project (or with no project allocation) can be added. The project assignment is not required when creating a container; the rule simply enables the option.

Weights and Dimensions

If tracking weights and dimensions for containers, complete this setup as part of the template. Define the unit of measure and, if known, the tare weight and default dimensions. These values are inherited by new container units.

Define which transactions have weight and dimension fields enabled:

• On Create: Capture tare weight, gross weight, and dimensions.
• Build Container: Capture gross weight and dimensions for the container being built.
• Added to Build Container: Capture when a container is added to another container being built.
• Added to Build Shipment: Capture when a container is added to a shipment.
• Container being directly shipped: Capture at shipping for a single container shipped without a Shipment ID.
• On Update transaction: Capture or update at any time using the Update Unit transaction.

Container Attributes

• Static attributes: Assign attributes as part of the template setup that apply to all containers of this type.
• Unit attributes: Define attributes to capture when container units are created. Edits can be made through the container edit function.
• Transaction attributes: Define data captured for the container as part of a transaction. The data is associated with the container unit but not directly assigned as an attribute. Use for values that may be captured at different times with different results: for example, a "condition" attribute captured throughout the container's lifecycle to build historical data.