Posted by cyaneo on October 26, 2009 at 10:18am
| Project: | Ubercart 2 VAT support |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi
First thank you for this highly needed module, so now I can enter my Prices inkl. VAT!
BUT this does not work on the options of attributes - there I have to enter the price excl. VAT.
Comments
#1
VAT-inclusive attribute options work when the option price is being set for a specific product or product class. However this cannot currently be done for default option prices, as until the attribute is attached to a product or class, it is not known whether the product will eventually be taxed or not - if these prices were entered inc VAT but you then added them to a product that did not have VAT applied, the price would be incorrect. This is further complicated by countries that have more than one tax to be applied.
I guess in a lot of cases all products in a store will be taxed, so I could add an option to "Assume default attribute option prices will be taxed". I will put this on my to-do list for the module.
#2
Thank you!
#3
#4
Could the option be extended also to shipment quote prices and additional payment fees enabled by uc_pma module as well? VAT is applied for shipping fees at least in all Scandinavian countries.
Thanks!
#5
Shipping and uc_pma has already been requested in #489198: Allow inputing of VAT inclusive prices, now marking this as duplicate so all "Inclusive VAT price field" requests can be kept in the one issue.
#6
As per longwave's comment in #1:
Allowing attributes to be entered inclusive of VAT is great, however in most stores the fact that only the default attributes must be entered in exclusive of VAT is pretty confusing for end users.
Attached is a patch to implement a setting to allow default attribute prices to be entered inclusive of VAT.
#7
Here's a reroll of #6 to keep up with the changes in the dev version.
#8
Committed with a few small changes, thanks for the patch.
#9
Great, thanks longwave.
_uc_vat_attribute_description() make perfect sense, and the fieldset around uc_vat_default_attributes_inclusive was certainly debatable.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.