docs: avalara integration tutorial (#13808)
* docs: avalara integration tutorial * fix getTaxLines method * fixes * fix broken link * fix build error * fix vale errors
This commit is contained in:
@@ -23,9 +23,14 @@ const taxProviderOptions: FormattingOptionsType = {
|
||||
`## Overview
|
||||
|
||||
A Tax Module Provider is used to retrieve the tax lines in a provided context. The Tax Module provides a default \`system\` provider. You can create your own Tax Module Provider, either in a plugin, in a module provider, or directly in your Medusa application's codebase, then use it in any tax region.`,
|
||||
`## Implementation Example
|
||||
|
||||
As you implement your Tax Module Provider, it can be useful to refer to an existing provider and how it's implemeted.
|
||||
|
||||
If you need to refer to an existing implementation as an example, check the [Avalara Tax Module Provider tutorial](https://docs.medusajs.com/resources/integrations/guides/avalara).`,
|
||||
`## Understanding Tax Module Provider Implementation
|
||||
|
||||
The Tax Module Provider handles calculating taxes with a third-party provirder. However, it's not responsible for managing tax concepts within Medusa, such as creating a tax region. The Tax Module uses your Tax Module Provider within core operations.
|
||||
The Tax Module Provider handles calculating taxes with a third-party provider. However, it's not responsible for managing tax concepts within Medusa, such as creating a tax region. The Tax Module uses your Tax Module Provider within core operations.
|
||||
|
||||
For example, during checkout, the Tax Module Provider of the tax region that the customer is in is used to calculate the tax for the cart and order. So, you only have to implement the third-party tax calculation logic in your Tax Module Provider.`,
|
||||
`## 1. Create Module Provider Directory
|
||||
|
||||
Reference in New Issue
Block a user