Skip to main content

Container Move Types

Defines container move types and explains the different label options you can choose when using the Move container functionality in Inventory.

Updated today

This feature is currently in an open beta. If you run into any issues or have feedback, reach out to support with the blue chat bubble in your Hauler Hero account or support@haulerhero.com.


Want to learn more? Check out our Beta Inventory documentation.

Container move types provide a standardized way to classify and record every change in a container’s location and status. This functionality creates a detailed and auditable transaction history for each asset, which is essential for accurate inventory management. By logging moves either automatically through driver actions or manually in the office, you gain full visibility into your asset lifecycle and improve overall operational efficiency.

What is a Container Move Type?

A container move type is a label that classifies the reason for a container’s change in location or status. Using these types helps you maintain an accurate and detailed history for each asset in your inventory, from its initial order to its final decommissioning.


What are the Different Container Move Type Options?

A “move” in your inventory doesn’t always mean a change in physical address; it can also refer to a change in the container’s status or its stage in the operational lifecycle. Each move type creates a transaction record, giving you a complete audit trail for every container.

  • Order: Use this type when you purchase a new container from a manufacturer. This logs the container in your inventory system, but it’s not yet physically arrived at your yard.

  • Repair: Use this to indicate that a container is damaged, out of service, and undergoing maintenance or repair.

  • Receive: This marks the physical arrival of a newly ordered container at your facility, making it officially part of your available inventory.

  • Load: This signifies that a container has been loaded onto a truck, typically in preparation for delivery or transit.

  • Deliver: This move type is used when a container is delivered to a customer’s service location.

  • Remove: This is used when a container is picked up from a customer’s service location and returned to your yard or another site.

  • Confirm: This type is for logging minor repositioning of a container that is already on-site without a full-fledged delivery or removal action. For example, site A to site B, but same customer.

  • Decommission: This permanently removes a container from your active inventory, typically because it is too damaged to be repaired or has reached the end of its useful life. The container is no longer in use.


Why Tracking Move Types Matters

Properly tracking move types provides complete visibility into the lifecycle of each container. This detailed transaction history, or ledger, is crucial for maintaining accurate inventory counts, understanding asset utilization, and ensuring operational transparency.

This feature is especially valuable for office staff who need to log a historical move after the fact. For example, if a driver’s tablet was offline and they couldn’t log a delivery in the field, an administrator can manually create the move transaction to keep the container’s history accurate.


How Container Moves Are Logged

Container moves are logged in two primary ways, ensuring your records are always up-to-date:

  1. Automatically: Most moves are logged automatically through driver actions completed in the field via the tablet app. When a driver completes a task like a delivery or removal as part of a work order, the system creates the corresponding move transaction.

  2. Manually: You can log moves manually using the Move Container dialog in the web application. This method is ideal for administrative adjustments, correcting records, or logging actions that happen outside of a standard work order, such as receiving a new container from a supplier or decommissioning an old one. See How to Manually Move a Container.

Did this answer your question?