10/11/04
My client's e-commerce site calculates shipping charges based on the
dollar amount of purchase. Shipping is free if customers order $200 or more
at one time, otherwise, the cost of shipping is automatically calculated
from rates for dollar ranges we have set up in the back office.
We have discovered that if a purchase total (not including tax) is
$19.99, the shipping charge is shown as $0 (it should be $5.49).
It doesn't matter if just one product is $19.99 or a combination of
products is $19.99. The shipping charge is calculated by the shopping carg
as $0.
$19.99 is the break point between shipping charge ranges; other range
breaks are $9.99, $39.99, $59.99, $79.99, $99.99, $199.99. But the $0
shipping charge only comes up for the $19.99 amount. I don't know if the
apparent error at $19.99 just coincidentally is at a break point or not.
Has anyone else discovered this "bug"? Any ideas?
Thanks!
Steve Howse
Howse Design
jshowse@qwest.net
ShopSite 7 Pro: Shopping cart bug?
-
- Posts: 2572
- Joined: Fri Aug 04, 2006 12:02 pm
- Location: Anywhere
- Contact:
Re: ShopSite 7 Pro: Shopping cart bug?
Try giving the 'break point' a higher decimal precision, like 19.999,
and see if that helps.
-Loren
J. Stephen Howse wrote:
and see if that helps.
-Loren
J. Stephen Howse wrote:
10/11/04
My client's e-commerce site calculates shipping charges based on the
dollar amount of purchase. Shipping is free if customers order $200 or more
at one time, otherwise, the cost of shipping is automatically calculated
from rates for dollar ranges we have set up in the back office.
We have discovered that if a purchase total (not including tax) is
$19.99, the shipping charge is shown as $0 (it should be $5.49).
It doesn't matter if just one product is $19.99 or a combination of
products is $19.99. The shipping charge is calculated by the shopping carg
as $0.
$19.99 is the break point between shipping charge ranges; other range
breaks are $9.99, $39.99, $59.99, $79.99, $99.99, $199.99. But the $0
shipping charge only comes up for the $19.99 amount. I don't know if the
apparent error at $19.99 just coincidentally is at a break point or not.
Has anyone else discovered this "bug"? Any ideas?
Thanks!
Steve Howse
Howse Design
jshowse@qwest.net
Re: ShopSite 7 Pro: Shopping cart bug?
It is probably caused by a rounding error or an inexact binary to
decimal conversion. Try adding an extra 9 to the end of each of your
limits, i.e 19.99 would be entered as 19.999.
I couldn't reproduce the problem with a single product of 19.99 but I
could with 3 products, 13.33, 3.33, 3.33. Adding the extra 9 at the end
of the limit resolved the issue.
Jim
J. Stephen Howse wrote:
decimal conversion. Try adding an extra 9 to the end of each of your
limits, i.e 19.99 would be entered as 19.999.
I couldn't reproduce the problem with a single product of 19.99 but I
could with 3 products, 13.33, 3.33, 3.33. Adding the extra 9 at the end
of the limit resolved the issue.
Jim
J. Stephen Howse wrote:
10/11/04
My client's e-commerce site calculates shipping charges based on the
dollar amount of purchase. Shipping is free if customers order $200 or more
at one time, otherwise, the cost of shipping is automatically calculated
from rates for dollar ranges we have set up in the back office.
We have discovered that if a purchase total (not including tax) is
$19.99, the shipping charge is shown as $0 (it should be $5.49).
It doesn't matter if just one product is $19.99 or a combination of
products is $19.99. The shipping charge is calculated by the shopping carg
as $0.
$19.99 is the break point between shipping charge ranges; other range
breaks are $9.99, $39.99, $59.99, $79.99, $99.99, $199.99. But the $0
shipping charge only comes up for the $19.99 amount. I don't know if the
apparent error at $19.99 just coincidentally is at a break point or not.
Has anyone else discovered this "bug"? Any ideas?
Thanks!
Steve Howse
Howse Design
jshowse@qwest.net
Re: ShopSite 7 Pro: Shopping cart bug?
To Jim and Loren,
Thanks for your quick responses. Adding the extra digit to the range
seems to work.
Thank you both very much!
Steve Howse
Thanks for your quick responses. Adding the extra digit to the range
seems to work.
Thank you both very much!
Steve Howse