Multiple prices based on ACL

Hi,

I would recommend to use a custom user field instead of a custom address field. Then, you can use a mass action with the trigger after a user is updated a filter on the value of the custom field, and an action "change the user group" in your mass action so that the user group is changed based on the user selection in that field.
Then, you can configure two sets of shipping methods, or two sets of payment methods, one for each user groups with different prices so that the price paid will reflect the user group the user is in.
You can then change again the user group after the order with another mass action on the trigger "after an order is updated" and a filter on the order_status and another one on the user group of the user.

Hi,

The problem is that if you try to use a custom address field instead of a custom user field, the mass actions system cannot use the action to change the user group of the customer and the after an address is created trigger. And with the "after a user is created/updated" trigger, the address isn't yet generated in the database so you can't use an address filter on it.
Also, it will mess the user groups of the customer when the customer has several addresses and/or when he manages his addresses on the frontend.

So I don't see another way besides developing a custom plugin to handle that.

Hi,

I would rather replace the user group in your mass action and configure that "free" user group as a child of the "registered" user group so that it would have the same access rights by default.
Then, you could configure the price in the products for all the user groups except the "free" one and that should do the job.

Hi,

So what do you mean by "it doesn't work" ?
I checked on your website, and when I try to register through the registration module you're using, I'm redirected to that page and no user account is created: take.ms/Rh9vn

However, when I do it through the HikaShop registration page skillsalliance.com.au/store/index.php/co...l=user&task=register I'm successfully registered AND the mass action properly add my user account to the "free" user group:
take.ms/KQjmC

So as far as I can see the process in HikaShop works just fine, and the errors you get when you try to register through the other extension registration is because it's using the HikaShop fields but only displaying some of them and not others which are required.
So the problem is with the integration. It should display all the fields that are enabled. Or you should disable the ones you don't want to use.