Hi,
Sorry for the newbie question, but we only recently decided to try out Sylius for our company and noticed something that I don't see a way to fix other than customizing the taxation logic but most ecommerce alternatives support out of the box e.g. Magento, Prestashop, Woocommerce.
The problem comes with calculating VAT Tax in European Union countries.
Let's say we have 4 types of customers,
Local Retail Customers (LRC)
Foreign Retail Customers (FRC)
Local Businesses (LBC)
Foreign Business (FBC)
For retail customers there are two cases I've encountered so far based on individual country's law
For business customers I see two different cases as well
I thought of setting up Zones first with scope for taxes but I can't see how to set it up the way the system currently works. I can't see any association between "Customer Group and Tax" or between "Zones and Customer Group" that would enable this sort of association I'm describing. Also there's not a way to automatically check during checkout if the guest is a company or an individual.
One common implementation I see for this in checkout when purchasing from abroad is the following:
1a. when the guest fills in a company name, he is considered a BC
1b. the guest selects if he's buying as individual or company
Am I missing something simple here maybe because it looks to me like a serious flaw. I appreciate any advice. Thank you in advance
After checking around abit more I still can't find a solution to this within sylius. There's no relation between tax rate and customer tax class.
Here's an example in Magento where we have tax rates, product tax class and customer tax class to define taxation for products.

Here's an example from virtuemart

We would like to introduce customer tax category concept in 1.1, right now it is a bit too late but thank you for research & explanation of the issue - makes sense. :) 馃憤
Hi @pjedrzejewski it's very nice to see that this will be addressed because for me it wasn't possible to use Sylius at all with this issue. It will be nice to revisit.
+1 Actually a showstopper for me to.
@ioweb-gr as for the creator of this issue, it would be really appreciate if you look at the proposed solution in #8676. Thank you very much for your time!
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.
this is not stale
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.
Are there any news about that? @pjedrzejewski
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.
Hey @pjedrzejewski
I know this issue has been closed due to lack of activity.
This is not due to missing elaboration from the community but because of missing interest, internal roasmap, missing time, lack of feedback to the community on your side (not meant harmfully at all).
Maybe you could place a "not stale" Tag or samething like that?
Or give some feedback and close :-)
Just feels weird if stalebot closes tickets when they're not stale.
Most helpful comment
+1 Actually a showstopper for me to.