Multiple stores with master products (shared) and local prod

[penfold]

Hi there,

 

Am currently working on a solution for a client where they would require a multiple stores solution, each running on a separate domain, but with 2 product sets; one product set is the master product set, which is retrieved from a master db and accessible for each 'client' osc site. Then each client osc site can add their own products to their local site.

 

There's also the need to have a separate admin panel for each site, where they can add, update, and remove local products, but only be able to modify prices for the master products.

 

How would I be able to setup a system, where it retrieves product info from 2 databases and display it within the osc shop? It would be ok if the local products are listed within a separate category, although if it is possible to display them merged within the master categories that would be better.

 

I've looked at the multiple stores mod and virtual mall system, but they do not match the requirements.

 

Thanks,

 

 

Eelco ter Borg

[OnePhatWebyCat]

Not sure this will help or even if this is how you ment,

But this is how i am set up.

 

I made one full store, I needed two that where simular.

 

I needed one with different admin setup. so i modifyed it.

 

I needed one with all the products.

 

I needed one with all discounted products.

 

So i fully created one store, database and all, Then i used phpmyadmin dumped the dadabase.

 

 

I set up another database diff name Imported the .sql file under new name.

 

and copyed the first store to new location changed the configure.php files to match.

 

and discounted all products.

 

seemd easy to me and worked for my situation.

[penfold]

Thanks for the info, but not exactly what I meant.

 

The way you described you got a single db for each store, but what I need is to retrieve products from 2 databases. The reason I want 2 databases is so that the client can update the master products in the master db, and automatically their distrubutors have the updated master products.

 

Beside this each distributor will have store specific products that they can only sell in their store, thus the need to store it in a separate db.

 

Technically I could put everything in one db and use store IDs to identify the products per customer, but I would still have the problem with the separate db for each distributor and no redundancy that if the one db goes down, all 100+ sites are down completely.

 

Eelco

[Guest]

Why not a store with 1 db but different admin levels and in each admin they have access only to the maser products plus their products

[azer]

penfold i have the same project .. but since im a newbie i was trying to see in the different mall version of osc if something is like what we need .. by the way , since your 2 shops are form different domains , do they have different name and so all the mails and confirmation need to give a different shop name ?

[penfold]

Yes correct....everything is different for each shop, except master products.

 

The idea of one db goes out of the window, as when you have to update the master products (regularly) you would have to do that on each and every site. With a few sites it is ok, but we are looking here at potentially 20+ sites. That is quite a lot of work.

 

So, therefore I had the idea to use 1 master db, that each site accesses for these master products, but have their own db for all their local details and additional products.

[azer]

what about having only one db but fos some tale add an shop_id for those setting that are specific to one shop ?

[penfold]

I thought about that, but having only 1 db is to risky. If this db goes down, straight away all our customers are down, while with 2 dbs per site, they can still run, and if a db goes down it is only one site, and not for all our customers.

[Daemonj]

I thought about that, but having only 1 db is to risky. If this db goes down, straight away all our customers are down, while with 2 dbs per site, they can still run, and if a db goes down it is only one site, and not for all our customers.

 

Unless you are planning on running each db on a different server your statement is moot.

 

If you are planning on having separate databases, you will have severe performance issues and unless you are running RAID the databases could still become unavailable due to a hardware (drive and/or system) failure.

 

In order for an entire mysql database to not be available, the server is most likely down. Unlike some databases, a single corrupt table will not make the database unavailable.