Tier pricing when price scope is Website

[proatwork]

Preconditions (*)

1. Magento 2.3.1 CE
2. PHP 7.1.23
3. Global-Settings catalog/price/scope = 1 (WEBSITE) bin/magento config:set catalog/price/scope 1
4. Add store codes to URLs (for easy testing)

Steps to reproduce (*)

1. Create two separate websites (I will name them "Okay" and "Bug")
2. Set the default base currency (All Storeviews scope) to SEK, display currency to USD and allowed currencies to USD and EUR
3. Set the "Bug" base currency to EUR, display currency to EUR and allowed currencies to EUR only
4. Under Stores > Currency > Currency Rates set:
   • 1SEK = 0.10USD = 0.093EUR
   • 1EUR = 10.75 SEK = 1.12USD

5. On a product

   • in All Storeviews scope

   • set the price to 100SEK

   • set a discount based tier:

   • in "Bug" scope

     • set the price to 10EUR

     • Ttier pricing will still exist/be inherited in this scope:

Expected result (*)

1. In the "Okay" store, the tier pricing is correctly calculated
2. In the "Bug" store, the tier prices should be calculated correctly

Actual result (*)

1. In the "Bug" store, the tier pricing is incorrectly calculated

If you set a 1:1 currency rate between EUR and SEK then the tier prices work correctly, but the EUR prices on the "Okay" store are affected.

[m2-assistant[bot]]

Hi @proatwork. 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 2.3-develop instance - upcoming 2.3.x release

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

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

• [ ] yes
• [ ] no

[m2-assistant[bot]]

Hi @AlexWorking. 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).

  Details

  If 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.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 Issue: Confirmed once verification is complete.

• [ ] 7. Make sure that automatic system confirms that report has been added to the backlog.

[proatwork]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @proatwork. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @proatwork, here is your Magento instance. Admin access: https://i-22784-2-3-develop.instances.magento-community.engineering/admin Login: admin Password: 123123q Instance will be terminated in up to 3 hours.

[proatwork]

I was able to reproduce bug in 2.3-develop instance

"Okay" Store

"Bug" Store

[AlexWorking]

Hello @proatwork. We confirm the issue, but please add to Your Steps to Reproduce one more step You most probably just forgot to add. The step concerning setting currency rates of SEK to EUR and EUR to SEK. Without this step everything works seemingly correctly, (though indeed it doesn't). Also please remove points with the sample data from the post as they are not necessary for the issue reproduction. Thank You.

[magento-engcom-team]

:white_check_mark: Confirmed by @AlexWorking Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99608, MAGETWO-99609 were created

Issue Available: @AlexWorking, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant[bot]]

Hi @irajneeshgupta. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. 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!

• [ ] 3. 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

• [ ] 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.magento.com/browse/AC-828