You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, we use the tax calculation to be the ones offered by WooCommerce, Store Location(marketplace location), Customer's Billing Address, or Customer's Shipping Address as shown in this screenshot.
So, we are unable to let the system calculate tax from the vendor's store location which creates an issue for the marketplaces that are based on countries like USA where the tax varies from state to state depending on the store location of the vendor.
Describe the solution you'd like
We might add another option to the dropdown to let the system calculate tax from the vendor's store location.
Describe alternatives you've considered
No response
Additional context
A client from the USA reached out to us in a ticket and also shared his frustration on Facebook regarding this long-known issue of Dokan. [Facebook community post link]
The text was updated successfully, but these errors were encountered:
J-H-Mojumder
changed the title
Add option to calculate tax from vendor' store location.
Add option to calculate tax from vendor's store location.
Aug 2, 2024
Is your feature request related to a problem? Please describe.
Currently, we use the tax calculation to be the ones offered by WooCommerce,
Store Location
(marketplace location),Customer's Billing Address
, orCustomer's Shipping Address
as shown in this screenshot.So, we are unable to let the system calculate tax from the vendor's store location which creates an issue for the marketplaces that are based on countries like USA where the tax varies from state to state depending on the store location of the vendor.
Describe the solution you'd like
We might add another option to the dropdown to let the system calculate tax from the vendor's store location.
Describe alternatives you've considered
No response
Additional context
A client from the USA reached out to us in a ticket and also shared his frustration on Facebook regarding this long-known issue of Dokan. [Facebook community post link]
The text was updated successfully, but these errors were encountered: