It was because Shipping is usually something where multiple options aren't presented to the user with separate fields.
When we pass shipping to a payment gateway, it's a single field that gets passed. When we display Shipping as part of the formatted order data it's a single line item, etc.
So we locked it down to only one Shipping field per form.
So if you add multiple Shipping Fields and don't use conditional logic properly so that multiple Shipping Fields are then presented to the user, we'd have to decide how to handle that from both a payment gateway add-on perspective as well as how to present that in the order display in the entry details as shipping is currently (and in most ecommerce applications) a single line item.
It isn't something i've seen come up before. I see where what is described has value, but we'd have to look at all the scenarios and see how that is handled when a user doesn't properly configure things so that only a single Shipping field is selected.
We can discuss it further and see how we can enhance the functionality to support something like this, but for now the only solution is to incorporate shipping as a Product Field rather than using the Shipping Field itself.
Posted 10 years ago on Wednesday February 15, 2012 | Permalink