@alex-jansen this is a proposal to add some groundwork for VAT (the ability of the merchant to process orders without VAT / Sales tax).

Examples would be:

• Amazon Sales Tax Exemption Program

• Candle Science

• EU has a compulsory program

It would be for me a sensible first step, I have some questions though:

1. locally sales taxes have different names (VAT in Europe, GST in India and many Asian countries, Sales Tax in the US), how could we account for the differences in naming this?
2. What would be a good comment in your opinion?

It's a very atomic change, should it never the less go into pending first?

This pull request is being nudged due to inactivity.

I really don't think adding a flurry of booleans to Offer is the way to go.

I would suggest we define a separate object named TaxInformation or something similar which would contain various tax bits, but also meta-information, in particular:

• Who this tax information applies to: where (country codes, zip codes in the US), who (people with disabilities, business, schools, etc). The second one would be a enum and that can be extended as we discover that shops painted red have a discount.

I really don't think adding a flurry of booleans to Offer is the way to go.

I would suggest we define a separate object named TaxInformation or something similar which would contain various tax bits, but also meta-information, in particular:

• Who this tax information applies to: where (country codes, zip codes in the US), who (people with disabilities, business, schools, etc). The second one would be a enum and that can be extended as we discover that shops painted red have a discount.

Hey,

Ok, I am struggling in between what I'd like to see, what you'd like to see and what's possible:

Generally calculating taxes and shipping and displaying it on the frontend is "complicated". There are three approaches:

• In the US you calculate taxes after you have a shipping address for consumers and B2B alike as even a zip code can be insufficient to calculate taxes precisely (yes, people have even been fined for that). There's an entire ecosystem of companies calculating taxes for eCommerce.
• in Europe for consumer and mixed shops you usually calculate taxes for your country and if you ship intracomunity (other EU countries) or outside EU, you recalculate after shipping address
• on B2B shops you don't show taxes at all in Europe as you assume businesses either do not pay them or pay at checkout and get them back.

Your multiple taxes system is great in theory, I just don't believe it's relevant for schema or structured data as the info will not be available.

The problem is still that these tax exemptions are often locale-dependent (e.g., as you mentioned the reduction for the blind in Italy), so should be specifiable by country (similar to how shipping costs are specified by destination). Just having a single exemption boolean at the Offer level cannot generally be sufficient.