Magento Community Edition: Version 2.4.7-beta1 - Tier pricing with multiple websites

[RocktechnolabsDev]

Preconditions and environment

• Magento Community Edition '2.4.7-beta1' without sample data is installed.
• Multiple website setup, Website have products
• Add tier prices for multiple websites
• Catalog Price Scope is website
• Multiple websites have different currency as well, like main website have AUD dollar, UK website have British dollar

Steps to reproduce

1. Login into admin > Catalog > Products > Create new simple product (add required details to create a product)

2. Add tier price in that product, Select All Website[AUD] option in Website, Select Not Logged In customer group, Quantity is 1, Price type is fixed, price is 33, at that moment product assigned to the single(main) website only. save tier price.

3. Assign product into UK website, save the product

4. Add tier price for UK website, click on Advanced Pricing, select UK[GBP] option in website, Select Not Logged In customer group, Quantity is 1, Price type is fixed, price is 33, save tier price.

5. Here you can see, tier price have two records one for main website, and another one is for UK website.

6. Now unassigned product from UK website, see tier pricing record, UK[GBP] tier pricing record website scope changed to All Website[AUD] and that tier pricing record being duplicate.

7. So instead of change website scope , if record will remove that it's more convenient to end user.

Expected result

Remove UK website tier pricing record instead of change scope in website

Actual result

Tier pricing record website scope is changed to All Websites[AUD] and that record being duplicate record.

Additional information

https://www.awesomescreenshot.com/video/21699627?key=cf5ed9104189d7a1b314fc17278ad849

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

Hi @RocktechnolabsDev. 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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]

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: 👇

• 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 @RocktechnolabsDev,

Thank you for reporting and collaboration.

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

Steps to reproduce

• Login into admin > Catalog > Products > Create new simple product (add required details to create a product)
• Add tier price in that product, Select All Website[AUD] option in Website, Select Not Logged In customer group, Quantity is 1, Price type is fixed, price is 33, at that moment product assigned to the single(main) website only. save tier price.
• Assign product into UK website, save the product
• Add tier price for UK website, click on Advanced Pricing, select UK[GBP] option in website, Select Not Logged In customer group, Quantity is 1, Price type is fixed, price is 33, save tier price.
• Here you can see, tier price have two records one for main website, and another one is for UK website.
• Now unassigned product from UK website, see tier pricing record, UK[GBP] tier pricing record website scope changed to All Website[AUD] and that tier pricing record being duplicate.

Tier pricing record website scope has been changed to All Websites[AUD] and that record being duplicate record.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-9774 is successfully created for this GitHub issue.