Feature Requests

Allows users create a separate tracking request for single container that was initially tracked using a different shipment number by mistake.

If a Tracking Request is created with incorrect information, there is no way currently to update that request or create a new request for the same container# with correct information until the pending request times out. Need an ability to cancel the request in pending status so a new tracking request for the same container# can be created.

DHL, COSLog, Kintetsu, ECU, APL Logistics, Hyundai Glovis, Schenker, CH Robinson, Apex Maritime, Expeditors and Damco

Ability to link a shipment to your customer (consignee/account) * Ability to filter a shipment by one or more customer * Filter containers and other reports by customers * Filter dashboard by customers * See All / Add & Update customers

Show current geographic location of a vessel in transit and the path between locations and ports of call (AIS data). Show planned arrivals, vessels which have arrived/berthed/discharged, and container volumes by lane and by date.

knowing the correct ERD (earliest return/receiving date) and cutoff of a booking is impossible to know and vital to every shipper. it varies for every port and terminal. this data (BEGIN RECEIVE and CARGO CUTOFF) lives behind terminal logins in the export flow

comparing carriers to see which have more delays, better on-time performance, etc.

Customer wants to know which ports are more congested and which ones are more efficient, so that they can change where to send their shipments to avoid delays.