The GA4 tag template has code in it to automatically set those parameters to the e-commerce extension values by default. For example, if you map to "order_total" it will take the mapping, but if nothing is mapped it will use the value from "_ctotal" which is populated by the e-commerce extension. The value of using the e-commerce extension is that you essentially only have to do the mappings once in the extension, and those mappings are then used in any number of tags that would need those parameters to be sent for events like add to cart, product pages, checkout pages, and order confirmations. If you don't know whether a tag is enabled for the e-commerce extension, you can look at the notes in the left bar of the tag and it will let you know if it has been enabled for the e-commerce extension.
The only time you should override the e-commerce extension with a mapping would be if a particular tag needs a product price with a particular formula that doesn't match how you are currently populating your product price (ex: original price vs discounted price). You would then make that calculation in an extension, store the value in a new variable, and map the new variable to the tag to override the e-commerce extension. This would be on an as-needed basis, as the e-commerce extension SHOULD cover everything you need to send to a tag vendor.
... View more