compendiumvent1

Hi Luminus,

Thanks for explaining the priority and compounding functionality with the examples, which makes everything clear now. Especially the combination of the two makes the effect of priority clear as the outcome can be all different.

Best regards,
Harry

Hi Mirko,

In addition to my last reply I can give the result of testing the priority setup as suggested by me. This resulted in selecting the general country DE rate and not (only) selecting the postcode rate when it matches the postcode by:
– setting priority 1 for general country DE and priority 2 for postcode
– OR the postcode on priority 1 and the general country DE on priority 2.

So apparently only the default behavior from top to bottom, as you mentioned, is the only way to get 1 rate selected when matching the postcode or not. Automatically the setup sequence is saved like that too with postcode setting first and then the country setting.

If this is how the functionality is supposed to work, the remaining question is what the priority function actually does do. What you mentioned on the multiple tax rate, suggests that then more than 1 rate is selected when this applies e.g in a specific country or the same postcode. But this would mean the rates that apply are compounded as not only 1 is selected. If this is the case what is then the functionality of use of the compounding function.
Therefore please explain what is the difference between the priority function to the default behavior from top to bottom?
How does the compounding function then fit in?

I look forward to hear back soon to wrap this up so I can inform our marketplace integrator about the tax functionality behaviour in WooCommerce in order to adjust to this. Currently our integrator follows now the priority function to select 1 rate while the default behavior results with them in multiple rates.

Best regards,
Harry

Hi Mirko,

Thanks for your reply.

However I still see not the remaining functionality of priority setting.

You mentioned that the most important thing to remember is the default behavior from top to bottom in order for the postcodes tax rates to be triggered. So how will then the Priority 2 for postcodes be fine as these are automatically put below the priority 1 of in our case the country DE when saving this, as the priority 2 will never be selected?

Than as you mentioned, entering multiple tax rates for a specific country, for example multiple VAT rates within the same country, you need to prioritize them according to their relative importance. Hence, in the field for Priority you can enter the number for each tax rate. In the example every tax rate is set with a different priority level and only one particular tax rate corresponds to a specific priority.
Is this then the use of priority?
If so, what is then actually the result taking the example and keeping in mind that compounding is not selected?

Depending on your reply what should then be our setup for the system to select only the tax rate on postcode when matching e.g. 0% and when not matching on country level e.g for DE 19% without compounding these?

Look forward to hear back soon.

Thanks,
Harry

Hi Mirko,

Thanks for your reply and to perform a test and replicate the issue.

Herewith the screenshots of our tax settings:
Tax Options: https://snipboard.io/UVbZTS.jpg
Tax rates (we have only standard): https://snipboard.io/2mTjOD.jpg

The setting for country code DE is the mentioned setting way 2 , which is automatically saved after all the priority 1 at the bottom.
All the others country codes with also zipcode settings are the mentioned setting way 1.

Look forward to hear back soon so we know how this should work and resolve the issue we have fast.

Thanks,
Harry