#1214 new

Bug: multiple (forced) shipping methods/calculations

Reported by dleffler | September 21st, 2014 @ 12:02 PM

All our current shipping calculators either apply: a single cost to the entire order regardless of size/quantity (Flat), a single cost based on the total cost of the order (Table Based), a single cost based on the weight of the entire order (UPS/FedEx). And since we can only use one type of shipment per order (as with most ecommerce sites), when 'required/forced' shipping is used, it creates issues such as which shipment type/cost to use.

There is a need for at least one new calculator which allows the admin to assign a cost per item, either custom cost with each item, and/or simply a straight cost per item.

We also need some additional checking/enforcement of 'forced' shipping since you can set/force a shipping method/option, but it may conflict with other items ordered...and the cost/method applied to the order is simply the first/last item added to the cart. This doesn't necessarily mean we'll implement 'multi-shipping' methods (though the code is stemmed in), but may have to warn the customer (before and after selection) and not allow addition to the cart?

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Bug Tracker for Exponent CMS

Shared Ticket Bins

People watching this ticket


Referenced by