Terminal49
Create
Log in
Sign up
Roadmap
Feedback
Improvements
157
Changelog
Boards
Improvements
Feature Requests
API Features
Dashboard Stats
Daily Digest
Powered by Canny
Improvements
Description
Category
Select a category
Dashboard UX
API
Terminal/Carriers
Data Reliability
Uncategorized
Showing
Trending
Sort
Trending
Top
New
Filter
Under Review
Planned
In Progress
Complete
posts in
All Categories
All Categories
Dashboard UX (25)
API (9)
Terminal/Carriers (117)
Data Reliability (9)
De-duping containers
I spoke with Centric Brands today and we are having issues with being charged 5 or more times for the same container because of uploading multiple BOLs with the same container number. This is because they don't want to miss anything for these consolidated shipments (to save on costs). This is leading to current billing disputes. Going forward we should not charge for the same container many times. We can probably filter this out by assuming the same container on the same sailing (even if several BOLs) is only a tracking request for 1 container.
0
4
add Estimated Discharge Date
Right now Terminal49 shows only the actual discharge date, not the estimate (when it is available from the carriers). Some customers use Estimated Discharge for planning purposes so want to see that via Terminal49.
0
1
Capture when container starts next cycle.
Carriers do not always return the final empty returned milestone for each container in it's lifecycle. When this happens we are unable to update the consumer or stop checking the container status at the shipping line. Once a container is picked up we can check the container status individually at the shipping line instead of in the context of the BL/Booking we will be able to see when a new journey (empty out) has begun and we can create a new event like. 'Lifecycle Ended' 'Journey Terminated' .
1
·
planned
5
Track by House BL
Track by house Bill of Lading
0
12
auto-update shipments when a container splits off a booking
occasionally, a container will split off from its original booking mid-journey. T49 should automatically update shipments so that the departed container does not show up anymore (and possibly create the new booking to which the container relocated).
0
6
Extend time frame in stopping shipment tracking after not receiving updates from the terminal
2
4
Don't send POD events for Rail containers
rail containers are not actually available for drayage carriers to pick up until they arrive at the rail terminal, so there is no value in container availability/LFD at the port of discharge.
0
3
Powered by Canny