New customer. Association with a shop possible?

[Ted]

We're mimicking the Struts/JSP logic of the KonaKart frontend in our own Wicket frontend by using KKAppEng for most purposes.

We have customers and products shared in Multi-Store Single DB Mode and developing currently to support multiple stores. Now since customers are shared (and can use their account created at store 1 to log into store 2) it's essential for commercial purposes that we track at what shop a customer is registered as a new user initially.

Can this be configured? If not, any suggestions as to what approach can be taken best will be greatly appreciated.

[julie]

When you register a customer, you could save the store info in one of the custom fields.

[Ted]

I see there's a customers.store_id field which seems to be set to the default store ('store1') when a customer is added - instead of the actually store. There's however no field in e.g. CustomerRegistrationIf to set that manually. Would that field be a good candidate to use instead of a customer field - or are there consequences when that field is used?

[julie]

No, don't use that because there are implications. Use the custom field which can be set through the api.

[Ted]

Can you give me an indication as to what implications? They may or may not coincide with our requirements

[greg]

The store_id column is used in where clauses to support the multi-store implementation..  If you populate that yourself you could get problems.  I'd use a custom field instead.