Skip to content

Commit b25aaff

Browse files
authored
Adjust dynamic URL section, Tax provider visibility section (#1272)
# [TAX-2651] ## What changed? * `Tax provider visibility` section replaces `Platform-wide availability` section. * `Dynamic tax URLs` section replaces `Tax profile` section. ## Release notes draft Small clarifications around tax provider visibility and configurable tax URLs. [TAX-2651]: https://bigcommercecloud.atlassian.net/browse/TAX-2651?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
1 parent 31645d6 commit b25aaff

File tree

1 file changed

+14
-13
lines changed

1 file changed

+14
-13
lines changed

docs/integrations/tax.mdx

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -23,17 +23,24 @@ Once you've obtained your app ID, fill out [this form](https://docs.google.com/f
2323

2424
Once your tax provider configuration is ready, we'll let you know through email. The email will also include your `provider_id`, which is required when [establishing a connection](#establishing-a-connection) with the [Tax Provider API](/docs/rest-contracts/tax).
2525

26-
### Tax profile (optional)
26+
### Tax provider visibility
2727

28-
BigCommerce sets the tax provider registry with your URLs for [Tax Provider API](/docs/rest-contracts/tax) requests. BigCommerce sends requests to these URLs, for example, when a shopper requests tax estimates.
29-
If you would like to support multiple connections for a merchant, BigCommerce can set the registry with flexible URLs that use our new profile option.
30-
These URLs would include a reserved string, for example, `https://{profile}/estimate`, allowing merchants to customize the base domain.
28+
By default, tax providers can be installed on any number of stores. Your tax provider will only be visible on these stores after [establishing a connection](#establishing-a-connection).
3129

32-
When connecting or installing your app, you must allow merchants to enter the URL's base domain in the control panel. Merchants need to be able to self-serve updates to the URL through your app.
33-
When you [Establish a Tax Provider connection](#establishing-a-connection), include the `profile` base domain along with credentials associated with the merchant's account.
30+
Tax providers can optionally be made visible on all stores on the BigCommerce platform. If you are interested in exploring this topic, please discuss the available options with your [BigCommerce tech partner contact](https://www.bigcommerce.com/partners).
31+
32+
Once an arrangement has been confirmed, you can make a request to enable platform-wide availability for your tax provider by emailing [taxproviderapi@bigcommerce.com](mailto:taxproviderapi@bigcommerce.com) with the relevant details.
33+
34+
### Dynamic tax URLs (optional)
35+
36+
BigCommerce sets the tax provider registry with your URLs for [Tax Provider API](/docs/rest-contracts/tax) requests. BigCommerce sends requests to these URLs, for example, when a shopper requests a tax estimate. These URLs can optionally include a reserved string to generate a dynamic URL.
37+
38+
BigCommerce offers the `{profile}` reserved string. When you [Establish a Tax Provider connection](#establishing-a-connection), include a `profile` value along with credentials associated with the merchant's account. This `profile` value will then be applied to any future requests made by this merchant.
39+
40+
For example, the tax URL `https://{profile}/estimate` allows merchants to customize the base domain. This can be especially useful when using tunnelling software during development of your sandbox tax provider (e.g. ngrok).
3441

3542
<Callout type="info">
36-
You must liaise with the merchant to provide them with customized URLs. BigCommerce merely consumes the URL values the merchant enters and uses the provided string value for Tax Provider API requests.
43+
It is the tax provider's responsibility to enforce the profile value being populated by merchants. Blank values cannot be processed as valid URLs.
3744
</Callout>
3845

3946
### Test tax provider (optional)
@@ -46,12 +53,6 @@ When you [share provider details](#sharing-provider-details-with-bigcommerce), s
4653
We recommend only creating one test tax provider instance. When you develop your app, it's best to test your [Tax Provider API](/docs/rest-contracts/tax) endpoints outside the BigCommerce platform. This helps avoid unnecessary dependencies.
4754
</Callout>
4855

49-
### Platform-wide availability (optional)
50-
51-
Tax providers can be made available to all stores on the BigCommerce platform. If you are interested in exploring this topic, please discuss the available options with your [BigCommerce tech partner contact](https://www.bigcommerce.com/partners).
52-
53-
Once an arrangement has been confirmed, you can make a request to enable platform-wide availability for your tax provider by emailing [taxproviderapi@bigcommerce.com](mailto:taxproviderapi@bigcommerce.com) with the relevant details.
54-
5556
## Building the app
5657

5758
You must build a BigCommerce [single-click app](/docs/integrations/apps/guide/types#single-click) to use the Tax Provider API for tax estimates and document submissions. Using a BigCommerce single-click app lets you promote your solution in the BigCommerce App Marketplace and ask merchants to authorize your app during install. Single-click apps also allow merchants to configure tax provider settings through an iFrame in the control panel.

0 commit comments

Comments
 (0)