By using this website, you agree to our Terms of Use (click here)
Hi
First of all, thanks Tim for putting effort in setting up this excellent forum! Well done! Looking forward to the coming Distribution forum=)
Now to the question, posted this same question in the LinkedIn group aswell, but didn't seem to get any replies, so I give it a try here instead.
The case here is that we want to have automatic freight calculation based on the weight of the order, so we want to setup a Ship via code(Non-integrated) where the freight cost should be calculated as follow on the sales order(no packages/boxes are included):
- If total weight of the items on the sales order is 0-5kg, cost should be 5$
- If total weight of the items on the sales order is 6-10kg, cost should be 8$
- If total weight of the items on the sales order >10kg, cost should be 10$
For the freight calculation, we do not want to take volumes into account, only weight. The items do however contain volumes for other reporting purposes.
The easiest way to set this up I thought would be to use a Ship via code with a Net calculation, no base rate and a table of 3 lines in the Freight rates tab: 0 kg, 0 volume(liter) - 5$, 5 kg, 0 volume(Liter) - 8$ and 10 kg, 0 volume(Liter) - 10$
This works fine as long as the item(s) doesn't have a volume, but as soon as we specify a volume on the item the calculation goes off and always takes the highest cost. How can we make sure the freight calculation is only based on weights, even when we have a volume on the item? Is this not possible?
Please let me know if you need some more information and/or print screens.
Hey VJW,
You're very welcome.
I haven't had the time to create posts for the Distribution modules yet, but, since your question is related to the Distribution module, I figure, hey, what the heck, let's just make your question the first one. So I created the Distribution modules forum and moved your post there (I hope you don't mind).
I should be able to take a look at this tonight while sitting in the rocking chair in the kids room as they fall asleep. That's my AUG Forums time 🙂
Keep in mind that there are two things at play here:
Freight Cost can be seen in the Freight Cost field on the Totals tab of the Sales Orders screen
Freight Billed can be seen in the Freight field on the Totals tab of the Sales Orders screen.
Let's just focus on Freight Cost for the moment.
I created a test Ship Via that looks like this on the Freight Rates tab of the Ship Via Codes screen:
My test item looks like this on the Packaging tab of the Stock Items screen;
Then I create a Sales Order and populate the following in the Shipping Settings tab of the Sales Orders screen (note that I'm leaving Shipping Terms out of the equation for now):
If I put my test item on the sales order for a quantity of 1, this is what the Totals tab looks like:
That looks correct to me because my 2.72 weight meets the criteria for the first rate on the Freight Rates tab of the Ship Via Codes screen.
Then I increase the sales order quantity to 2 and my Totals tab looks like this:
This looks funny to me because I was expecting the Freight Cost and Freight fields to go up to 2 based on the fact that the Order Weight is 5.44 which is more than 5, enough to qualify for the second rate on the Freight Rates tab of the Ship Via Codes screen.
Then I increase the quantity of my order to 19 and my Totals tab looks like this:
Then I increase the quantity of my order to 20 and my Totals tab looks like this:
Finally, I was able to trigger the second rate of 2, but only when the Order Weight is greater than or equal to the Weight on the Freight Rates tab of the Ship Via Codes screen AND the Order Volume is greater than or equal to the Volume on the Freight Rates tab of the Ship Via Codes screen.
The key word in that previous sentence is AND. At least, that's what the formula appears to be.
But then I tried another scenario by lowering the Volume requirement to .25 on the second line of the Freight Rates tab in the Ship Via Codes screen:
I do another order with the same information as before, but now down to a quantity of 1 and the Totals tab looks like this:
That's weird because, even though the order doesn't meet the Weight criteria, it still gets the rate of 2 based on meeting the Volume criteria.
Based on this test, it seems to me like the entire calculation is based on Volume and not on Weight.
So, let's try removing the Volume from the Packaging tab on the Stock Items screen like this:
Now this is what the Totals tab looks like for a quantity of 1 (ah, much better):
And the Totals tab for a quantity of 2 (perfect!):
Based on this, it seems to me like the presence of a Volume number on the Packaging tab of the Stock Items screen is what is causing the problem with the Freight Cost calculation.
Three Ideas:
1. Move your current volume data out of the Volume field on the Packaging tab of the Stock Items screen and into the Attributes tab on the Stock Items screen.
2. Open a support case and find out if this behavior of the Volume "taking over" the calculation is intended or if it really should be an "either or" type of calculation where either the Weight or the Volume (not just the Volume) should trigger the next freight tier on the Freight Rates tab of the Ship Via Codes screen. It definitely looks funny to me.
3. Look into using Shipping Terms to calculate the Freight Billed correctly since that's what we really care about anyways. But I'm kind of doubtful that this will work. Plus, I've been typing too long anyways 🙂
I'd be interested to hear what you find out from opening a support case.
Hi
Received a reply on this:
At the moment it is not possible, the system chooses the highest cost based on volume or weight.
In your case the system chooses the highest cost because the order volume is more than 0.
Thanks for following up with the explanation. Maybe you just need a customization to take Volume out of the calculation equation. Or use a Stock Item attribute.
Hello, I know this post was from a long time ago, but I was wondering if there are any updates on this? I am experiencing the same issue in 2020 R2. Thanks!