I am currently maintaining two child portals on the same DNN installation, each carrying the same products. To do so, I first tried to do data synchronization, with the products in each child portal carrying the same product number. To be honest, this was not working very well for me though I no longer remember exactly why. Since I do not maintain inventory for my stores, I ended up turning off synchronization and, instead, did an XML export from one store with products and then an import into the other store. I don't have a lot of change in the "inventory" so when I add something, I do it manually to each portal at this point.
The thing that I recall about the synchronization method (again, I no longer use that method), is that certain data fields but not all are synchronized. I think the product description is synchronized, if I recall, but the title is not though I only briefly tried this method before concluding I didn't really need it for my particular solution.
Anyway, the point is that it is possible to have one code base for products using synchronization. However, I spent so little time with that technique that Susanne or someone more knowledgeable about it would have to respond on the more technical aspects.
Hope this helps.
All products must be added to all portals with the same product number / item code before they will be included in the sync process. If you want add fields to sync. or remove fields from sync., you must change the following stored stored procedure: CAT_ProductUpdate . The default fields are listed in the chapter below:
The Product tables of all portals which have the [Product data synchronization] option enabled will be included in the synchronization job.The unique key is the field (column) ProductNumber of the table CAT_Products. This field is named [Item code] on module CAT_Products. If a field of the table CAT_Products which is included in the synchronization is changed in one portal all products of the other portals with the same ProductNumber will also be changed. The synchronization is realized under the consideration of these fields (UnitCost and BulkPriceLimit Fields are not included):Category3ProductName EANISBNFree1Free2...
If you only use English as portal language, you must delete all entries of the CAT_Resources table to activate the standard entries from the cat_products table for the localized fields e.g. Productname, Description, DescriptionHTML etc:
Host -> SQL execute: Delete from {databaseOwner}CAT_Resources