mattsoundworld is right. as earlier in this post it was said customer table doesn't have email/username as primary key. We can easily extend the login/registration methods. Rest I don't think needs to be taken care. But if this is the case it shouldn't be so hard to include this one check in NC's basic functionality. Anyway thank you guys.
We developed a "multi-employee-stores" (stores for selling prices to employees of different companies) with different prices/products for each store using v2.8 with customer roles, multi-skin (each skin for each customer role), ACL on categories and products and tier prices by customer role. With v3.x you can customize to assign automatically a customer role (one per store, and maybe with different log-in credentials) when the customer registers and assign special roles ("Burger King" and "McDonald") to give different pricing and products. I hope you understand and get some hints for what you want.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.