$0 Shipping Subtotal after a shipping method is selected in the Shopping Cart Estimator

[matthew-muscat]

Preconditions (*)

• Confirmed affecting Magento 2.4.1 (PHP 7.4)
• Confirmed affecting Magento 2.3.4 (PHP 7.3)

Steps to reproduce (*)

1. Configure the store to utilize an "Online" carrier method that offers live quoting (in this case, this was Shippit, but it's been confirmed with other third party modules too — DHL, FedEx etc are suspected, but unconfirmed to also be affected by this)
2. Add an item to the shopping cart
3. Request a Shipping Estimate
4. Select one of the provided live quote options
5. Observe the "Shipping Subtotal" is set as $0

Expected result (*)

1. The shipping subtotal should be updated to the price value of the quote, rather than $0

Actual result (*)

Selecting the "Shippit - Standard" shipping method results in a $0 shipping subtotal

Notable Observations

• The issue dis-appears from the current user session if they have entered checkout and selected the shipping method within the Checkout. Returning to the Shopping Cart page then enables the Shopping Cart Shipping Estimator to operate as expected.
• This appears to only affect carriers extending against "AbstractCarrierOnline" — "AbstractCarrier" implementations appear to be unaffected (ie: flat rate or third party implementations using AbstractCarrier

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [ ] 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 @matthew-muscat. Thank you for your report. To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[stale[bot]]

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!