Access Level Pricing

-- HikaShop version -- : HikaShop Business: 2.6.2
-- Joomla version -- : Joomla! 3.5.1 Stable [ Unicorn ] 05-April-2016 22:45 GMT
-- PHP version -- : 5.6.19
-- Browser(s) name and version -- : Firefox 45.0.1

Before the update we have pricing that the public and registered users can see. The minimum quantity is 1. We also have retailer pricing on some products. Generally in quantities of 1,3,5 and 10 pieces for price breaks.
The retailer then sees the public price, and his price with different quantities purchased. After 2.6.2 when logged in as retailer you no longer see the public price.
If I change the min Qty of retailers starting price to 2pcs the public price shows again.
Any ideas on this one

Thank you

Let me try to explain the problem.
Here is how prices are organized for many products:

Here is how it worked before an update

Here is how it works now:

Here is what I think.

The default price always include ALL groups. view.xscreenshot.com/9a92f5778ad2d70884da54abd50ce87f
So that was a bug BEFORE, which worked good for us. A Retailer saw a Registred/Public price as well is his.

Now it decides which price to show. And if there are several prices, chooses the cheapest.

And here is how it's intended to work.
- A default price is assigned to all user groups
- Each user group uses either the default price if has no own price, or own price. If there are two prices assigned to the group, then the cheapest one is shown.
- If you want to show your valuable groups the common price, so they see how kind you are to them and how much they save, then you must use this field view.xscreenshot.com/3170f695069497dda90e4479930e10e4

Nicolas, am I right?

Is yes, what should we do? We have a great number of products setup the old "buggy" way. It's a pain to edit them all and to copy-paste the default price to the Retail price field.

Hi,

You can potentially use a mass action to fill the product retail price field.
This has to be set like that: take.ms/IZfXA

Be careful when executing a mass action, a database backup is a very good thing before any mass action execution.
To make it work correctly, the global price (no access restrictions) must be the first price set in the products.