Where Asset & container tracking fits
05 Service is the operating context.
This page should not feel like an isolated feature sheet. It belongs to a role, a stage, a control, and an outcome in the Haultro operating spine.
24/48/72 hr
Fill prediction windows
Full history
Custody and movement records
Photo evidence
Inspection proof
Tenant-scoped
Registry and events
The challenge
- ! Container identity and ownership drift when inventory lives in spreadsheets.
- ! Teams cannot reconstruct which yard, bay, truck, or customer last held an asset.
- ! Inspections and condition photos get separated from the unit they describe.
- ! Idle containers tie up capital when dwell evidence is not visible.
- ! Overflow decisions arrive too late when fill readings are not forecast.
What it does
- ✓ Maintain a typed registry with asset tag, serial number, ownership, state, and billing eligibility.
- ✓ Record custody-preserving moves between facilities, bays, customers, and field addresses.
- ✓ Capture condition inspections, checklists, notes, timestamps, and photo evidence.
- ✓ Track dwell and idle state using recorded movement history.
- ✓ Store fill readings and generate 24/48/72-hour predictions from recent evidence.
- ✓ Ingest compatible sensor or device records only after a written provider and hardware acceptance.
Inside the module
What your team can work with.
✓Tenant-scoped asset registry with unique asset tags
✓Facility and bay inventory structure
✓Customer, organization, and field custody states
✓Idempotent asset-move records with actor and timestamp
✓Inspection checklist, condition, notes, and photo URLs
✓Lifecycle dates from acquisition through retirement
✓Billing-eligibility and occupancy-period records
✓Dwell and last-moved evidence
✓24/48/72-hour fill predictions from real readings
✓Condition-based maintenance handoff
✓Signed outbound webhooks for accepted external synchronization
✓Explicit provider and hardware availability states
Asset & container tracking · Connected to the work on the groundRecover idle steel
Use recorded custody and dwell evidence
Every move records who acted, when it happened, and the resulting custody and billing state. Teams can review idle assets without treating missing GPS or scan data as a confirmed location.
Find idle assets
Review idle-since and last-moved timestamps by facility, bay, customer, or state.
Reconstruct custody
Follow the idempotent movement history from the registry record.
Review condition
Use inspection notes, checklists, and photos tied to the exact asset.
Connected across the platform
One source of truth.
Routing & dispatch
Recorded bin assignments and fill evidence help dispatch choose work without claiming automatic geofence or scan events.
Disposal & weight
Container and job associations connect recorded weight tickets to the correct service context.
Scheduling & jobs
Registry state and fill predictions support human-reviewed pickup and swap planning.
Billing & invoicing
Billing eligibility and occupancy periods preserve the evidence used by rental and metered workflows.
How it works
Adopting asset & container tracking.
01
Register the asset
Create or import the asset tag, serial number, type, ownership, and initial custody state.
02
Record each move
A tenant user records the from and to facility, bay, customer, address, custody, and billing state with an idempotency key.
03
Inspect and read
Attach condition evidence and ingest accepted fill readings from configured devices.
04
Forecast and review
Haultro calculates 24/48/72-hour fill values and surfaces dwell evidence for dispatch review.
Standards & compliance
Built in, not bolted on.
Chain-of-custody evidenceCondition and inspection audit history
FAQ
Questions, answered.
How are passive containers tracked today?
They use the registry, recorded custody moves, assignments, inspections, and service history. The current production contract does not claim RFID or QR field scanning, automatic geofence movement, or physical-scan reconciliation.
How does fill prediction work?
Haultro derives 24/48/72-hour values from recent tenant fill readings. A prediction remains evidence-bounded; missing or stale sensor data is not replaced with a fabricated reading.
What sensors and hardware are supported?
The platform has device and fill-reading ingestion paths. A named sensor or hardware combination is supported only after the customer device, credentials, payload, cadence, and live acceptance have been verified.
Does Haultro automatically flag stolen containers?
No. Teams can review last-known custody, last movement, idle state, and service history, but automatic lost or stolen classification is not part of the current production contract.
Get started
See asset & container tracking on your routes.
We'll tailor a demo to your fleet and the business you run.