Hello,

I've been doing some testing, and I was wondering how exactly the master/child relationship in Smith Cart functions. I was also curious what functionality benefits come from having this set up.

Currently, the web-store I am building has one parent store, and 40 child stores. All stores are split into 10 main "tabcategories". Some "tabcategories" only have 1 buynow store under them, some have 6. I was testing the parent/child relationship to see if I could share products between stores under the same "tabcategory", but not to stores under a different category. Sorry if that last paragraph is confusing.

From what I can tell so far, having the parent store is irrelevent. I've conducted a few tests to check the parent store funcationality, and this is what I have found.

1. Orders made on any child store can be viewed on any other child store. A parent store does not need to be referenced.

2. Products and categories "shared" from a child store share with all other stores, no matter if a store is set to child or parent.

3. Products added to child stores are not also added to parent stores. The product on a child store must be shared on a product level, causing the product to be available on all child stores and the parent store.

4. If a buynow store is set to "child", one can not pick the associated "parent" store - making it impossible to set a child/parent store heirarchy.

I'm sure there is some programming rationality behind how it is set up. I would just like to understand the relationship better, so that I can take advantage of every functionality possible for my 40 buynow page store.

Thanks! Alex