Feature request: reorganize tax data structure
Reported by dleffler | September 20th, 2014 @ 01:12 AM | in 2.3.1 (closed)
It appears our tax data table structure is not conducive to multi-area taxes. Though we have most of the non-US tax regions code fixed, the way we manage tax classes/zones/rates isn't logical for assigning a 'tax class' to a product and then pull the correct tax rate based on the shipping address.
Comments and changes to this ticket
-
dleffler September 20th, 2014 @ 03:57 AM
- State changed from “new” to “resolved”
While not a true db table restructure, we now manage tax 'rates'. A tax rate is assigned a tax class and tax zone therefore a tax class (assigned to a product) can have multiple tax zone/rates.
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.
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
dleffler
expNinja