Hi,
anything new about this issue?
+10 from me; important feature to have working correctly.
@zolthan / @blizam Would one of you mind opening a new issue with full steps to reproduce so that the core team can properly debug the issue? I'm going to close this one due to lack of information from the OP, so it would be great if you could do that so the team can chase it down!
Hi David,
I can't believe that the ticket is just closed?! In the first link on this page https://mage2.pro/t/topic/544 the problem is explained with screenshots.
And in the second link it is explained textually:
Hi Alan
I need to show a wholesale price for my products for users in the Wholesale customer group. This was easy in the Group Price functionality in Mage 1.9, but for some reason has been removed from Mage 2.
I have tried the following:
Setting up a separate Wholesale website
- The Price attribute in the product's Basic Settings screen treats the Price attribute as Global scope, even though in the Attributes it shows that Price is Website scope
Using the Tiered Pricing in Advanced options
- Even with the Quantity set as 1, it will only show the tiered price in the basket, not the catalogue pages
Any help would be appreciated
Many thanks
The probelm is, that the Group Prices were removed in Magento 2 and it is not possible to set a Qty-1 tier price for specific customer groups.
Best
Sebastian Wilhelm
I do not think its a bug, or maybe it is.
What I did, and it works flawlessly, I set up different customer groups, and in "Catalog Price Rule" I have created a rule for each group applying %%% discount to whole catalog, or categories of choice.
Then, in Tier pricing on a product edit page, I entered tier pricing, starting with "2 and above", etc. NOT "1 and above".
See my screenshots, and always remember: "NEWLY DISCOVERED BUGS MAY TURN INTO FEATURES IF NOT DEALT WITH FOR A LONG TIME". LOL







The issue is resolved for me, personally, in 2.0.4... and I may have had other issues in my 2.0.2 install
Good to know! :+1:
Is it really solved already?
Because I am still having this issue on Magento 2.1.3.
Most helpful comment
+10 from me; important feature to have working correctly.