A split cargo event happens when a container is left at port while other containers on the MBL depart without it. Often, the left-behind container is moved to a new MBL or booking. OpenTrack detects this and sends you an alert.

For example, let’s say you have an MBL with 3 containers on it. These containers have just been discharged at a transshipment port.

A split cargo event is triggered when:

This can also happen at the port of discharge or at origin.

In all these cases, OpenTrack’s exception monitoring detects the situation and alerts you.

Then instead of scrambling to react, you can dig deeper, understand what happened, and provide a proactive update to everyone watching the shipment.

You look great, the shipment moves more smoothly, and everyone is impressed by how you’re truly on top of your freight. It’s a win-win.

OpenTrack notices when we stop getting data on only one of the containers on a master bill. After 2 days we terminate tracking on the container with the completion reason Not Found at SSL.

Whenever possible OpenTrack also tries to determine whether the container stopped getting data because it moved to a different master bill. In those cases, we terminate tracking with the completion reason Moved to New MBL.

Need to be notified faster than 2 days after the split occurs? We also have an experimental Split Cargo Incident filter which detects when a container is left behind after 24 hours. Feel free to use this instead, though it might be more prone to false positives. We’re actively looking for feedback to hone this.

You can easily configure an email alert that sends a daily summary of split cargo events.

Click the button below to access the Split Cargo Alert template.

Click the Save button in the top right to save it to your My Reports folder. Feel free to customize it to your needs by changing the columns and filters.

Click the Email button in the top right, then click the toggle to activate email notifications.

Set the frequency (daily, weekly…) and add recipients if you’d like others to receive this too.

Now instead of manually scanning for exceptions, you can let OpenTrack’s incident detection automatically surface potential incidents. By focusing on true exceptions only, you save time and energy to spend on more high-value tasks.