Welcome to Vortx Community Forum, where you can ask questions and receive answers from the staff at Vortx and other members of the community.

If you had a user account on our previous forums website, you will need to register a new account here.

Learn more about...

AspDotNetStorefront
DotFeed

Shipping supposed to be free but is charging

We've some items that always need to be shipped Overnight, to achieve this we have set our Shipping Calculation to Use Individual Item Shipping Costs and also set FilterOutShippingMethodsThatHave0Cost to true, hence for those products we set the price only for overnight method and left the other methods set to 0, by doing this we we're able to show only those shipping methods for those specific items.

On the other hand we set the FreeShippingThreshold to 100 and the ShippingMethodIDIfFreeShippingIsOn to 1,2,6 which stands for Ground,Standard Overnight, 2nd Day. However if we set FreeShippingAllowsRateSelection to true it will charge for the shipping even when the total amount is over FreeShippingAllowsRateSelection and we are selecting one of the free shipping methods in ShippingMethodIDIfFreeShippingIsOn  . You may see here how the selected method is being shown as FREE, however it's actually charging for the shipping. If we set FreeShippingAllowsRateSelection  to false it works just fine but we need the customers to be able to select other methods in order to receive the product earlier.

 

asked Mar 24, 2015 in MultiStore by alerancur (180 points)
edited Mar 24, 2015 by alerancur

1 Answer

0 votes

Hi Alejandro,

Yes, we have seen this before, and had to modify the code to reflect the logic correctly. Which version of ASPDNSF are you working on? We have made the updates for earlier versions of 9 ( all before 9.4 if I remember correctly).

Sincerely,
Robert

GoVedia
Enterprise AspDotNetStorefront Development Partner
Web Design, Platform Enhancements & Managed Services

answered Mar 24, 2015 by Robert (3,440 points)
I'm currently working with 9.5 with source code.
It would then appear that code modifications may be necessary. you may want to start with a ticket with support, since this is OOB functionality, and appears to be a bug.
Thanks Robert, I will
...