Hey @npuana,
Yes, you are correct about the street address in my example (1450 Glenarm Pl) actually being from Denver, but I also tested with just the zip code as well as actual Glenwood Springs addresses too and got the same, correct 8.6% rate. When the store location is in Denver and that real Denver address is used, the correct 8.31% rate is calculated:
https://cld.wthms.co/sZtxc2
To answer your question about how Services determines tax rates, here are some examples:
Colorado has “Home Rule” jurisdictions. That means that merchants (store owners) will only need to pay city tax if the destination address is also in their same home rule jurisdiction. So, for example:
- A merchant has an economic Nexus in Louisville, CO. He gets an order from Denver, CO. Denver and Louisville are in different Home Rule jurisdictions, so that order doesn’t have city tax.
- A merchant has an economic Nexus in Louisville, CO. He gets an order from Louisville, CO. That order does have city tax, and that tax will be collected directly by the city, not the state.
- A merchant has an economic nexus in San Francisco, CA. He gets an order from Louisville, CO. That order doesn’t have city tax (or any kind of tax, really).
- A merchant has an economic nexus in San Francisco, CA. He also has a lot of clients from Colorado, so he has also an economic nexus in Colorado as a whole. He gets an order from Louisville, CO. That order doesn’t have city tax.
So, the TaxJar rate calculator can’t account for some of these cases, because it doesn’t allow to specify both the origin and destination addresses. However, the API (and the Services plugin) should be returning the actual, correct rates.
Hopefully this helps clarify how it works, but from all the different tests that I’ve done after (very recently) hearing that the fix was released, the rates do seem to be correct based on the various shop base locations and destination addresses for all the cities I’ve checked.