Free shipping cart rules do not apply

[Larke12]

Preconditions and environment

• Magento 2.4.6-p1
• Setup free shipping promotion as denoted in documentation: https://experienceleague.adobe.com/docs/commerce-admin/marketing/promotions/cart-rules/price-rules-cart-free-shipping.html

Steps to reproduce

1. Setup a cart rule for all customer groups with no coupon, following the setup as denoted in the documentation.
2. Ensure shipping methods with cost are available: Flat Rate and/or Table Rates.
3. Add product(s) to cart that triggers the condition (i.e. If All of these conditions are True: Subtotal equals or greater than 50)
4. Provide estimated shipping information or full shipping address, view shipping costs.

Expected result

All shipping methods with cost should show as $0.00 or on selection denote a deduction of equal value.

Actual result

No discount is applied to offer free shipping on any methods.

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @Larke12. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Bravo. 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: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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-Bravo]

Hi @Larke12,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

• Setup a cart rule for all customer groups with no coupon, following the setup as denoted in the documentation.
• Ensure shipping methods with cost are available: Flat Rate and/or Table Rates.
• Add product(s) to cart that triggers the condition (i.e. If All of these conditions are True: Subtotal equals or greater than 50)
• Provide estimated shipping information or full shipping address, view shipping costs.

All shipping methods showing $0 as a shipping costs.

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

[TiffanyElNino]

@Larke12 I encountered this problem with 3rd party shipping methods, maybe it helps you as well. These custom shipping methods were setting their rate based on the comparison $request->getFreeShipping() === true, but in some responses the result of getFreeShipping() is an int(1), due to a recent cast change which results in a false expression.

[engcom-Bravo]

@TiffanyElNino Thanks for your contribution & collaboration over here.

Hi @TiffanyElNino,

Can you please provide latest update on this comment https://github.com/magento/magento2/issues/37945#issuecomment-1702531112 and also please check issue is causing due to any third party extensions if so please refer the solution here https://github.com/magento/magento2/issues/37945#issuecomment-1710011886.

Please let us know if you are still facing any issue.

Thanks.

[engcom-Bravo]

Hi @Larke12,

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.

[Larke12]

@TiffanyElNino Thanks for the tip! That does in fact seem to resolve the issue a client of mine was facing, though third party shipping methods were not installed in my test case.

Given that this isn't the first issue raised for this problem and the fix is reverting the core change, it seems likely that this should be revisited by someone at some point. Otherwise if people come across this a simple plugin should help overcome the bug.