Container Movement Tracking: What Enterprise Logistics Mobile Apps Need

Container tracking problems look like technology problems. They are actually custody problems. A container that is lost is not lost because there is no GPS on it. It is lost because there is no clear record of who last had custody, when they transferred it, and whether the receiving party confirmed the transfer. GPS tells you where the container is. A custody chain tells you who is responsible for it.

Enterprise logistics operations that invest in GPS and IoT tracking without building the custody chain record end up with a map of container locations and no accountability for how they got there. The disputes that follow - between shippers, carriers, terminals, and receivers - cost more to resolve than the technology would have cost to build correctly.

Tracking vs. visibility

A container GPS device tells you where the container is. It does not tell you who has it, how long it has been there, or whether it should be somewhere else by now. Those questions require a custody chain - a sequential record of every handoff, every scan, and every dwell period.

The difference matters operationally. An operations manager looking at a map of container locations cannot answer the questions that drive decisions: Is this container overdue at its next destination? Who accepted custody at the last handoff? Was the condition checked? Is demurrage accruing?

Container visibility requires the GPS track plus the custody record plus the schedule comparison. The mobile app is the tool that captures the custody record at each handoff. The GPS device provides passive location data. The mobile app - used by drivers, terminal operators, and yard managers at the point of transfer - provides the active custody record.

Operations that invest in passive tracking without building the active custody capture end up with a map and no chain of accountability.

The custody chain

A custody chain is a sequential record of every party who has had responsibility for a container, from origin to destination. Each entry in the chain contains: a container identifier, a timestamp, a location, the party accepting custody, the party transferring custody, and a condition note.

The mobile app builds this chain by capturing a scan at each transfer point. The scan triggers a custody transfer record that is written to the backend immediately - or queued locally if connectivity is unavailable and synced when it returns.

The condition note at each handoff is the data point that resolves damage disputes. A container that arrives at its destination with a damaged seal and no condition record in the custody chain is a dispute with no resolution path. A container that arrives with a damage note at the port entry scan - recorded by the terminal operator on a mobile device with a photo attached - is a dispute with a clear answer: the damage was present when the container entered port, and the party who accepted custody at that scan is responsible.

Building condition capture into the handoff flow - as a mandatory step, not an optional field - is the difference between a tracking system and a liability management system.

Dwell time and why it matters

Demurrage is the fee charged when a container occupies a terminal, port, or depot location beyond the free storage period. The fees are substantial - typically $150 to $500 per container per day at major ports, accruing automatically once the free period expires. Large logistics operations manage thousands of containers simultaneously and pay significant demurrage charges each month for containers that sat too long without an alert triggering intervention.

A container tracking app that captures arrival time at each location and compares it against the scheduled free period generates an alert when dwell time reaches a configurable threshold - typically 70 to 80 percent of the free period. The alert goes to the party responsible for arranging the next movement: the freight forwarder, the shipper's logistics team, or the carrier. The alert fires while there is still time to act.

The alert is only useful if it is actionable. An alert that says "container XY123 at Los Angeles Port, dwell time 36 hours" is not actionable. An alert that says "container XY123 at Los Angeles Port, 36 hours of 48-hour free period elapsed, $380/day demurrage begins in 12 hours, contact freight forwarder for pickup arrangement" is actionable. The mobile app that generates the alert should include the next step, not just the data point.

The exception capture requirement

Exceptions are the events in a container's journey that deviate from the plan: a damaged seal, a customs hold, a missed handoff window, a container rejected at inspection. Each exception is a potential liability event. The question is whether the liability is documented at the time of the event or reconstructed from memory after a dispute.

A container tracking app that includes an exception capture flow - a mandatory step when a scan reveals a condition that deviates from the expected state - documents the exception at the point of discovery. The exception record includes: the nature of the deviation, a photo, the timestamp, the location, and the party who discovered it.

The exception record is the evidence in every subsequent discussion about who is responsible for the deviation and what it cost. An operation that captures exceptions consistently, at the point of discovery, in a standardized format, has a defensible position in every dispute. An operation that reconstructs exception history from emails, WhatsApp messages, and memory does not.

What to build vs. integrate

Container tracking platforms - TradeLens, project44, FourKites, and others - provide real-time container location data aggregated from carriers, terminals, and shipping lines. They are the right starting point for operations that need carrier-agnostic visibility across multiple shipping lines without building their own data connections.

The mobile app layer sits on top of the platform. The platform provides the passive tracking data - vessel positions, terminal scans, carrier milestone updates. The mobile app provides the active custody record - the handoffs that happen between carrier milestones, the condition checks, the exception captures, and the dwell time alerts that require someone to act.

Build the mobile app for the custody events that the platform does not capture: the yard transfer at the inland depot, the gate-in scan at the cross-dock, the handoff between the container drayage driver and the warehouse receiver. These are the gaps in the platform data. They are also the gaps where disputes originate.

Integrate the platform for the carrier milestone data. Build the mobile app for the human-mediated handoffs. The two together produce a complete custody chain.