Skip to content

Fix bug 13314: Magento 2 Tier Pricing Not Working As Expected on Product Page. #27636

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: 2.4-develop
Choose a base branch
from

Conversation

tna274
Copy link
Contributor

@tna274 tna274 commented Apr 6, 2020

Description (*)

Fix bug 13314: Magento 2 Tier Pricing Not Working As Expected on Product Page.

Related Pull Requests

Fixed Issues (if relevant)

  1. Magento 2 Tier Pricing Not Working As Expected on Product Page. #13314: Magento 2 Tier Pricing Not Working As Expected on Product Page.

Manual testing scenarios (*)

  1. I have added a set number of tiered pricing for product "A" which it's base price is £50 and set 5 tiers as below:
  • Buy 5 at £45 (All Groups "General, Guest & wholesale)
  • Buy 10 at £40 (All Groups)
  • Buy 15 at £35 (All Groups)
  • Buy 20 at £30 (All Groups)
  • Buy 25 at £25 (All Groups)

I have set a specific wholesale price tier for:

  • Buy 15 at £20 (Wholesale Only)

But on my frontend the tier pricing for a wholesale customer looks like this:

  • Buy 5 at £45 (All Groups) <---- This is working as expected.
  • Buy 10 at £40 (All Groups) <---- This is working as expected.
  • Buy 15 at £20 (Wholesale) <---- This is working as expected.
  • Buy 20 at £30 (All Groups) <---- Should be hidden.
  • Buy 25 at £25 (All Groups) <---- Should be hidden.

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Apr 6, 2020

Hi @tna274. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

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

Copy link
Contributor

@mrtuvn mrtuvn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you fix permissions file ?

@tna274
Copy link
Contributor Author

tna274 commented May 4, 2020

Hi @mrtuvn
If you want to suggest any change on my pull request, please create a new request change.
Thanks

@sidolov sidolov added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Aug 17, 2020
@joshuaswarren
Copy link

@tna274 - thank you so much for your efforts contributing to the Magento community and your work on this pull request! It looks like this request has been open for about three years now, and there hasn't been any activity on it in a while. Are you still experiencing this issue, and are you available to help complete the changes that @mrtuvn outlined so that the pull request can be processed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Catalog Priority: P3 May be fixed according to the position in the backlog. Progress: pending review Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants