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
Free shipping for physical and virtual products with table rate not working correctly #27861
Comments
Hi @engcom-Delta. Thank you for working on this issue.
|
✅ Confirmed by @engcom-Delta Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions! |
Hi @SteveMcC71. Thank you for your report and collaboration! The related internal Jira ticket The fix will be available with the upcoming |
I do not believe the scope of this fix was correct. It does not include fixes to the Freeshipping carrier in the module-offline-shipping where the free shipping threshold is calculated. This may be intentional as more than likely any change here would require another configuration setting (I.E. ignore virtual items) but it seems incorrect to assume that virtual items would be included in the free shipping threshold check. |
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
If we have both a virtual and physical product in our cart and the total value exceeds our threshold of € 20 the shipping is free because it considers both types of product rather than excluding the virtual product from the calculation as expected.
With JUST virtual products in the cart the calculation is correct, or with JUST physical products in cart the calculation is correct.
The text was updated successfully, but these errors were encountered: