-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shopify: Sales Order Aggregate same tax rate in Sales Order #12
Comments
Hey @ankush, just found out, shopify seems to work differently.
Question: Shall we just import it as shopify displays it: This would mean:
|
@ankush I can maybe create a pull request to try it out? |
Sure, I haven't given much thought to this problem yet, will check it out 👍 Maybe make this behaviour configurable? Not everyone would want to merge the tax lines. I guess it does make sense to use "Actual", but it would be good to keep the percentage in the description. |
Agree did that with following pull request: #18 |
Just joining the conversation, is this solved? |
I've changed the tax computation to completely mirror Shopify's calculations and also item wise tax distributions. At present, I have no plans of aggregating this, as it increases complexity because Shopify also has multiple options for configuring taxation. The only sane way to handle it is to use them at actuals, which is what we've done right now. So if anyone else wants to take a stab at merging tax lines, feel free to do so. ref: ecommerce_integrations/ecommerce_integrations/shopify/order.py Lines 185 to 199 in 5c58d82
|
Refer PR above, there's option to do this now ^ |
In our country we have very difficult VAT and Tax Settings and it was hard to set it up in shopify. Let's take the following example:
Current Behaviour:
When such a SalesOrder is synced from shopify. It will end up having these lines:
Idea:
Aggregate all 7% VAT at the end with a single line Type Actual with 2,60 (regarding example above).
Just a request for comments.
Regards
The text was updated successfully, but these errors were encountered: