Following best practices, how should the Architect add the taxes for all orders?

A company wants to build an Adobe Commerce website to sell their products to customers in their country. The taxes in their country are highly complex and require customization to Adobe Commerce. An Architect is trying to solve this problem by creating a custom tax calculator that will handle the calculation of taxes for all orders in Adobe Commerce.

Following best practices, how should the Architect add the taxes for all orders?
A . Add a new observer to the event sales.quote.collecLtotals.before” and add the custom tax to the quote
B . Write a before plugin to MagentoQuoteModelQuoteManagement::placeOrder() and add the custom tax to the quote
C . Declare a new total collector in "etc/sales.xmr in a custom module

View Answer

Answer: C

Explanation:

According to the Adobe Commerce documentation, the best way to add a custom tax calculation to all orders is to declare a new total collector in the “etc/sales.xml” file of a custom module. This way, the custom tax logic can be implemented in a separate class that extends the MagentoQuoteModelQuoteAddressTotalAbstractTotal class and overrides the collect() and fetch() methods. The collect() method is responsible for calculating the tax amount and adding it to the quote address, while the fetch() method is responsible for displaying the tax amount in the cart and checkout pages. The new total collector can be assigned to any area of the order totals, such as before or after the subtotal, shipping, or grand total.

Reference: Customizing order totals

How to add custom fee or discount to order totals in Magento 2