POs adding tax on recalculate

I have a staging site set up and I just checked POs there and they are functioning correctly. The only difference in the staging site is BoosterPlus and Multi-Inventory Premium are one version back.

Ok, I have figured this out, but there is still a bug in ATUM.

I had my sales tax rates in WooCommerce set down to two lines, one for state, one for local, this was a recent change.

I had both lines set to Country = US and State = AZ, with an asterix in Postal/ZIP and City. ATUM seems to be only looking at the ZIP/City only. It really needs to be looking at them all. AND FURTHER, it should not be dependent on this anyway, because POs are mostly used as business purchases anyway, so there should be no tax regardless of where the supplier is located.

Hi @allarmsllc

Good to know that you figured out the cause.
ATUM is actually getting the WooCommerce taxes configuration for Purchase Orders also and this cannot be changed (this has been working in that way since the very first version). Anyway, we’re going to test everything in order to confirm that it’s working as expected and if we find any issue, we’ll fix it.

FYI, with the ongoing Purchase Orders premium, you should be able to set distinct taxes configurations for every PO and also assigning the tax to the supplier and getting it from there by default when any PO linked to that supplier is created. Or you can decide to just not apply taxes to any PO if you really want this.

Best Regards,
Salva.

“you should be able to set distinct taxes configurations for every PO and also assigning the tax to the supplier and getting it from there by default when any PO linked to that supplier is created. Or you can decide to just not apply taxes to any PO if you really want this.”

How do I set taxes for POs separately from the WooCommerce sales tax and especially for specific suppliers?

As I have said, this functionality will come with the ongoing Purchase Orders premium add-on. We plan to release this add-on in the coming months ??

I have to purchase an add-on to fix your plugin? Tax should not be added to POs by default. If I happen to have a supplier in Arizona, where I have sales tax defined in WooCommerce, I just have to deal with it being added to POs? This is not an acceptable solution.

Good Day @allarmsllc ,

Thank you very much for all your replies and for using ATUM.

My name is Pavel, the founder of this great plugin ??

I just want to step in to prevent any issues or misunderstandings. The plugin you are using is a free version and I can proudly say the largest and most featured plugin of this kind without asking for any fee.

We can do only as much to give out for free and since the very beginning the free version supported one tax setting. If you are an international trader and your shop is getting massive, using the free version will limit you to do things manually.

As my senior developer suggested you could take advantage from our new premium add-on that will include more flexible options and lot larger feature set. However, I pay ten thousands of euros for any feature to be developed and can not afford to give everything away for free.

So, even though you feel distinct taxes should be part of free Purchase orders in ATUM it will not happen and can not happen if I am to keep ATUM development and support alive for many years to come.

This forum is about free features so I can not discuss pricing or anything else here. The forum admins may block this thread if we keep on going.

Please, if you want to discuss further use the official forum via link you can find in your site’s ATUM installation.

I hope you understand where I am coming from.

Best Regards,

Pavel

I understand it costs money to develop software, and I appreciate that fact. I do pay for one of your premium add-ons, Multi-Inventory, because it adds functionality.

However, not including tax on POs should be the default function, that is my point. Leaving it as is, your plugin is using a completely unrelated setting to determine whether to add tax on a PO, which is different than a customer order. I really hope you can fix this issue without requiring the purchase of an add-on.

HI @allarmsllc ,

Thank you very much for your reply.

I am not sure I follow? Purchase Orders are unrelated to customer orders by default. I do not know nature of your business, but maybe I am misunderstanding what you are saying?

When you create a PO, you are creating a document that goes to your supplier. Taxes on customer order have nothing to do with taxes on the PO. That is why we give an option to add or not add or to add custom tax.

Please, do tell me if I am not understanding your issue?

Pavel

When I add a PO, it is using my settings in WooCommerce>Settings>Taxes>Standard Rates…where I have sales tax defined for my state of Arizona. I had a rate set with Country = US and State = AZ, with * in both Postal Code and City. When set this way, your plugin adds tax to a PO if I hit the Recalculate button. If I add a range of Postal Codes in the WC settings, to limit it further, your PO plugin doesn’t add tax.

“That is why we give an option to add or not add or to add custom tax.”

Where is this separate setting for tax on POs?

Ok, I found the Add Tax button when doing Add Item on the PO. So that question is answered. But, your plugin still seems to be pulling tax info from the WooCommerce Tax settings when the rates are defined without a Postal Code or City.

Hi @allarmsllc ,

Ok, got you there.

We are going to amend the free POs so they take into consideration postal codes and cities.

We need some time however, please, do give us few weeks and follow up the change log.

Hope this helps.

Pavel