-
Notifications
You must be signed in to change notification settings - Fork 11
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
Provide setting to select when order is committed #18
Comments
Good thoughts @jmauzyk. We'll discuss it and see what might be involved in that. Are you on Commerce 3? |
Yep, using the latest version of Commerce 3. Thanks!
…On Wed, Apr 8, 2020 at 10:21 AM Jason Siffring ***@***.***> wrote:
Good thoughts @jmauzyk <https://github.com/jmauzyk>. We'll discuss it and
see what might be involved in that.
Are you on Commerce 3?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFCP3JEF7AJSWKDPLX36KY3RLSJBJANCNFSM4MD73GTQ>
.
|
Bumping. We have a similar use case. In our scenario, some orders cannot be shipped via traditional means and requires communication with the customer after the order is completed and partial shipping payments are collected with Commerce 3 after order completion. |
Bumping as well, we have a similar scenario. We have a Order Status called "Quote," which is used to provide customers with pricing and terms prior to placing an order. Not until they actually order the product should it be committed within Avatax. |
Currently the Avatax plugin commits an order when the order is marked complete. However, we're finding there are situations where this causes issues:
These are just a few examples. I think it would be beneficial if there were an option in the Avatax plugin settings to select which order statuses trigger an order being committed. This would allow users to ensure that orders are only committed when they have been shipped/approved, and weed out scenarios above such as cancellations and edits to orders.
The text was updated successfully, but these errors were encountered: