Skip to content
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

Closed
SteveMcC71 opened this issue Apr 15, 2020 · 5 comments
Labels
Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: done Reported on 2.3.4 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch stale issue

Comments

@SteveMcC71
Copy link

SteveMcC71 commented Apr 15, 2020

Preconditions (*)

  1. Magento 2.3.4
  2. Magento 2.4-develop

Steps to reproduce (*)

  1. Create table rate file
    image
  2. Stores -> Configuration -> Sales -> Shipping Methods -> Table Rates "Price vs. Destination"
  3. Include Virtual Products in Price Calculation as "No"
    image
  4. Create a Simple Product with price 40$
  5. Create a Virtual Product with price 20$
  6. Navigate to Storefront and add both products to the Cart

Expected result (*)

  1. If a customer adds a physical product AND a virtual or downloadable product to their cart, the cost of the downloadable or virtual product should not be used to calculate the free shipping threshold (in our example 20$)
  2. Shipping price should 20$ according simple product price 40$

Actual result (*)

  1. 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.
    image

  2. With JUST virtual products in the cart the calculation is correct, or with JUST physical products in cart the calculation is correct.

@sidolov sidolov added this to Ready for Grooming in Low Priority Backlog Sep 24, 2020
@sidolov sidolov added this to Ready for Confirmation in Issue Confirmation and Triage Board Oct 21, 2020
@ghost ghost removed this from Ready for Grooming in Low Priority Backlog Oct 21, 2020
@magento-engcom-team magento-engcom-team added the Reported on 2.3.4 Indicates original Magento version for the Issue report. label Nov 13, 2020
@engcom-Delta engcom-Delta self-assigned this Nov 20, 2020
@m2-assistant
Copy link

m2-assistant bot commented Nov 20, 2020

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.4-develop branch

    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Add label Issue: Confirmed once verification is complete.

  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Delta engcom-Delta added Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Nov 20, 2020
@m2-community-project m2-community-project bot moved this from Ready for Confirmation to Confirmed in Issue Confirmation and Triage Board Nov 20, 2020
@magento-engcom-team
Copy link
Contributor

✅ Confirmed by @engcom-Delta
Thank you for verifying the issue. Based on the provided information internal tickets MC-39292 were created

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.

@engcom-Delta engcom-Delta added the Priority: P3 May be fixed according to the position in the backlog. label Nov 20, 2020
@m2-community-project m2-community-project bot added this to Ready for Development in Low Priority Backlog Nov 20, 2020
@stale
Copy link

stale bot commented Feb 4, 2021

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!

@stale stale bot added the stale issue label Feb 4, 2021
@stale stale bot closed this as completed Feb 18, 2021
@m2-community-project m2-community-project bot moved this from Ready for Development to Done in Low Priority Backlog Feb 18, 2021
@magento-engcom-team
Copy link
Contributor

Hi @SteveMcC71.

Thank you for your report and collaboration!

The related internal Jira ticket MC-39292 was closed as Fixed.

The fix will be available with the upcoming 2.4.3 release.

@tsfanning21
Copy link

Hi @SteveMcC71.

Thank you for your report and collaboration!

The related internal Jira ticket MC-39292 was closed as Fixed.

The fix will be available with the upcoming 2.4.3 release.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: done Reported on 2.3.4 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch stale issue
Projects
Development

No branches or pull requests

4 participants