Using standard tax engine #1128
-
Until now I have used the Basic tax engine in a project I my webshop (in development). However, because we now also have products with a tax percentage of 9 (next to the default 21), I decided to switch to the standard tax engine. For regular products I see a tax category field is automatically added to the sidebar. But for product_variants it is not added. Is that correct? So I would assume I add It manually by adding a tax category field to the sidebar myself. Is that the way to go? I do not see the new tax percentage reflected for products which I have set to the Tax category connected to the tax rate of 9%. Should I do more to get this to work? I set the engine via the config to use the standard tax engine and added the tax category to the blueprint but that does not seem to do anything. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
That's weird. The "Tax Category" field should get added, whether it's a standard product or a variant product.
Did this cart exist before you switched the tax engine? If so, you might need to do something to trigger the cart to be "recalculated" using the new tax rate. |
Beta Was this translation helpful? Give feedback.
-
Seems to be the case in your starter kit as well. If I add a product I see the Tax Category field in the sidebar. For a product with variants this does not appear. I tested it with a new cart so that is unfortunately not the issue. |
Beta Was this translation helpful? Give feedback.
-
I noticed when I add a Tax category manually the tax category is not used if I name it like this: "taxcategory": [ If I use an underscore this leads to an error "Array to string conversion" "tax_category": [ The tax category with that ID does exist. |
Beta Was this translation helpful? Give feedback.
-
Thanks for your help @duncanmcclean, I think the problem is solved. Probably a combination of removing the tax_category field from the blueprint and installing the latest version where the tax_category field is added automatically (to the product variants blueprint). |
Beta Was this translation helpful? Give feedback.
Thanks for your help @duncanmcclean, I think the problem is solved. Probably a combination of removing the tax_category field from the blueprint and installing the latest version where the tax_category field is added automatically (to the product variants blueprint).