Skip to main content

You and Sallaum Lines, looking at the same shipment

Sallaum Lines runs its whole network on Logisoft. Book on Logisoft too and there is nothing to send them and nothing to check against them, because you are both working the same shipment. Not two systems kept in step. One.

Sallaum Lines

Where the work goes

Nothing has to travel between you

This is not a faster connection between two systems. It is the absence of one. The messages your team sends the line, and waits on, stop existing rather than getting quicker.

Two systems

Your system and the carrier's system as two separate boxes, with five messages passing back and forth between themYouThe linebookingconfirmationwhere is it?draft B/Lamendment

Every arrow is something somebody sends, and something somebody waits for. Each one is a chance for the two sides to end up holding different answers.

One shipment

A single shipment in the centre with you, Sallaum Lines, the terminal and the agent each attached directly to itOne shipmentBK-48812YouSallaumTerminalAgent

Sallaum Lines already runs on Logisoft. Join them and there is nothing in the middle: you, the line, the terminal and the agent are all on the same shipment.

Nothing to send

The booking you enter is the booking the line works from. Nothing is exported, emailed, or typed in again at their end while you wait to hear back.

No delay

When the line moves a car forward, your shipment moves forward. There is no overnight update and no lag, because there is no second copy to catch up.

Papers in place

The draft B/L and the shipping documents sit with the cars they cover, where both sides can see the same version, instead of travelling around as attachments.

One version

Your booking and theirs cannot drift apart, because there is only one. Nothing to compare on a Friday, and no argument about whose list is right.

The questions you ask the line every week stop needing to be asked

Has it been received. Is it on the vessel. Has the B/L been cut. You are looking at the same shipment they are, so the answer is already on your screen.

Cars being driven off the stern ramp of a vehicle carrier while stevedores walk alongside on the quay
BK-48812
WVWZZZ1KZ8WLoaded
JTDKN3DU1A0On quay
WBA8E9105GKAwaiting

One booking. Three cars, three stages.

Your customers can see it too

Give a shipper their own login and they stop ringing you for updates, which removes the second set of chasing emails nobody counts.

Car by car, not booking by booking

Forty cars on one booking will sit at different stages. You see each one, which is what you need when a customer asks about theirs.

No overnight wait

Nothing runs on a schedule between two systems, because there is only one. What the line does now, you see now.

A terminal clerk with a handheld tablet walking rows of finished vehicles in a port yard at sunset
ConsigneeChanged
Sallaum LinesCarrier
Antwerp terminalTerminal
Receiving agentAgent

Nobody was emailed.

Change it once, and it is changed for everyone

Amend a party, a description, a customs detail or a car. There is no second update to send and no window where your paperwork and the line's disagree.

The terminal sees it as well

Terminals, agents and brokers on the shipment work the same one, so a change does not have to be repeated down the chain by email.

Nothing to reconcile

There is no end-of-week comparison between your bookings and the carrier's, because they were never two lists in the first place.

You still control your own side

Sharing a shipment is not sharing a company. The line sees the shipments it carries for you, and nothing else about your business.

What a shared shipment takes off your desk

Typing it twice

A booking entered in your system and again in the carrier's is two chances to get a VIN wrong and one guaranteed argument about which list is current.

Chasing for status

Emailing an agent to ask whether a car has been received, loaded or cut off stops being part of the job when the answer is already in front of you.

Asking for documents

The draft B/L does not have to be requested and waited on. It sits with the cars it covers, and both sides are reading the same version of it.

Repeating amendments

Change a party, a description or a customs detail once. No second message to send, and no spell where the two sides hold different versions.

Weekly reconciling

No comparing your booking list against the carrier's to find the three that do not match, because there is only ever one list.

Re-explaining the shipment

Terminals, brokers and receiving agents work the same shipment, so it stops being described again from scratch at every handover.

Two systems, or one shipment

FeatureYour system, separate from the lineOne shipmentBoth of you on Logisoft
Where the booking livesIn two placesIn one
Getting it to the lineExport, email, or type it againNothing to send
How current the status isAs current as the last update someone sentIt is the same shipment
Getting the draft Bill of LadingAsk for it, then waitIt is already there
Amending after bookingChange it in both placesChange it once
Checking the two sides matchA weekly jobNothing to check
Something to build and maintain
Terminals and agents on the shipmentEmailed inAlready on it

Frequently Asked Questions

Sallaum Lines is a trademark of its owner, used here only to identify the carrier described. Logisoft is the software provider to Sallaum Lines, not their agent, and this page is published by Logisoft rather than on their behalf. Nothing here alters the terms on which Sallaum Lines carries cargo, and the capabilities described are Logisoft's own, checked against our product source. Carriers change their systems and their terms, so confirm anything decision-critical with the line directly.

Still checking your bookings against the line's?