Magento 2.2.5 - If Multi-Storefront, Shipping Rates on an Admin Order use rates from the default store

callumstar commented 6 years ago

Preconditions

Magento 2.2.5
PHP 7
Multistore installation
Websites with a shipping method enabled with different rates

Steps to reproduce

Create multistore version of Magento 2.2.5
Set up a single shipping method with different shipping fees for both websites in 'Stores > Configuration > Sales > Shipping Methods' (e.g. Flat Fee of £10.00 for default and Flat Fee of £15.00 for second storefront)
Attempt to create a new order in the admin area and use the second storefront
Click on the button 'Get shipping methods and rates'

Expected result

Shipping Rate should appear with the cost of £15.00

Actual result

Shipping Rate appears with the cost of £10.00 (as defined in the default store)

magento-engcom-team commented 6 years ago

Hi @callumstar. 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-engcom-team give me {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +). For more details, please, review the Magento Contributor Assistant documentation.

@callumstar do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

[ ] yes
[ ] no

callumstar commented 6 years ago

Hi @magento-engcom-team,

Yes I can reproduce this with any shipping rate on any vanilla instance of Magento 2.2.5.

callumstar commented 6 years ago

Hi @magento-engcom-team,

I believe that this is linked to the following issue:

12889 (incorrectly closed)
15497
16604

magento-engcom-team commented 6 years ago

Hi @engcom-backlog-nazar. 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:

[x] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the label G1 Passed will be added to the issue automatically. Please, edit issue description if needed, until label G1 Passed appears.
[x] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add G2 Passed 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.3-develop branch
Details
- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.
Details
- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x
[ ] 6. Add label G3 Passed once verification is complete.
[ ] 7. Make sure that automatic system confirms that report is acknowledged.