Use case
In the warehouse of pallet network depots, there are 2 main ways of working for loading the delivery vehicles:
1/ the inbound trucks (”trunks”) arrive at the depot, and the FLT (fork lift truck) drivers immediately take the pallets of the trunks to put them on the delivery vehicles;
2/ the trunks remain loaded and the FLTs load the delivery vehicles by collecting the pallets one by one from the trunks they’re on
To support the second use case, it’s important that the warehouse operators know where to search for the pallets (on which trunk are they?).
Therefore we’ve added the last pallet location to the LOADING SHEET document template.
Loading sheet vs trip sheet (driver manifest)
The loading sheet and the trip sheet are 2 very similar documents in terms of layout but they have a different use case:
The loading sheet is designed to be used by the warehouse operator to load the truck
The driver manifest is designed to be used by the driver on their trip
They contain similar information but the order of the document is reversed: the loading sheet contains the pallets in reverse order of delivery, as a pallet that needs to be delivered last should be loaded first.
While they are similar in layout, the available information in the template engine is not necessarily the same, as mentioned the pallet locations are currently ONLY available in the loading sheet.
There also is an alternative layout of the loading sheet that does not resemble the trip sheet that much; the pallet locations are also NOT available on this one:
When the information is filled in
Often when generating a loading sheet the column remains empty, even if you configured it correctly. E.g. in the example below for some orders it’s filled in, for some it’s not:
It’s important to realise that pallets go through a number of statuses. This can be seen in the TMS when you open the order detail:
The information shown in the loading sheet is the TRUNK THE PALLET IS ON AT THE MOMENT THE LOADING SHEET IS GENERATED.
This means that, if at that moment the pallet is not physically present on a trunk, the information column stays empty.
E.g. in the example above:
for the order(consignment) the pallet is delivered (”delivery signed”) which means it’s not at the delivery depot and thus also does not have trunk information.
for MWT1698 the pallet is still on the trunk (”delivery depot scanned in”) which means it is waiting to be unloaded and the trunk information thus is present:
