Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Scenario: We are getting to a point where Taxes are often applied even when the store does not reside in that Tax Zone.
This patch will allow this to be configurable per Tax Type.
By default, this is checked.
If you uncheck, the Tax Type will not check the store address.
Comment | File | Size | Author |
---|---|---|---|
#13 | commerce-match_store_to_tax_zone-3005440-13.patch | 3.97 KB | thenchev |
#10 | interdiff-2_10.txt | 2.54 KB | jonnyeom |
#10 | commerce-match_store_to_tax_zone-3005440-10.patch | 4.08 KB | jonnyeom |
Selection_076.png | 10.02 KB | jonnyeom |
Comments
Comment #2
jonnyeom CreditAttribution: jonnyeom as a volunteer commentedComment #3
bojanz CreditAttribution: bojanz at Centarro commentedYou will need to make a strong case for why such an option should be accepted and available.
At this point in the release cycle I try to delegate every such custom use case to custom code.
Comment #5
jonnyeom CreditAttribution: jonnyeom as a volunteer commentedSo, earlier this year, the Supreme Court passed a ruling that States can charge taxes despite not having a physical presence in a state.
Here is an article.
I found that I currently have a use case directly related to this so I made a patch. Your thoughts?
Maybe there is a better approach for handling this. Still thinking.
Comment #6
vood002 CreditAttribution: vood002 commentedI also have a use case for this functionality.
I have a client who has to charge sales taxes in two states as their business is based in one, but the company that handles their fulfillment is based in another.
I installed this patch on 2.11 and it solved the problem for me. I have to imagine this is not that rare of a situation.
Comment #7
rwhirn CreditAttribution: rwhirn commentedI believe it should say exactly what the message now says, should just be a checkbox to turn off:
o tax type will be used only if both the customer and the store belong to one of the territories
or radio buttons:
o tax type will be used only if both the customer and the store belong to one of the territories
o tax type will be used if the customer belongs to one of the territories
Comment #8
themic8 CreditAttribution: themic8 commentedjonnyeom, Thank you, this fixed the same issues I was working through.
Current project: I needed to be able to apply tax based on the state, not just the state the store is based out of. I also needed to be able to apply VAT tax for countries in Europe.
Currently using Drupal commerce 8.x-2.11
Comment #9
BrightBoldUse case for this feature: US store with a small number of nexuses so they didn't think it warranted a tax cloud. In D7, Rules allowed them to have per-state tax rates triggered by the customer's location only. Upon upgrading to D8, this is no longer an option. Having this checkbox would allow upgrading sites to retain the same functionality they had in Commerce 1.x; it feels like a regression to have lost it.
Comment #10
jonnyeom CreditAttribution: jonnyeom as a volunteer commentedUpdating the patch with updated tests.
Glad there are various use cases for this!
Comment #11
noah CreditAttribution: noah as a volunteer commentedA Canadian business we're working with has grandfathered in some odd (but legal) tax rules that don't match the built-in "Canadian sales tax" plugin, but require that different taxes be charged to customers in different provinces regardless of the location of the store. This patch applied successfully to 2.16 (with some offsets) and is accomplishing what we need—thanks!
(I'm never sure when something should become RTBC, so I'm not going to change this, but it looks good to me.)
Comment #12
arunkumarkApplied patch #10. Working as expected.
Comment #13
thenchev CreditAttribution: thenchev at Acro Commerce commentedreroll
Comment #15
jsacksick CreditAttribution: jsacksick at Centarro commentedThe "tax registration" setting needs to be used now. There's no longer a matching done on the store address, this has changed in the latest 2.28 release.
See #3246388: Local tax type application should be determined based on the tax registrations.
Comment #16
noah CreditAttribution: noah as a volunteer commentedIs there any documentation on how to achieve this functionality using the "tax registration" system? The store we're managing is in Canada, but its tax rules don't match the out-of-the-box Canadian sales tax rules—are we looking at having to write a custom tax plugin, or should we be looking for a different path forward? All we need to do is ignore the store address when determining the tax rate.
Any advice appreciated.