Skip to content
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

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

Open
666triv opened this issue Jan 22, 2018 · 2 comments
Open

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

666triv opened this issue Jan 22, 2018 · 2 comments
Assignees
Labels
Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P3 May be fixed according to the position in the backlog. Progress: PR Created Indicates that Pull Request has been created to fix issue Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.

Comments

@666triv
Copy link

666triv commented Jan 22, 2018

Preconditions

  1. Magento 2.2

Steps to reproduce

  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.

The basket works in the way you would expect any qty over 15 pieces the price stays at £20 but the product page does not update.

Expected result

  1. The tier price higher than what the customer would receive should be hidden as it's not relevant to that specific customer group. Rather than showing all available, as it was hidden in Magento 1 so has the programming/logic for this changed.

Actual result

  1. The higher tier price values which include the customer group browsing a product an still see the tier prices for higher quantities even when the discount is grater.
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jan 22, 2018
@magento-engcom-team
Copy link
Contributor

@666triv, thank you for your report.
We've acknowledged the issue and added to our backlog.

@magento-engcom-team magento-engcom-team added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed labels Feb 7, 2018
@nirav-kadiya nirav-kadiya self-assigned this Jan 12, 2019
@magento-engcom-team
Copy link
Contributor

Hi @ssp58bleuciel. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your 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.

@magento-engcom-team magento-engcom-team added this to PR In Progress in Community Backlog Mar 24, 2020
@ghost ghost unassigned nirav-kadiya Apr 6, 2020
@ghost ghost moved this from PR In Progress to Ready for Dev in Community Backlog Apr 6, 2020
@ghost ghost assigned tna274 Apr 6, 2020
@ghost ghost moved this from Ready for Dev to PR In Progress in Community Backlog Apr 6, 2020
@ghost ghost 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
@ghost ghost unassigned tna274 Aug 17, 2020
@sidolov sidolov added this to Ready for Grooming in Low Priority Backlog Sep 3, 2020
@m2-community-project m2-community-project bot moved this from Ready for Grooming to Pull Request In Progress in Low Priority Backlog Sep 3, 2020
@m2-community-project m2-community-project bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: PR in progress labels Sep 3, 2020
@sidolov sidolov added this to Ready for Development in Low Priority Backlog Sep 24, 2020
@m2-community-project m2-community-project bot moved this from Ready for Development to Pull Request In Progress in Low Priority Backlog Sep 24, 2020
@m2-community-project m2-community-project bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: PR Created Indicates that Pull Request has been created to fix issue labels Sep 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P3 May be fixed according to the position in the backlog. Progress: PR Created Indicates that Pull Request has been created to fix issue Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Low Priority Backlog
  
Pull Request In Progress
Community Backlog
  
PR In Progress
Development

No branches or pull requests

5 participants