Feature Requests

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.

If an event is expected (eg vessel arrival) but does not occur in T49 within a reasonably expected timeframe, have some kind of alert/notification that the data might be inaccurate. This will help build trust in the data so users know if it should be regarded with skepticism and they may need to seek answers elsewhere.

display a flag to viewers labeling suspicious data if: "report issue" button has been pressed our internal automatic conformance suggests that the data might be incorrect (e.g. ATA preceeds ETA by too much, LFD is too far out, etc)

Identify which pool a chassis belongs to for containers at the destination terminal. A chassis can belong to a public or a private pool. Pools can be identify via https://gierregistry.com/

Provide transparency to customers which carriers and terminal data sets are available, sometimes available, and not supported