Timeline for How to get the VAT value into checkout page from my account information
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2020 at 15:03 | comment | added | simonthesorcerer | Yes, M1 also had 2 attributes IIRC. But I think the separation of customer and customer_address wasn't so strict back then, or you might have had a customization in M1 that handled this. Haven't worked with M1 a lot lately, so this is from memory obviously. | |
| Oct 26, 2020 at 14:50 | comment | added | Webninja | I agree completely. I guess it is because of the automatic customer group selection at the registration phase, but I'm sure this could have done in a more sensible way. Maybe set the customer taxvat as the default VAT ID of the address if no other is given or something like that. Was it like this in M1 as I have a migration case where migrated registered customers are all of a sudden ordering with tax included as they expect things to work as they worked in M1? | |
| Oct 26, 2020 at 14:40 | comment | added | simonthesorcerer | Yes, same. I think the customer-attribute ("taxvat") is nonsense. It makes more sense to have the VAT ID at the customer's address, because different addresses may require different tax calculations. | |
| Oct 26, 2020 at 14:36 | comment | added | Webninja | It really puzzles me why there are two fields for the VAT ID. It is really confusing for the customers. | |
| Aug 11, 2020 at 16:07 | history | answered | simonthesorcerer | CC BY-SA 4.0 |