Resolving address book / tax issues for Canada [#75339]

Attached is a module and patch that we use internally to make the Ecommerce system more Canadian. This is what it does:

Adds all of the Canadian provinces to the states list in the store module
Renames fields in the address book system (logged in or not) so that they are Canadian friendly
Makes the new provinces/states field a required field from a drop down list

The end result is that provincial taxes such as PST get calculated correctly. For example, setting a tax rule such as "Add 7.00% where state = 'British Columbia'" actually works now. Please note that this is a temporary hack that should be fixed by making the core ecommerce system more international.

Related issue messages:
http://drupal.org/node/60605
http://drupal.org/node/39653

Comment	File	Size	Author
	ecom_canada.zip	2.47 KB	rickvug

Comments

Comment #1

mass0ud commented 8 August 2006 at 14:48

Great feature! Is it backwards compatible with 4.6? I am running custom modules developed for 4.6 and can't upgrade to 4.7 for at least a few more months.

Regards,
Massodu

Comment #2

rickvug commented 8 August 2006 at 21:09

No, this wont be compatible with 4.6. Sorry.

Comment #3

avolve commented 21 October 2006 at 03:10

Is there a patch in the works to have the provinces come under Canada as a separate country?

I see this as causing problems for calculating GST with the country set to Canada as opposed to USA. There are already issues with 'Canada' (which changes to country = 'ca') being set for tax in that it does not add this in the checkout already???

anything i am missing?

thanks for adding this patch btw

Comment #4

gordon commented 22 October 2006 at 02:03

Status:

Active

» Needs work

Thanks for this, but unforcantly this builds on a system that just doesn't scale.

The adress modules needs work to so that it can handle all states/provinces around the world. I would love it to have the states for Australia as well.

I did have 1 idea of adding the countries/states back into the database so that they can be read in depending on the country. The problem with this is that it makes translating much more difficult.

With the inclusion of jQuery into Drupal 5.0 we can really do some fun things with the interface, which will allow us to be able to handle all address systems around the world. The problem with doing this is that it will have problems for people without js.