Messages

Thanks, again, Ryan.  Yes, I realize that I could do it - I was asking if it was being done and I just didn't realize it.  In this mode it seems like a reasonable core feature.

John

Thanks, Ryan.  I'll take a look at catalog pricing.  Can I use the non-catalog pricing for the 99.7% and then just add the catalog pricing for the ones that need to be different?  Or can I have 1 catalog for the 99.7% (100 stores) and N catalogs for the others (2)?  My requirements are that I use the same code to expose and manage the store.  (i.e. I don't want 100 webapps to maintain for the storefronts)

Thanks,
John

I am currently working in Multi-Store Single Database (Engine Mode 2) with shared customers and products.  For 99.7% of the time this model is perfect for what I need but is there a way to allow for exception cases where a product has different prices in two different stores?  How about applying specials just to certain stores??

Thanks,
John

To be clear... my preference is to house the customers together for the benefits like single sign on...   I'd just like to maintain the store-customer relationship.

I am currently working in Multi-Store Single Database (Engine Mode 2) with shared customers and products.  I am looking for a way to determine which store the customer originally registered with so, for example, when newsletters are sent out they come from the store they have a relationship with and not some generic organization.