These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Container Tracking
- Integrations
Integrations
Plan the outside sources that supply vessel updates and operating evidence.
- SCM with Container Tracking
- Vessel event source
- Fleet authority source
- Document source
- Commercial system
Systems to connect
- Vessel event source. Decide how carrier or tracking updates reach the booking’s vessel and ETA details. Preserve the source and time of each update in the connected process.
- Fleet authority source. Decide who supplies driver eligibility and vehicle readiness, including the external identifiers recorded on those records.
- Document source. Bring delivery photos or documents into record attachments with a title, visibility and evidence type.
- Commercial system. Set up a separate carrier invoice and contract process if the team needs demurrage calculation or settlement beyond the recorded load amount and booking free days.
How connections are governed
Name an owner for each source and agree how errors reach the Transport Supervisor. A provider message should be reconciled with the selected load and booking before it changes an operating record. Retain the receipt and its operation key for a failed action so a retry cannot silently duplicate an effect. Test a changed ETA and a failed update during the first operating cycle.
Set up SCM with Container Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.