Skip to main content

IFS Cloud has the option to define the load sequence in the Consolidated shipment. The customer’s requirement is to set the sequence in such a way, that the goods which are delivered last to be loaded first. 

 

Even though this is possible, I can see that the load sequence is missing on the “Load consolidated shipment” window. It is not available under “Handling Units to Load” or “Loaded Handling Units”. 

Further, even in the related WADACO Configuration it is missing and there’s no such related item to configure. 

 

If the load sequence is added to the consolidated shipment, then it should definitely be available on the “Load consolidated shipment” and in WADACO. Because, if the load sequence is used, the warehouse worker who uses a scanner should know which shipment to be loaded first. Otherwise, there’s no use of having it just in the consolidated shipment. 

Is this the standard design or is there any other way to achieve this?

Hi,

The Load Consolidated Shipment feature was developed in 24R2 and the associated WaDaCo processes in the release after 25R1. It is a fairly new and comprehensive development. We have not considered the load sequence on the consolidated shipment as per now. I think you might have a point here. Are you more asking for this as information in in the tabs and WaDaCo processes? Or are you also asking for a mode where this is validated so you cannot load a handling unit until all load sequences of the previous one is loaded?

By the way, nice that you look into the very latest development we have done and come with feedback.

Best Regards

Fredrik


Hi Fredrik,

First of all thank you for this quick response! This is what makes the IFS Community so valuable! 
Also I like this new functionality but I think there is something missing to make it work for our customer.

Yashod has raised this question on my behalf as we are working on the same Customer Project where I am in the lead of the Shipment Delivery proces while Yashod is handling the WADACO configuration.

We have an interesting requirement from the customer where the customer is planning the route of a truck. As example the Truck will have to stop at 5 different locations for 5 different customers. 

Once the sequence of the locations to stop is known then the Warehouse should get the information on what which pallets should get loaded first into the truck and which needs to be loaded as last to avoid unnecessary movements during the transport.

So the principle to handle is what is Delivered Last needs to be Loaded First. And vice versa, what is Delivered First needs to be loaded Last. 

There is currently not a function where I am aware of to fill as a user which shipment is delivered on the first stop, which is second, thirth etc. But there is a function available "Load Sequence No” to describe what needs to be loaded first.

So I am planning to use this "Load Sequence No” to let the Warehouse Employee know what to load into the truck and in which sequence it needs to be loaded. 

What I expect from IFS which is currently not possible:

  1. Information of the Load Sequence No to be presented in WADACO. (MUST for my current customer)
  2. Information of the Load Sequence No to be presented in the Load Consolidated Shipment screen in cloud. (Since we have assigned it on the shipments, it should be possible to show which Handling Units must be moved in which order).
  3. Optional: WADACO validations or "Hints/Warnings” like you described. You cannot load a handling unit until all load sequences of the previous one is loaded.
  4. Optional: new functionality to set the order of the delivery of the shipments in the Consolidated Shipmenb. Let's call it Delivery Sequence, then let this Delivery Sequence determine the Load Sequence (in opposite order: Deliver First is Load Last). Having this will make it really clear what the Delivery Sequence is and what the Load Sequence is. 

I am happy to explain more on this when needed, I am open for a Teams call. 


Hi,

I think your feedback is interesting and requirements are valid. Load Sequence No is the concept to use to control this. However as you say there is room for improvement here. Bullet 1 and 2 should not be too hard to add to the core product. The other bullets are also interesting, might take some more time. 

I will mention this to our product management, for potential addition to our roadmap for future prioritization.

Best Regards 

Fredrik 


Hi Fredrik,

Thank you for your comments and bringing my feedback to product management.
Could you please let us know their feedback? 

Best Regards,

Harm


Hi,

We have now added the Load Sequence No field in the Load Consolidated Shipment page, in both the Handling Units to Load tab and the Loaded Handling Units tab. This will be included in 25R2. 

WaDaCo remains will be added to the general roadmap for potential prioritization in the future.

Best Regards

Fredrik


Hi,

We have now added the Load Sequence No field in the Load Consolidated Shipment page, in both the Handling Units to Load tab and the Loaded Handling Units tab. This will be included in 25R2. 

WaDaCo remains will be added to the general roadmap for potential prioritization in the future.

Best Regards

Fredrik

Thank you Fredrik for your reply, that is good news. 
I have also received this information via the Customer's Case. 


Reply